Here's another gotcha that bit me just yesterday, that, in retrospect seems so obvious:
sub main_code
{
while(1) {
eval{ fork_and_do_stuff() };
print STDERR "error, but we go on anyways\n";
}
}
sub fork_and_do_stuff
{
my $pid = fork
if( $pid == 0 ) { ## simplified...
do_stuff();
exit 1;
}
}
So what happens if you die() within do_stuff() ?
The control would actually go to the eval block
enclosing the fork_and_do_stuff() call! I've
inadvertantly a child process that would execute the parent code.
That obviously sucks.
The solution is to put yet another eval block in the child code:
sub fork_and_do_stuff
{
my $pid = fork
if( $pid == 0 ) {
eval{ do_stuff() };
exit 1;
}
}
After this, I'm definitely going to be in the habit of putting all forked code in some sort of eval block to make sure that I can safely wrap the forking code in another eval block...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|