Re: Happy child (w/10.2), gets SIGABRT (w/10.1)
Re: Happy child (w/10.2), gets SIGABRT (w/10.1)
- Subject: Re: Happy child (w/10.2), gets SIGABRT (w/10.1)
- From: Peter Lovell <email@hidden>
- Date: Mon, 10 Mar 2003 16:32:10 -0500
On Monday, March 10, 2003, at 12:50 AM, Lance Drake wrote:
After a call to wait4(ch_pid...), the parent, examining WIFEXITED,
reports the child process has been quit via SIGABRT. (100% > repeatable)
Discussion:
-----------
In my tool, main() performs a fork(), the parent is supposed to quit
and leave the child remaining and running. This is exactly what
happens with the 10.2.4 implementation. When my manager asked for
10.1 support, it seemed like a simple enough thing - but noooooo... I
have loaded a separate disk with OS 10.1 and installed the 2.0 PB
tools, re-built the project and the formerly, completely reliable code
sputters to a total standstill.
If I skip the fork and simply execute, all of my code runs with no
problems or exceptions - it works fine! But, as soon as the fork
takes place, the child process dies a horrible death...
Hi Lance,
do you know whether the abort happens right at the start, or after the
child has done all (or some) of its work?
Regards.....Peter
p.s. I assume that both the parent and child are re-built using 10.1.x
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.