Re: [PATCH 5.6.0] local $SIG{FOO} restoration

2000-03-30 Thread Doug MacEachern
On Wed, 29 Mar 2000, Hugo wrote: I believe that this (or take2) might cause a problem for code like: sub handler { print "sig handled" } my $handlesub = "handler"; [... something reads $handlesub in numeric context ...] $SIG{ALRM} = $handlesub; i suppose the handler should

Re: [PATCH 5.6.0] local $SIG{FOO} restoration

2000-03-30 Thread Tom Christiansen
i suppose the handler should not be restored if it was Perl's, something along the lines of (on top of take2 patch): Exactly! this kind of thing is common in programs that do sigmasks or tty mode masks. The typical mistake is set noecho do something unset noecho or block

Re: [PATCH 5.6.0] local $SIG{FOO} restoration

2000-03-29 Thread Hugo
In [EMAIL PROTECTED], Doug MacEachern writes: :when 'local $SIG{ALRM} = sub {...}' goes out of scope, magic_setsig() sets :the SIGALRM handler to SIG_DFL, rather than the original handler. this :causes quite a bit of trouble running inside of apache, since 'local :$SIG{ALRM}' unhooks the apache

[PATCH 5.6.0] local $SIG{FOO} restoration

2000-03-28 Thread Doug MacEachern
when 'local $SIG{ALRM} = sub {...}' goes out of scope, magic_setsig() sets the SIGALRM handler to SIG_DFL, rather than the original handler. this causes quite a bit of trouble running inside of apache, since 'local $SIG{ALRM}' unhooks the apache SIGALRM handler for the life of that proccess. the