Re: open fails in daemon

• Subject: Re: open fails in daemon
• From: Garth Cummings <email@hidden>
• Date: Wed, 23 Jul 2003 14:50:35 -0700

email@hidden writes:

The rule Chris and I both cited still stands. If using frameworks above
basic BSD frameworks, you cannot safely proceed after a fork() without
an exec().

I'm throwing in the towel. Thanks so much for all your help, guys, but I
can't spend any more time on this. My final test was to:
launch a tool that did a daemon(0,0), then an execlp(<self>)
when relaunched, the tool subscribed for login notifications and waited
on logout/login, the notifier was called and the tool did an
execlp(<another tool>)
the second tool launched successfully, but crashed when calling either
execlp(<CarbonApp>) or open(<CarbonApp)

Here's the stack dump which looked about the same for both execlp and open:
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0 Crashed:
#0 0x8fe1f460 in strlen
#1 0x8fe02554 in load_executable_image
#2 0x8fe01410 in _dyld_init
_______________________________________________
darwin-development mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-development
Do not post admin requests to the list. They will be ignored.

• Follow-Ups:
  • Re: open fails in daemon
    • From: Jim Magee <email@hidden>

• Prev by Date: Re: ni_setpassword() and ni_setuser() authentication
• Next by Date: Re: zero filling pages
• Previous by thread: Re: open fails in daemon
• Next by thread: Re: open fails in daemon
• Index(es):
  • Date
  • Thread