[#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:
Fwd: Bug: Time#-(1e-6) doesn't substract one microsecond.
Hi,
The following minor patch proposal was recently posted on comp.lang.ruby.
Cheers,
Dave
-----Original Message-----
Subject: Bug: Time#-(1e-6) doesn't substract one microsecond.
From: Dmitry Maksyoma <ledestin@gmail.com>
Date: 17 May 2006 15:53
Newsgroups: comp.lang.ruby
Hello,
Please consider the following test:
t = Time.mktime(2006, 5, 1)
puts t, "sec: #{t.sec}, usec: #{t.usec}"
t2 = t - 1e-6
puts t2, "sec: #{t2.sec}, usec: #{t2.usec}"
t2 = t - 2e-6
puts t2, "sec: #{t2.sec}, usec: #{t2.usec}"
Mon May 01 00:00:00 NZST 2006
sec: 0, usec: 0
Mon May 01 00:00:00 NZST 2006
sec: 0, usec: 0
Sun Apr 30 23:59:59 NZST 2006
sec: 59, usec: 999999
Substracting one microsecond doesn't do anything, substracting 2
microseconds
actually substracts one microsecond.
The problem is that (time_t)1e-6*1e6 yields 0, so I changed it to
(time_t)lround(1e-6*1e6). This way the same Ruby code yields:
Mon May 01 00:00:00 NZST 2006
sec: 0, usec: 0
Sun Apr 30 23:59:59 NZST 2006
sec: 59, usec: 999999
Sun Apr 30 23:59:59 NZST 2006
sec: 59, usec: 999998
--- /home/dmaks/time.c 2006-05-16 19:50:35.000000000 +1200
+++ ruby-1.8.2/time.c 2006-05-17 13:29:50.000000000 +1200
@@ -1285,7 +1285,7 @@
if (f != (double)sec_off)
rb_raise(rb_eRangeError, "time %s %f out of Time range",
sign < 0 ? "-" : "+", v);
- usec_off = (time_t)(d*1e6);
+ usec_off = (time_t)lround(d*1e6);
if (sign < 0) {
sec = tobj->tv.tv_sec - sec_off;