perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: t/perl/signals failure
Date Wed, 05 Jan 2005 16:50:38 GMT
Eric Cholet wrote:
> Le 5 janv. 05, à 17:41, Eric Cholet a écrit :
> 
>> Le 5 janv. 05, à 17:20, Stas Bekman a écrit :
>>
>>> As I've followed up, you didn't miss anything. As I'm not on your 
>>> platform all I can suggest is to dig into the code, i.e.
>>> t/response/TestPerl/signals.pm
>>
>>
>> Thanks, here's what I am seeing in that code:
>>
>>     if (!$static) {
>>         local $ENV{PERL_SIGNALS} = "unsafe";
>>
>>         eval {
>>             local $SIG{ALRM} = sub { die "alarm" };
>>             alarm 2;
>>             run_for_5_sec();
>>             alarm 0;
>>         };
>>         ok t_cmp $@, qr/alarm/, "SIGALRM / unsafe %SIG";
>>     }
>>
>> run_for_5_sec() runs for about 2 seconds, and then nothing happens. In
>> the signal handler I replaced die with warn, but the warn doesn't happen.
> 
> 
> I forgot to mention that after those 2 seconds, I see this is the error 
> log:
> 
> [Wed Jan 05 17:36:54 2005] [notice] child pid 29676 exit signal Alarm 
> clock (14)

That probably means that Apache installs its own sighandler or something 
like that? It certainly shows that a user can't use perl's ALRM on MaxOSX.

Please post a skip patch?

The POSIX works right?


-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Mime
View raw message