SIG error during global destruction - perl

Question

I have an issue with a script I created. This is the first time I use signal as I would like my script to run like a daemon, so I set several signal Handler to properly end my script :
local $SIG{HUP} = \&StopSuperviser;
local $SIG{INT} = \&StopSuperviser;
local $SIG{QUIT} = \&StopSuperviser;
local $SIG{ILL} = \&StopSuperviser;
local $SIG{ABRT} = \&StopSuperviser;
local $SIG{TERM} = \&StopSuperviser;
This is working properly but when I send one of those signal to my script (Crt-C, kill -15, kill -1 ...) the StopSuperviser function is correctly called but I always receive the following error in my script's output:
Argument "HUP" isn't numeric in null operation during global destruction.
I have searched on google but I didn't find anything dealing with this behavior.
May someone put some light in this?
Thanks you very much for your help
Best Regards
Florent
#
Thanks four your replies, here is the StopSuperviser Function:
sub StopSuperviser
{
print "On quite\n";
$StopAlarm = 1;
&DeleteThreadOrder($AllProcess);
foreach my $Subprocess (#$AllProcess) {
foreach my $thread (#{$Subprocess->{Thread}}) {
$thread->kill('USR1');
$thread->join();
}
}
exit;
}
I also use the following package :
use Alarm::Concurrent;
This may important to know, or may not :)
Hope this help :)
Thanks again for your response and help
Best Regards
Florent

Answer 1

I had this problem earlier this year, and ended up finding the solution on PerlMonks, but I can't find the link now. I'll update if I come across it. Their explanation was much more detailed than what I present here.
It's an expression of a feature described in perlsub:
If a subroutine is called using the & form, the argument list is
optional, and if omitted, no #_ array is set up for the subroutine:
the #_ array at the time of the call is visible to subroutine instead.
If memory serves, you should be able to fix it by changing:
local $SIG{HUP} = \&StopSuperviser;
to
local $SIG{HUP} = sub { StopSuperviser() };