[#62297] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap. — Eric Wong <normalperson@...>
nari@ruby-lang.org wrote:
7 messages
2014/05/02
[#62307] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— SASADA Koichi <ko1@...>
2014/05/03
(2014/05/03 4:41), Eric Wong wrote:
[#62402] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— Eric Wong <normalperson@...>
2014/05/05
SASADA Koichi <ko1@atdot.net> wrote:
[#62523] [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan — ko1@...
Issue #9632 has been updated by Koichi Sasada.
3 messages
2014/05/11
[#62556] doxygen (Re: Re: [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan) — Tanaka Akira <akr@...>
2014-05-11 8:50 GMT+09:00 Eric Wong <normalperson@yhbt.net>:
3 messages
2014/05/13
[#62727] [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl — Eric Wong <normalperson@...>
rb_unlink_method_entry may cause old_me to be swept before the new
7 messages
2014/05/24
[#63039] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/10
Hi,
[#63077] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/10
SASADA Koichi <ko1@atdot.net> wrote:
[#63086] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/11
(2014/06/11 4:47), Eric Wong wrote:
[#63087] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/11
SASADA Koichi <ko1@atdot.net> wrote:
[#62862] [RFC] README.EXT: document rb_gc_register_mark_object — Eric Wong <normalperson@...>
Any comment on officially supporting this as part of the C API?
5 messages
2014/05/30
[ruby-core:62606] [ruby-trunk - Bug #9475] Behavior change with include + super + alias_method between 1.9.x and 2.x
From:
nagachika00@...
Date:
2014-05-15 15:25:23 UTC
List:
ruby-core #62606
Issue #9475 has been updated by Tomoyuki Chikanaga. Backport changed from 1.9.3: DONTNEED, 2.0.0: DONE, 2.1: REQUIRED to 1.9.3: DONTNEED, 2.0.0: DONE, 2.1: DONE r45367, r45387, r45388 and r45389 were backported into `ruby_2_1` branch at r45955. ---------------------------------------- Bug #9475: Behavior change with include + super + alias_method between 1.9.x and 2.x https://bugs.ruby-lang.org/issues/9475#change-46746 * Author: Ben Weintraub * Status: Closed * Priority: Normal * Assignee: Nobuyoshi Nakada * Category: * Target version: * ruby -v: ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-darwin12.0] * Backport: 1.9.3: DONTNEED, 2.0.0: DONE, 2.1: DONE ---------------------------------------- Ruby 2.0 appears to have introduced a subtle behavior change in method resolution that persists in 2.1.0. The attached test case (also visible online at https://gist.github.com/benweint/8791007) is extracted from an actual application, and while I won't defend the need to do something like this, it is clear that the behavior changed in 2.0. Note that this sounds similar to https://bugs.ruby-lang.org/issues/9236 but is in fact distinct - the test case given in that bug was fixed in Ruby 2.1. Steps to reproduce: 1. Run the attached testcase on Ruby 1.9.3 note the output 2. Run the attached testcase on Ruby 2.0.0-p353 or 2.1.0-p0, and note the output Expected results: While it's certainly not obvious to me what 'should' happen when executing this code, on 1.9.3, it produces this output: ~~~ foo from C foo from B foo from A ~~~ Actual results: On 2.0+, I get this instead ~~~ foo from C foo from B foo from B (again) foo from B foo from B (again) foo from B ... previous two lines repeated many times ... test.rb:11: stack level too deep (SystemStackError) ~~~ That is to say, on 2.0, we get into an infinitely recursive loop that doesn't happen with 1.9.3. ---Files-------------------------------- test.rb (340 Bytes) -- https://bugs.ruby-lang.org/