[#7872] Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...>

All, I needed a nonblocking socket connect for my asynchronous-event

18 messages 2006/05/14
[#7873] Re: Nonblocking socket-connect — Tanaka Akira <akr@...17n.org> 2006/05/14

In article <3a94cf510605140559l7baa0205le341dac4f47d424b@mail.gmail.com>,

[#7874] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

How about introducing the method Socket#set_nonblocking, or alternatively

[#7875] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,

[#7876] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

Well, it's ok then. I'm comfortable adding in the nonblocking

[#7877] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,

Re: [ ruby-Bugs-4491 ] Segfault on x86_64 when built with -O0 in CFLAGS

From: Yukihiro Matsumoto <matz@...>
Date: 2006-05-17 08:57:47 UTC
List: ruby-core #7887
Hi,

In message "Re: [ ruby-Bugs-4491 ] Segfault on x86_64 when built with -O0 in CFLAGS"
    on Wed, 17 May 2006 17:27:48 +0900, ts <decoux@moulon.inra.fr> writes:

| This is the call rb_protect(rb_sys_warning()) which give the crash because
| rb_sys_warning() is a variadic function.

Thank you, Guy.  Does this patch could solve the problem?

							matz.

In This Thread