Brent Phillips wrote:
> I've been fighting a strange problem for a while now; I'm not 100% sure if
> it's in pTh or somewhere else.
>
> Basically, my app keeps coredumping as a result of a SIGABRT (which I think
> is coming from pTh) with the following stack trace:
>
> #0 0x400f2111 in __kill ()
> #1 0x400f1d66 in raise (sig=6) at ../sysdeps/posix/raise.c:27
> #2 0x400f3447 in abort () at ../sysdeps/generic/abort.c:88
> #3 0x40053795 in __pth_scheduler ()
> #4 0x400550ee in pth_spawn_trampoline ()
> #5 0x40053248 in pth_mctx_set_bootstrap ()
> #6 0x400531c6 in pth_mctx_set_trampoline ()
> #7 <signal handler called>
>
> Is there any way to get a better idea of why the SIGABRT is being raised?
Sure.. edit the generated Makefile and add "-g" to CFLAGS so that
debugging information is preserved. Rebuild and reinstall the library
and use file(1) to verify that it is "not stripped". Regnerate the above
stacktrace which should show you the file and line number where abort()
is being called (maybe within an assert() statement).
-Archie
__________________________________________________________________________
Archie Cobbs * Packet Design * http://www.packetdesign.com
______________________________________________________________________
GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager (Majordomo) [EMAIL PROTECTED]
