Issue #7214 has been updated by Conrad.Irwin (Conrad Irwin).


Hey ko1,

Your debugging API looks good :).

It would be great to do this in a gem, but we can't create binding objects anymore due to changes in symbol visibility. (for 1.9 we used rb_vm_make_env_object, but it's now not exported, see [1])

This patch "fixes" it, but there should be a better way: https://gist.github.com/2f19a3cffb1a7bdfaf22

Is there any chance you can make this function callable from C extensions?

Thanks!
Conrad

[1]  https://github.com/banister/binding_of_caller/blob/master/ext/binding_of_caller/binding_of_caller.c#L151
----------------------------------------
Bug #7214: Ruby 2.0 breaks support for some debugging tools
https://bugs.ruby-lang.org/issues/7214#change-33011

Author: banister (john mair)
Status: Open
Priority: Normal
Assignee: ko1 (Koichi Sasada)
Category: core
Target version: 2.0.0
ruby -v: ruby 2.0.0dev (2012-10-18 trunk 37260) [x86_64-linux] 


Notably the "Pry" debugger breaks, and (though i haven't checked) I'm assuming the 'debugger' project as well. The reason for the breakages (as far as i can see) is that the `rb_vm_make_env_object` function is now hidden. In the comments for 1.9.3's vm.c it was stated an alternative API for `rb_vm_make_env_object` (see https://github.com/ruby/ruby/blob/ruby_1_9_3/vm.c#L53-60) would be provided, but I have been unable to find one.

Can you please inform me of where I can find the new API (if it exists), or alternatively, provide a work-around so we can get the debuggers working on Ruby 2.0

Thanks






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