Re: Daemon/launchd crashes with EXC_BREAKPOINT (SIGTRAP)
Re: Daemon/launchd crashes with EXC_BREAKPOINT (SIGTRAP)
- Subject: Re: Daemon/launchd crashes with EXC_BREAKPOINT (SIGTRAP)
- From: Eric Gouriou <email@hidden>
- Date: Tue, 20 Nov 2007 15:59:27 -0800
On Nov 20, 2007, at 12:24 AM, Elango C wrote:
I have created the Daemon which will sense the USB device arrival
and removal during the system
startup / Login. The same application works fine in Mac OS Tiger
(10.4) but the same application
is throwing errors in Mac OS Leopard and crashes.
[...]
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
[...]
Application Specific Information:
*** single-threaded process forked ***
Thread 0 Crashed:
0 com.apple.CoreFoundation 0x00b57119
CFRunLoopRunSpecific + 1833
1 com.apple.CoreFoundation 0x00b57d94 CFRunLoopRun
+ 84
2 Autopoll 0x00002cdb -[MyAutopoll
registerDeviceCallbackHandler] + 522
3 Autopoll 0x000026e8 -[MyAutopoll
init] + 114
4 Autopoll 0x00002623 main + 109
5 Autopoll 0x0000259a _start + 216
6 Autopoll 0x000024c1 start + 41
Are you fork()'ing that process and attempting to use CF-level
functionality
in the fork child ? This is not supported, and in 10.5 some checks
have been added
to error out if CF is used in a fork child.
For daemons/agents started via launchd, forking (or using daemon())
should be unnecessary.
If there is a good reason for creating a new process, you'll have to
exec or posix_spawn()
the executable.
Eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden