Stack Smashing Detected

Is MIRIAD being a pain? Let us know your experience.

Moderator: Mark.Wieringa

Stack Smashing Detected

Postby dasingh92 » Fri Jan 17, 2020 1:08 pm

I have compiled miriad from source code. It is setup on a linux system (Manjaro to be specific). I have been trying for sometime now to get the "imgen" and "cgdisp" tasks running. On running the tasks I'm returned the following error:

*** stack smashing detected ***: <unknown> terminated

Program received signal SIGABRT: Process abort signal.

Backtrace for this error:
#0 0x7faa2641dfaf in ???
#1 0x7faa2641df25 in ???
#2 0x7faa26407896 in ???
#3 0x7faa26461257 in ???
#4 0x7faa264f1154 in ???
#5 0x7faa264f1105 in ???
#6 0x5631d38a55d4 in ???
#7 0x5631d38a61c1 in ???
#8 0x5631d38a6c0b in ???
#9 0x5631d38a6d3a in ???
#10 0x5631d38a1a66 in ???
#11 0x5631d38a1df0 in ???
#12 0x7faa26409152 in ???
#13 0x5631d389f69d in ???
#14 0xffffffffffffffff in ???

I increased the MAXBUFF and reduced MAXDIM in the $MIR/inc/maxdim.h and $MIR/inc/tempdim.h , but it had no effect on the error. I know this a security feature from gcc to prevent stack smashing attacks. Would making changes to the makefile help? Please advice.

Posts: 1
Joined: Wed Jan 15, 2020 12:35 pm

Return to MIRIAD

Who is online

Users browsing this forum: No registered users and 0 guests