SIGTRAP after writing to socket
SIGTRAP after writing to socket
- Subject: SIGTRAP after writing to socket
- From: Stefan Werner <email@hidden>
- Date: Tue, 14 Nov 2006 12:29:21 -0800
Hi,
I'm working on a project that is using xmlprc++ to communicate
between two processes on the same machine, sending TCP packets to
localhost. What is running as expected on 10.4 (occasional SIGPIPE
when the other process isn't ready), receives SIGTRAP signals on
10.3.9. Even when I tell my application to ignore SIGTRAP, OS X still
seems to pick it up and pops up a message that the application has
quit unexpectedly (even though it continues to run).
I can't directly debug into it, since xmlrpc++ is using non-blocking
sockets and therefore I receive the signal asynchronously, that is
gdb stops in just some random place. I could narrow it down to pretty
much a single write() instruction in xmlrpc++. When I remove that, I
do not get the SIGTRAP, but obviously not any communication between
the processes either.
My questions would be
a) what could it be that I'm doing to a poor socket that results in
SIGTRAP on 10.3.9?
b) how do I not do that?
Thanks,
Stefan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden