From: silin@...
Date: 2014-01-27T00:31:43+00:00
Subject: [ruby-core:60118] [ruby-trunk - Bug #9454] The	define_method(:class) segfault

Issue #9454 has been updated by Kyrylo Silin.


Sure. As far as I understand it should raise a *SystemStackError* instead of segfaulting (that's how it worked before *v2.1.0p0*). If you could give me a hint, which file is relevant, I would probably come up with a patch (I don't promise anything, because I'm not very good at C and Ruby internals).

----------------------------------------
Bug #9454: The define_method(:class) segfault
https://bugs.ruby-lang.org/issues/9454#change-44611

* Author: Kyrylo Silin
* Status: Open
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-linux]
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
Ruby 2.1.0p0 segfaults when I invoke the following code.

    define_method(:class) { self.class }
    self.class #=> segfault :(

It affects exclusively Ruby 2.1.0p0 (I also tested on the most recent 2.0.0, 1.9.3 and 1.8.7).

By the way, on the contrary, the following code *does not segfault*.

    def self.class; self.class end
    self.class #=> SystemStackError

Viva la Ucraino revoluci��n!

---Files--------------------------------
bug9454.txt (625 KB)


-- 
http://bugs.ruby-lang.org/