From: Marc-Andre Lafortune <redmine@...>
Date: 2009-12-27T17:00:43+09:00
Subject: [ruby-core:27335] [Bug #2330] Non systematic segmentation fault with autoload rubyspec

Issue #2330 has been updated by Marc-Andre Lafortune.

Assigned to changed from Marc-Andre Lafortune to Yui NARUSE
Priority changed from Low to High

I'm quite flattered to have been assigned this issue, but I'm afraid my skills are being overestimated.

Here's the minimal test case to reproduce:
$ cat load_test.rb
load 'test.rb'

$ cat test.rb
def Kernel.load
end
call_method_that_doesnt_exist 


$ rubydev load_test.rb
test.rb:3: [BUG] Segmentation fault
ruby 1.9.2dev (2009-12-27 trunk 26184) [x86_64-darwin10.2.0]

-- control frame ----------
c:0006 p:0024 s:0014 b:0014 l:000013 d:000013 TOP    test.rb:3
c:0005 p:---- s:0012 b:0012 l:000011 d:000011 FINISH
^Z
[4]+  Stopped                 rubydev temp.rb
$ kill -9 %
[4]+  Killed                  rubydev temp.rb


Crash happens on line 751 of vm.c (vm_backtrace_each) because cfp->me->def is 0:
if ((*iter)(arg, file, line_no, rb_id2str(cfp->me->def->original_id))) break;

As stated previously, this bug is present since r25601.

Note: I've taken the liberty to reset the priority of this issue to High, but maybe I'm mistaken in thinking that any reproducible crashing bug should be at least at that priority?
----------------------------------------
http://redmine.ruby-lang.org/issues/show/2330

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