[#3419] Valgrind analysis of [BUG] unknown node type 0 — Andrew Walrond <andrew@...>

Hello list,

19 messages 2004/09/17
[#3422] Re: Valgrind analysis of [BUG] unknown node type 0 — ts <decoux@...> 2004/09/17

>>>>> "A" == Andrew Walrond <andrew@walrond.org> writes:

[#3423] Re: Valgrind analysis of [BUG] unknown node type 0 — Andrew Walrond <andrew@...> 2004/09/17

On Friday 17 Sep 2004 12:01, ts wrote:

[#3424] Re: Valgrind analysis of [BUG] unknown node type 0 — ts <decoux@...> 2004/09/17

>>>>> "A" == Andrew Walrond <andrew@walrond.org> writes:

[#3425] Re: Valgrind analysis of [BUG] unknown node type 0 — Andrew Walrond <andrew@...> 2004/09/17

On Friday 17 Sep 2004 12:37, ts wrote:

[#3426] Re: Valgrind analysis of [BUG] unknown node type 0 — ts <decoux@...> 2004/09/17

>>>>> "A" == Andrew Walrond <andrew@walrond.org> writes:

[#3428] Re: Valgrind analysis of [BUG] unknown node type 0 — Andrew Walrond <andrew@...> 2004/09/17

On Friday 17 Sep 2004 13:05, ts wrote:

[#3429] Re: Valgrind analysis of [BUG] unknown node type 0 — ts <decoux@...> 2004/09/17

>>>>> "A" == Andrew Walrond <andrew@walrond.org> writes:

Re: Ruby is eating my signals!

From: Eric Schwartz <eric.schwartz@...>
Date: 2004-09-07 19:39:36 UTC
List: ruby-core #3357
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 <eric.schwartz@hp.com>
Hewlett-Packard Company Linux/Open Source Labs (LOSL)


In This Thread

Prev Next