Re: Perl dropping signals?

5.6.1 and 5.8.x have very different signal handling. In 5.6.1 signals are handled immediately, and if the interrupted perl code is in a critical place, a coredump can result. In 5.8.x, by default, signal handling is deferred until a safer time. Perhaps this could explain what you are seeing. See http://search.cpan.org/~nwclark/perl-5.8.5/pod/perl58delta.pod#Safe_Signals and http://search.cpan.org/~nwclark/perl-5.8.5/pod/perlipc.pod#Deferred_Signals_(Safe_Signals).

Comment on Re: Perl dropping signals?

Replies are listed 'Best First'.
Re^2: Perl dropping signals? by Joost (Canon) on Aug 11, 2004 at 09:14 UTC
If safe signals are the problem, they can be disabled by setting the PERL_SIGNALS environment variable. From perlrun: PERL_SIGNALS In Perls 5.8.1 and later. If set to "unsafe" the pre-Perl-5.8.0 signals behaviour (immediate but unsafe) is restored. If set to "safe" the safe (or deferred) signals are used. See "Deferred Signals (Safe signals)" in perlipc. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]

Replies are listed 'Best First'.

Re^2: Perl dropping signals?
by Joost (Canon) on Aug 11, 2004 at 09:14 UTC

perlrun

PERL_SIGNALS
In Perls 5.8.1 and later. If set to "unsafe" the pre-Perl-5.8.0 signals behaviour (immediate but unsafe) is restored. If set to "safe" the safe (or deferred) signals are used. See "Deferred Signals (Safe signals)" in perlipc.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

[reply]