Hi,
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?
If it matters, this is happening in the context of a network message reader
thread that tries to read a message on a closed or otherwise messed up
connection and gets an error trying to peak at the header. After it
unsuccessfully reads the message, it calls pth_yield, which (I'm guessing)
is where the SIGABRT is raised.
Thanks in advance!
Brent Phillips
______________________________________________________________________
GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager (Majordomo) [EMAIL PROTECTED]
