Re: SIGTRAP after writing to socket
Re: SIGTRAP after writing to socket
- Subject: Re: SIGTRAP after writing to socket
- From: Quinn <email@hidden>
- Date: Fri, 1 Dec 2006 10:37:44 +0000
At 17:13 +0100 29/11/06, Stefan Werner wrote:
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?
Well, the API has changed slightly, but the implementation has
changed significantly. 10.4 has support for all sorts of kernel
goodness (64-bit, fine grained locking, KPIs, and so on) and these
had a significant impact on the implementation of sockets.
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.
I'd still like to take a look. It's /so/ improbable for sockets code
to generating SIGTRAP...
S+E
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
_______________________________________________
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