[#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,

one bug and one false positive defect in yaml2byte.c (we think)

From: "Pat Eyler" <rubypate@...>
Date: 2006-05-03 02:11:32 UTC
List: ruby-core #7808
We've been looking at coverity defects during our hacking night. there are two
potential bugs in yaml2byte.c.

The false positive is in syck_yaml2byte_handler.   Coverity can't find
an assignment or free for val.   It looks like it's being assigned to
in syck_add_sym (in st_insert).  We're pretty sure it's a false
positive, but if Why would like to check it ...


the bug (also identified by ville)  is in syck_yaml2byte_handler, and
involves type_tag not being freed.   This looks like the right fix. 
Why (or whomever), would you take a look at this and commit it if it's
good.


diff -p -u -r1.6 yaml2byte.c
--- yaml2byte.c 20 Sep 2005 06:50:20 -0000      1.6
+++ yaml2byte.c 3 May 2006 02:09:25 -0000
@@ -145,6 +145,7 @@ syck_yaml2byte_handler(p, n)
             strcat( type_tag, "!" );
             strcat( type_tag, n->type_id );
             bytestring_append( val, YAMLBYTE_TRANSFER, type_tag, NULL);
+           S_FREE(type_tag);
         }
     }
     switch (n->kind)


In This Thread

Prev Next