comment on

The parent is notified of which signal killed a child. If you wanted to monitor that, you could write a wrapper.

use IPC::Open3 qw( open3 );

my $child_pid = open3(
   '<&STDIN',
   '>&STDOUT',
   *CHILD_ERROR,
   @ARGV
);

my $error = '';
1 while read(CHILD_ERROR, $error, 64*1024, length($error));

$error .= "\n"
   if length($error) && substr($error, -1) ne "\n";

waitpid($child_pid, 0);

my $code = 0;
if ($? & 0x7F) {
   $error .= "Child killed by signal ".( $? & 0x7F )."\n";
   $code = 0x80 | $?;
}
elsif ($? >> 8) {
   $error .= "Child exited with error ".( $? >> 8 )."\n";
   $code = $? >> 8;
}

if (length($error)) {
   # Email $error here.
}

exit($code);
[download]

(As you can see, you no longer need custom handlers for warnings and exceptions in the script itself, unless you want to add stack backtraces.)

In reply to Re: Catching errors (II). by ikegami
in thread Catching errors (II). by Steve_BZ

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.


P is for Practical
	PerlMonks