Re: SIGTRAP after writing to socket
Re: SIGTRAP after writing to socket
- Subject: Re: SIGTRAP after writing to socket
- From: Stefan Werner <email@hidden>
- Date: Wed, 29 Nov 2006 17:13:53 +0100
Sorry for the late response - had to do some intercontinental
traveling in between.
On Nov 16, 2006, at 11:08 AM, Quinn wrote:
Given that there's no debugger involved, the other place I've seen
these sort of exceptions is when certain pieces of system software
'panic'. For example, CF's HALT macro (used when it detects that
things are completely messed up) expands to a breakpoint
instruction ("trap" on PPC, "int3" on Intel). dyld does the same
thing. Usually when this happens you get a message on the console
that explains what happened. Do you see anything like this?
No messages at the console whatsoever. That's why I'm suspecting that
we must be doing something bad to the socket that puts it in a state
where it throws SIGTRAP. Still, the odd thing is that the same code
works fine under 10.4 and fails under 10.3.9 - the BSD socket APIs
haven't changed in between, have they?
Failing that, please post the crash log.
I can try and get one, even though it's not going to be very useful.
At the time SIGTRAP reaches the application, the thread that has done
the network operations has finished executed already, so the crash
log shows call stacks from a pretty random point in time, up to a few
seconds after the last call to socked APIs.
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