Re: how i capture a script error to a file ?

The error is not passed as an argument to your die handler, but is in $@.

Why shell out just to print an error message?

my $message = $@;
if( open my $log, '>>', 'log.err' ) {
    print $log $message;
} else {
    warn "Couldn't write to 'log.err': $!";
    warn $message;
};
[download]

Also, your __DIE__ handler will also be invoked from within eval { ... } blocks, which is most likely only confusing to you. You should check $^S to see if eval is currently running:

    return if $^S; # we are within an eval block
[download]

Comment on Re: how i capture a script error to a file ? Select or Download Code

Replies are listed 'Best First'.
Re^2: how i capture a script error to a file ? by shmem (Chancellor) on Apr 27, 2017 at 13:16 UTC
The error is not passed as an argument to your `die` handler, but is in `$@`. How so? `$@` is the last eval error. The arguments to `die` are passed to the DIE handler (whether invoked by perl itself or via die): `local $SIG{__DIE__} = sub { open my $fh, '>>', 'log.err' or warn "Can't append to 'log.err': $!" and return; print $fh @_, "\n\$\@: \|$@\|"; }; eval { die "fubar!"; }; # <--- update, semicolon was missing 1 / 0; __END__ Illegal division by zero at foo.pl line 8.` [download] Contents of log.err: `@_: \|fubar! at foo.pl line 7. \| $@: \|\| @_: \|Illegal division by zero at foo.pl line 8. \| $@: \|fubar! at foo.pl line 7. \|` [download] The `fubar! at foo.pl line 7.` is repeated since `$@` hasn't been cleared. If there had been a subsequent succeeding `eval`, `$@` had been cleared. Neither die messages nor system errors (`$!`) are shoehorned into `$@` for the DIE handler. update 2: Also, your __DIE__ handler will also be invoked from within eval { ... } blocks, which is most likely only confusing to you. You should check $^S to see if eval is currently running: `return if $^S; # we are within an eval block` [download] This, as a general advice, is misleading. One might very well be interested in eval errors. perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'	[reply] [d/l] [select]
Re^3: how i capture a script error to a file ? by gabrielsousa (Sexton) on Apr 27, 2017 at 13:31 UTC
eval dont work on me :( `Number found where operator expected at ./test3.pl line 21, near "1" (Missing semicolon on previous line?) syntax error at ./test3.pl line 21, near "1" Execution of ./test3.pl aborted due to compilation errors.` [download]	[reply] [d/l]
Re^4: how i capture a script error to a file ? by shmem (Chancellor) on Apr 27, 2017 at 13:35 UTC
Missing `;` after the eval { } , corrected. Sorry. We all write our own bugs :-( perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'	[reply] [d/l]