This is interesting. What happens if you say $ PERL_SIGNALS=unsafe perl myscript.pl to run this? (or whatever you and your shell like for setting environment variables.) See perldoc perldelta where it talks about the reintroduction of unsafe signal handling. The user docs are in perlrun for the PERL_SIGNALS environment variable, and perlipc for discussion of deferred signals. I am not sure whether a deferred 'safe' signal drags its initial sigaction along with it, or uses the one it finds when it is acknowleged. That could be OS-dependent.

After Compline,
Zaxo

In reply to Re: BUG? die() executing outside scope of eval block by Zaxo
in thread BUG! die() executing outside scope of eval block by jdhedden

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.