abort() missing return-address => useless core file

Bernhard Reutner-Fischer rep.dot.nop at gmail.com
Fri Nov 4 10:42:12 UTC 2011


On 3 November 2011 14:23, Grant Edwards <grant.b.edwards at gmail.com> wrote:
> It appears that the abort() function somehow breaks the resulting
> corefile so that you can't do a post-mortem backtrace.  I suspect that
> gcc has figured out that the abort() function never returns, so it
> doesn't push a return address onto the stack.
>
> I've managed to work around the problem by doing something like this
> to cause a segfault instead of calling abort():
>
>  *((volatile char*)0) = 0;
>
> That produces a usable core file.
>
> But, it would be nice if abort() could be "fixed" somehow...

Works for me. What exactly do you see? What arch? .config?


More information about the uClibc mailing list