Hello, having trouble with custom signal handlers. In my code I have: 
sub handleSigs {
  my ($signalReceived) = @_;
  my $exitVal = 0;
  log_terminal("warning: received $signalReceived signal");
  if ($signalReceived eq "INT") { $exitVal = 1; }
  elsif ($signalReceived eq "USR1") { $exitVal = 2; }
  elsif ($signalReceived eq "USR2") { $exitVal = 3; }
  myExit($exitVal);
}

$SIG{USR1}=\&handleSigs;
$SIG{USR2}=\&handleSigs;

[download]
The application talks to a custom telnet server, waiting for messages and processing those messages. If I send a SIGUSR1 to my process I get this error message: 
Signal SIGUSR1 received, but no signal handler set.

[download]
How best to debug this situation? PS: I read about safe/unsafe signals but the error message I got does not seem to apply unless I miss something. Using perl v5.20.2 on linux debian. Thanks.

In reply to trouble with custom signal handlers by casaschi

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.