[#7809] uninit bug in yaml/emitter.c — "Pat Eyler" <rubypate@...>
During our hacking night, we also looked at an UNINIT bug in yaml/emitter.c
[#7813] :!~ not a symbol — noreply@...
Bugs item #4344, was opened at 2006-05-03 17:41
[#7818] (security-related) patch to ALLOC macros to prevent integer overflow bugs — "Dominique Brezinski" <dominique.brezinski@...>
While fixing the integer overflow in rb_ary_fill(), it occurred to me
[#7833] segfault on Proc#call after setting a trace_func — Mauricio Fernandez <mfp@...>
$ cat bug2.rb
[#7843] Possible YAMl bug in 1.8.4 — Damphyr <damphyr@...>
OK, while parsing the td2 data from the ruby-lang website we stumbled on
Its probably a bug. I'm not familiar with the specifics, but Ruby
[#7858] Ruby threads working with native threads — "Francis Cianfrocca" <garbagecat10@...>
I recently wrote a network-event extension for Ruby ("eventmachine" in
[#7865] Strange interactions between Struct and 'pp' — noreply@...
Bugs item #4457, was opened at 2006-05-12 17:13
[#7872] Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...>
All, I needed a nonblocking socket connect for my asynchronous-event
In article <3a94cf510605140559l7baa0205le341dac4f47d424b@mail.gmail.com>,
How about introducing the method Socket#set_nonblocking, or alternatively
Hi,
Well, it's ok then. I'm comfortable adding in the nonblocking
Hi,
How about Socket#nbconnect and Socket#nbaccept?
On 5/15/06, Francis Cianfrocca <garbagecat10@gmail.com> wrote:
In article <1147709691.180288.28647.nullmailer@x31.priv.netlab.jp>,
[#7881] Segfault on x86_64 when built with -O0 in CFLAGS — noreply@...
Bugs item #4491, was opened at 2006-05-16 12:46
[#7882] reproducible bug in DRb on OSX — cremes.devlist@...
I've been tearing my hair out the last few days trying to track down
[#7909] SCRIPT_LINES__ issue when loading a file more than once — Mauricio Fernandez <mfp@...>
SCRIPT_LINES__ is an obscure feature very few people care about, but I happen
On Fri, May 19, 2006 at 06:46:05PM +0900, Mauricio Fernandez wrote:
Hi,
[#7923] Nonblocking accept — "Francis Cianfrocca" <garbagecat10@...>
Thanks to the Matz and colleagues for adding the *_nonblock functions. They
[#7928] set_trace_func: binding has wrong self value for return events — =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...>
Moin.
Florian Growrote:
Re: Coverity: Patch/Fix CID 17 OVERRUN_STATIC File: ruby/signal.c
Hello Kevin,
>static struct {
>VALUE cmd;
>int safe;
>} trap_list[NSIG];
>
>633 if (sig < 0 || sig > NSIG) {
>634 rb_raise(rb_eArgError, "invalid signal number (%d)", sig);
>635 }
>
>trap_list is only NSIG big so the "if" should be >=NSIG
>Arrays are zero based in C.
I agree that this is a valid bug. When I checked this, I couldn't find
whether ruby
map given signal number to correct C array number e.g signal 1 -> becomes
0 and
so on. If ruby does not do this it is a bug, because then we lost the
last signal (the signal
with the biggest number). So we probably should do sig = sig - 1 in the
begin of the function?
>
>
>Index: signal.c
>===================================================================
>RCS file: /src/ruby/signal.c,v
>retrieving revision 1.72
>diff -u -r1.72 signal.c
>--- signal.c 9 Jan 2006 22:32:55 -0000 1.72
>+++ signal.c 5 May 2006 02:24:42 -0000
>@@ -630,7 +630,7 @@
>rb_raise(rb_eArgError, "unsupported signal SIG%s", s);
>}
>
>- if (sig < 0 || sig > NSIG) {
>+ if (sig < 0 || sig >= NSIG) {
>rb_raise(rb_eArgError, "invalid signal number (%d)", sig);
>}
>#if defined(HAVE_SETITIMER)
>
>