On Thu, Nov 03, 2011 at 01:23:30PM +0000, Grant Edwards 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...
This probably just entails eliminating the noreturn attribute from the prototype... Rich _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
