Re: Ruby is eating my signals!

Hi,

At Wed, 1 Sep 2004 08:14:30 +0900,
Eric Schwartz wrote in [ruby-core:03334]:
> What's happening is that the STAF library does a connect() to the remote
> system, and that connect() is what is hanging.  When Ruby recieves the
> SIGALRM, rb_trap_immediate is not set, so the signal is deferred-- the
> problem is, because it's hanging inside the connect(), the Ruby
> internals that poll that deferred list never get called, so the signal
> is effectively "eaten".

Can't you use select() before it?  Or, is it safe to abort the
function?  If so, you could interrupt it by enclosing the call
with TRAP_BEG and TRAP_END.

-- 
Nobu Nakada