Re: No useful backtrace in core dump.

代尔欣
2010-04-22T09:02:19Z

http://sources.redhat.com/ml/gdb/2008-08/msg00123.html
From above thread:
Indeed, changing abort() to invalid memory reference makes backtrace work.
foo (int a, int b)
{
int c=40;
abort(); <--- IIUC, change to invalid memory reference
return a+b;
}

I don't know whether can remove the __attribute__((noreturn)) or not
when compiling glibc. It seems the problem a little complicated....

2010/4/22 Baurzhan Ismagulov <ibr@radix50.net>:
> On Thu, Apr 22, 2010 at 04:35:41PM +0800, 代尔欣 wrote:
>> How about I use lower optimize option with GCC? If this still
>> can't work, I will follow your suggestion...
>
> IIUC, the thread implies that rebuilding glibc without
> __attribute__((noreturn)) for abort() should solve the problem, but I
> haven't tried that.
>
> With kind regards,
> --
> Baurzhan Ismagulov
> http://www.kz-easy.com/
>