[#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 09:03:48 UTC
List: ruby-core #7888
Hi,

In message "Re: [ ruby-Bugs-4491 ] Segfault on x86_64 when built with -O0 in CFLAGS"
    on Wed, 17 May 2006 17:57:47 +0900, Yukihiro Matsumoto <matz@ruby-lang.org> writes:

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

Oops, here's the patch.

@@ -801,5 +801,11 @@ dir_s_rmdir(obj, dir)
 
+static void
+sys_warning_1(const char* mesg)
+{
+    rb_sys_warning("%s", mesg);
+}
+
 #define GLOB_VERBOSE	(1 << (sizeof(int) * CHAR_BIT - 1))
 #define sys_warning(val) \
-    ((flags & GLOB_VERBOSE) && rb_protect((VALUE (*)_((VALUE)))rb_sys_warning, (VALUE)(val), 0))
+    ((flags & GLOB_VERBOSE) && rb_protect((VALUE (*)_((VALUE)))sys_warning_1, (VALUE)(val), 0))
 

In This Thread