Re^2: Signal Handling throws Core Dump

When I give $SIG{INT} an anonymous subroutine, I can at least get it it to increment $sig and exit cleanly.

But when I try to run an object method designed to remove a stored PID from a DB, it cores.

# doesn't work
$SIG{INT}  = sub {
     $sig++;
     $control->removeMonitorPID($monitor->{PID});
};
[download]

dsb
This @ISA my( $cool ) %SIG

Comment on Re^2: Signal Handling throws Core Dump Download Code

Replies are listed 'Best First'.
Re^3: Signal Handling throws Core Dump by jettero (Monsignor) on Apr 25, 2007 at 16:57 UTC
Well, that shouldn't be too surprising. You're not really supposed to do stuff like that from a signal handler. That's not even a perl specific issue. -Paul	[reply]
Re^3: Signal Handling throws Core Dump by former33t (Scribe) on Apr 26, 2007 at 03:05 UTC
I first want to clarify that there are WAY better ways to do this, but if you want to increment a global variable to detect a signal being caught this will do the trick. As Paul noted earlier you shouldn't be trying to do anything complicated in the signal handler itself. `our $sig; $sig = 1; $SIG{INT} = sub { $sig++; }; my $oldsig; while (1) { if ($sig != $oldsig) { $control->removeMonitorPID($monitor->{PID}); #Execute the code ori +ginally in the signal handler. $oldsig = $sig; } .... Run main loop, but make sure to poll the status of the global v +ariable .... }` [download]	[reply] [d/l]
Re^4: Signal Handling throws Core Dump by jrw (Monk) on Apr 26, 2007 at 16:52 UTC
Can you mention some of the WAY better ways or point at some references for them?	[reply]
Re^4: Signal Handling throws Core Dump by dsb (Chaplain) on Apr 28, 2007 at 03:13 UTC
I actually did take the "complicated" code out of the sig handler and put it into a couple of conditional blocks as you demonstrated. I did still get the core dumps. However, I can't remember if I left the handler as simple as incrementing the global `$sig`. I'll give that a go... dsb This `@ISA my( $cool ) %SIG`	[reply]


P is for Practical
	PerlMonks