Hmm, not wanting to get into a semantic squabble here, but unless I'm mistaken (which is always possible) it is the signal handler, not the signal itself which was unsafe. Or more precisely the way perl used to process signals wich allowed for "unsafe" handling.

I was referring to Zaxo's signal handler, which printed out a string. As the linked node mentions, it is possible to cause a core dump when doing stdio in a signal handler during another stdio operation. So I figured a word of warning would be appropriate, since the original poster seemed to want to intercept the SIGINT and carry on regardless. Sorry for not explaining that in more detail earlier.

In reply to Re^4: How do we capture CTRL^C by tirwhan
in thread How do we capture CTRL^C by Anonymous Monk

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.