Handling of SIGINT

[Andy Armstrong]

On 19 Feb 2009, at 19:13, Alex Vandiver wrote:
> Hrm.  The odd thing is, this isn't Win32, this is  
> SPAR^H^H^H^HLinux.  At
> first I assumed something odd relating to double-forking, but even  
> that
> can't actually explain what I'm seeing -- certainly, simple test cases
> correctly pass on the INT to their kids correctly.  The odd thing is,
> the $SIG{INT}=sub{kill INT=>$self->{pid}} actually seems to solve the
> problem, which is even more inexplicable, now that I think about it.
> *mumble*  I'll see if I can strip this down to a smaller test case  
> later
> tonight.


Thanks Alex!

-- 
Andy Armstrong, Hexten