Re: [Speedycgi-users] Possible ALARM bug report and a feature wish

[PW <sub...@me...>]

Regarding my problem report (item 1):

After auditing again over 10000 lines of code, I finally found a well
hidden bug in the module that caused the symptoms which I wrongly
interpreted as an ALARM bug:

local( undef $/ );
...eval alarm routine ...
...trigger error if alarm and return;
...$/ = "\n";

which of course messed up the further processing in the main application
sharing the same name space if a timeout error was triggered, because I
forgot to setback the input record separator before and because the
localizing was bogus, it should have been: local { undef $/ }; The hard
part in tracing this error was that this also suppressed the
debugging/error output. 

In this sense, sorry for a false alarm ;)

Philippe Wiede
megapublic inc.


PW wrote:
> 1. Problem:
> ALARM eval kills SpeedyCGI process each time, causing a full reload of
> my application on the next request. This happens both in a module (if a
> WHOIS timeout error is raised) and in an internal subroutine (were the
> eval is most ever successful). I know that the change file of SpeedyCGI
> lists this issue as fixed but it does not seem so. Maybe it has to do
> with the Group feature?
> 
> Example code:
> .........
> 
> Result: a timeout signal causes the process to die after the HTTP request
> .........