Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Re: Catching errors (II).

by ikegami (Patriarch)
on Oct 30, 2014 at 14:50 UTC ( #1105639=note: print w/replies, xml ) Need Help??

in reply to Catching errors (II).

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);

(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.)

Replies are listed 'Best First'.
Re^2: Catching errors (II).
by Steve_BZ (Chaplain) on Oct 30, 2014 at 20:48 UTC

    Hi Ikegami,

    I'm trying it out now.

    Thanks very much,


Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1105639]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (3)
As of 2023-03-22 06:06 GMT
Find Nodes?
    Voting Booth?
    Which type of climate do you prefer to live in?

    Results (60 votes). Check out past polls.