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...
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|