Note that die is often caught in eval, and you usually don't want to log such fake deaths. You can avoid that by checking $^S:

  $SIG{__DIE__} = sub {
    die @_ if $^S;
    ...
  };

[download]

Note that the fake SIG handlers __DIE__ and __WARN__ have special handling: the handler is suspended while running it, so calling die() within the die handler does the right thing.

This still won't necessarily do the right thing for the commonish idiom of 'load module if available':

  BEGIN {
    $module_loaded = eval { require Some::Module };
  }

[download]
since in that context $^S is set to undef; I'm not aware of any easy way to determine in that case whether or not the failed require is happening inside an eval.

Hugo

In reply to Re: Re: Capturing Text from a die command by hv
in thread Capturing Text from a die command by or10n

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.