Re: SIGTRAP after writing to socket
Re: SIGTRAP after writing to socket
- Subject: Re: SIGTRAP after writing to socket
- From: Quinn <email@hidden>
- Date: Thu, 16 Nov 2006 10:08:06 +0000
At 8:33 -0800 15/11/06, Stefan Werner wrote:
It does, that is exactly what's puzzling me. The crash log mentions
EXC_BREAKPOINT.
That's because of the way that CrashReporter works. It catches the
Mach exception (EXC_BREAKPOINT), generates the crash log, and then
forwards the exception to the next handler in the chain. In this
case, the next handler is the BSD subsystem within the kernel, hich
reflects the exception back into the process as the appropriate BSD
signal (SIGTRAP).
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?
Failing that, please post the crash log.
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