comment on

Anything else that could de-register a signal handler?

Usually, signal handlers are set and unset by assigning to %SIG, so start looking for assignments to %SIG. A text search for "SIG" should be sufficient.

XS code can mess with signals behind your back, and without perl noticing it. If you use XS code, search for signal and sigaction in the XS code.

The POSIX module also implements a wrapper for sigaction, so you may also want to search for sigaction in the perl code.

And the most obvious one: Search for the constant part of the error message ("received, but no signal handler set.") in the code.

A quick CPAN search reveals that the message may actually come from within perl, from the thread handling or the magic handling code. However, perldiag does not document this message. So, it looks to me like you have really messed up perl's internals.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

In reply to Re^2: trouble with custom signal handlers by afoken
in thread trouble with custom signal handlers by casaschi

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks