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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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, details, 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, summary, 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.