Re: SIGTRAP after writing to socket
Re: SIGTRAP after writing to socket
- Subject: Re: SIGTRAP after writing to socket
- From: Scott Ribe <email@hidden>
- Date: Mon, 04 Dec 2006 11:22:25 -0700
- Thread-topic: SIGTRAP after writing to socket
> Again, the whole thing does not happen when the thread only opens and
> closes the socket but does not write to it. As soon as it writes to
> it, the program may receive receive a SIGPIPE, which is ignored
> correctly, then the program receives a SIGTRAP when the thread
> terminates. All the socket operations are asynchronous. The SIGTRAP
> occurs only on 10.3.9, not on 10.4.
I use MTTasks extensively in a Cocoa app: main thread handles UI, another
thread handles sending, and another receiving, using the BSD sockets API.
I've never seen a SIGTRAP from the socket communications.
The only SIGTRAPs I've ever seen were the (deferred) result of memory
management errors on my part.
I'd be taking a careful look at what happens in terms of memory management
(and maybe also thread synchronization) after the SIGPIPE is received.
--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice
_______________________________________________
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