On Jan 19, 2012, at 12:49 PM, Jens Alfke wrote: > On Jan 19, 2012, at 10:10 AM, Scott Ribe wrote: > >> Not true. It looks like the case at a cursory level because session >> management does this when you're in the terminal. There are various ways to >> arrange for a process to exit when its parent exits. But it is *not* the >> case that a process is automatically killed when its parent exits. > > Huh; you learn something new every day! > > In addition to shell behavior you mention, I also see this when Xcode crashes > and takes down the app I’m debugging. But I suppose Xcode configures the > process it launches to work that way?
This is probably because Xcode is using a pseudo-terminal device as the subprocess's output, so it can capture it and show it in the console window, and thus the subprocess has a controlling terminal, which is closed when Xcode crashes, which delivers SIGHUP to the subprocess. If a process hasn't specifically arranged otherwise, it will be killed by the SIGHUP. Regards, Ken _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
