[#35027] [Ruby 1.9-Bug#4352][Open] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) — "James M. Lawrence" <redmine@...>

Bug #4352: [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)

16 messages 2011/02/01

[#35114] [Ruby 1.9-Bug#4373][Open] http.rb:677: [BUG] Segmentation fault — Christian Fazzini <redmine@...>

Bug #4373: http.rb:677: [BUG] Segmentation fault

59 messages 2011/02/06

[#35171] [Ruby 1.9-Bug#4386][Open] encoding: directive does not affect regex expressions — mathew murphy <redmine@...>

Bug #4386: encoding: directive does not affect regex expressions

9 messages 2011/02/09

[#35237] [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order — Suraj Kurapati <redmine@...>

Bug #4400: nested at_exit hooks run in strange order

12 messages 2011/02/15

[ruby-core:35081] Re: allocate vs. initialize & JSON segfault

From: "U.Nakamura" <usa@...>
Date: 2011-02-04 01:54:45 UTC
List: ruby-core #35081
Hello,

In message "[ruby-core:35079] allocate vs. initialize & JSON segfault"
    on Feb.04,2011 08:24:57, <tle@holymonkey.com> wrote:
> Is there a preferred approach? Is the JSON example a bug, or should a
> script never override a C initializer without super?

In this case, JSON extension should check whether the members
of the struct is `empty' or not.
So, this is a bug of JSON extension.


Regards,
-- 
U.Nakamura <usa@garbagecollect.jp>


In This Thread