Bug #3349: [BUG] cfp consistency error - send
http://redmine.ruby-lang.org/issues/show/3349

Author: Jonathan Bourque Olivegren
Status: Open, Priority: Normal
ruby -v: ruby 1.9.1p376 (2009-12-07 revision 26041) [i386-darwin10.2.0]

I got this error when trying to use -rprofile ("ruby19 -rprofile Main.rb") on a game I've written in Ruby+Gosy, and it seems to be related to REXML.

The ruby level backtrace information ends on a line that looks like this in my code: "doc = REXML::Document.new(File.open(map_file_path))".

Here's the full dump:

/Users/jonte/dev/games/futurecop/map.rb:249: [BUG] cfp consistency error - send
ruby 1.9.1p376 (2009-12-07 revision 26041) [i386-darwin10.2.0]

-- control frame ----------
c:0014 p:---- s:0063 b:0063 l:000062 d:000062 CFUNC  :new
c:0013 p:0034 s:0059 b:0059 l:001070 d:001070 METHOD /Users/jonte/dev/games/futurecop/map.rb:249
c:0012 p:---- s:0051 b:0051 l:000050 d:000050 FINISH
c:0011 p:---- s:0049 b:0049 l:000048 d:000048 CFUNC  :new
c:0010 p:0086 s:0045 b:0045 l:0013f8 d:0013f8 METHOD /Users/jonte/dev/games/futurecop/map.rb:18
c:0009 p:---- s:0038 b:0038 l:000037 d:000037 FINISH
c:0008 p:---- s:0036 b:0036 l:000035 d:000035 CFUNC  :new
c:0007 p:0065 s:0031 b:0031 l:0019d8 d:0019d8 METHOD Main.rb:275
c:0006 p:0335 s:0018 b:0018 l:001468 d:001468 METHOD Main.rb:73
c:0005 p:---- s:0011 b:0011 l:000010 d:000010 FINISH
c:0004 p:---- s:0009 b:0009 l:000008 d:000008 CFUNC  :new
c:0003 p:0242 s:0006 b:0006 l:001a98 d:000aa8 EVAL   Main.rb:394
c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH
c:0001 p:0000 s:0002 b:0002 l:001a98 d:001a98 TOP   
---------------------------
-- Ruby level backtrace information-----------------------------------------
/Users/jonte/dev/games/futurecop/map.rb:249:in `new'
/Users/jonte/dev/games/futurecop/map.rb:249:in `initialize'
/Users/jonte/dev/games/futurecop/map.rb:18:in `new'
/Users/jonte/dev/games/futurecop/map.rb:18:in `initialize'
Main.rb:275:in `new'
Main.rb:275:in `load_room'
Main.rb:73:in `initialize'
Main.rb:394:in `new'
Main.rb:394:in `<main>'

-- C level backtrace information -------------------------------------------
0x10010cd7d 0   libruby19.dylib                     0x000000010010cd7d rb_vm_bugreport + 77
0x10002b174 1   libruby19.dylib                     0x000000010002b174 report_bug + 260
0x10002b308 2   libruby19.dylib                     0x000000010002b308 rb_bug + 200
0x1000fd1b6 3   libruby19.dylib                     0x00000001000fd1b6 vm_call_cfunc + 566
0x1000fe9a0 4   libruby19.dylib                     0x00000001000fe9a0 vm_call_method + 896
0x1000ff8ec 5   libruby19.dylib                     0x00000001000ff8ec vm_exec_core + 3180
0x100104b83 6   libruby19.dylib                     0x0000000100104b83 vm_exec + 1203
0x100106af0 7   libruby19.dylib                     0x0000000100106af0 vm_call0 + 624
0x1000fe298 8   libruby19.dylib                     0x00000001000fe298 rb_funcall2 + 296
0x10005e343 9   libruby19.dylib                     0x000000010005e343 rb_class_new_instance + 51
0x1000fd0d4 10  libruby19.dylib                     0x00000001000fd0d4 vm_call_cfunc + 340
0x1000fe9a0 11  libruby19.dylib                     0x00000001000fe9a0 vm_call_method + 896
0x1000ff8ec 12  libruby19.dylib                     0x00000001000ff8ec vm_exec_core + 3180
0x100104b83 13  libruby19.dylib                     0x0000000100104b83 vm_exec + 1203
0x100106af0 14  libruby19.dylib                     0x0000000100106af0 vm_call0 + 624
0x1000fe298 15  libruby19.dylib                     0x00000001000fe298 rb_funcall2 + 296
0x10005e343 16  libruby19.dylib                     0x000000010005e343 rb_class_new_instance + 51
0x1000fd0d4 17  libruby19.dylib                     0x00000001000fd0d4 vm_call_cfunc + 340
0x1000fe9a0 18  libruby19.dylib                     0x00000001000fe9a0 vm_call_method + 896
0x1000ff8ec 19  libruby19.dylib                     0x00000001000ff8ec vm_exec_core + 3180
0x100104b83 20  libruby19.dylib                     0x0000000100104b83 vm_exec + 1203
0x100106af0 21  libruby19.dylib                     0x0000000100106af0 vm_call0 + 624
0x1000fe298 22  libruby19.dylib                     0x00000001000fe298 rb_funcall2 + 296
0x10005e343 23  libruby19.dylib                     0x000000010005e343 rb_class_new_instance + 51
0x1000fd0d4 24  libruby19.dylib                     0x00000001000fd0d4 vm_call_cfunc + 340
0x1000fe9a0 25  libruby19.dylib                     0x00000001000fe9a0 vm_call_method + 896
0x1000ff8ec 26  libruby19.dylib                     0x00000001000ff8ec vm_exec_core + 3180
0x100104b83 27  libruby19.dylib                     0x0000000100104b83 vm_exec + 1203
0x100106af0 28  libruby19.dylib                     0x0000000100106af0 vm_call0 + 624
0x1000fe298 29  libruby19.dylib                     0x00000001000fe298 rb_funcall2 + 296
0x10005e343 30  libruby19.dylib                     0x000000010005e343 rb_class_new_instance + 51
0x1000fd0d4 31  libruby19.dylib                     0x00000001000fd0d4 vm_call_cfunc + 340
0x1000fe9a0 32  libruby19.dylib                     0x00000001000fe9a0 vm_call_method + 896
0x1000ff8ec 33  libruby19.dylib                     0x00000001000ff8ec vm_exec_core + 3180
0x100104b83 34  libruby19.dylib                     0x0000000100104b83 vm_exec + 1203
0x100104d30 35  libruby19.dylib                     0x0000000100104d30 rb_iseq_eval_main + 176
0x10002d902 36  libruby19.dylib                     0x000000010002d902 ruby_exec_node + 178
0x10002ee54 37  libruby19.dylib                     0x000000010002ee54 ruby_run_node + 84
0x100000ecf 38  ruby19                              0x0000000100000ecf main + 79
0x100000e74 39  ruby19                              0x0000000100000e74 start + 52
0x3 40  ???                                 0x0000000000000003 0x0 + 3

[NOTE]
You may encounter a bug of Ruby interpreter. Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

Abort trap


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