Re: forked die() in eval block has counterintuitive behavior?

Is this on win32? You may have found a weakness in the fork emulation. You may find it documented in perlwin32.

With a proper fork, nothing that happens in the child can affect the parent without explicit IPC. Do you have a $SIG{CHLD} handler set? See perlipc.

After Compline,
Zaxo

Comment on Re: forked die() in eval block has counterintuitive behavior?

Replies are listed 'Best First'.
Re^2: forked die() in eval block has counterintuitive behavior? by rlucas (Scribe) on May 24, 2005 at 13:03 UTC
As mentioned to samtregar above, I misrepresented that the die was caught "by" the parent -- in fact, it was caught in the child, by code that never was intended to have been forked. This is all on Debian Sarge, with Perl 5.8.4 and threads enabled. But I don't think any of it is platform-specific: once I understood what the code was underneath, it became clear that things were going by the book.	[reply]