[#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: Possible YAMl bug in 1.8.4
On 5/9/06, Mauricio Fernandez <mfp@acm.org> wrote:
>
> On Tue, May 09, 2006 at 10:51:54AM +0900, Curt Hibbs wrote:
> > Its probably a bug. I'm not familiar with the specifics, but Ruby
> > 1.8.4does have known bugs in its YAML support.
> >
> > I haven't verified this, by ruby-mswin32 (upon which the one-click
> installer
> > is built) has a new 1.8.4 build released last month. Since there have
> not
> > been any further releases of Ruby 1.8.4, I'm assuming that this
> ruby-mswin32
> > release includes updated YAML fixes from CVS HEAD.
> >
> > Anyway, I'm going to find out and, if so, update the one-click installer
> for
> > its next release.
>
> It's not fixed in CVS (ruby_1_8 branch):
>
> $ ruby -v yaml-bug.rb
> ruby 1.8.4 (2006-05-09) [i686-linux]
> /home/batsman/usr/lib/ruby/1.8/yaml.rb:133:in `load': syntax error on line
> 5, col 4: ` <dt>From: Yukihiro Matsumoto <matz at' (ArgumentError)
> from /home/batsman/usr/lib/ruby/1.8/yaml.rb:133:in `load'
> from yaml-bug.rb:7
> $ cat yaml-bug.rb
> require 'yaml'
>
> bug=[{:content=>"\n\n <dl>\n<dt>From: Yukihiro Matsumoto <matz at
> ruby-lang.org></dt>"}]
>
> dumped=YAML.dump(bug)
> p YAML::load( dumped )
Too bad... The change log does list a few syck bug fixes, but obviously not
all of the problems have been fixed.
Curt