From: Eric Schwartz Date: 2004-09-08T04:39:36+09:00 Subject: Re: Ruby is eating my signals! On Tue, 2004-08-31 at 18:52, nobu.nokada@softhome.net wrote: > Can't you use select() before it? No, sorry. The problem is in the connect() itself, so there's no handle to select() on yet. :( > Or, is it safe to abort the function? If so, you could interrupt it by enclosing the call > with TRAP_BEG and TRAP_END. Ah hah! That has fixed the problem exactly! So when executing code in a C extension, ruby turns rb_trap_immediate off? That would explain what I was seeing. Thank you very muck Nakada-san! -=Eric -- Eric Schwartz Hewlett-Packard Company Linux/Open Source Labs (LOSL)