first release of trepanning for rubinius after next rubinius release

4 views
Skip to first unread message

Rocky Bernstein

unread,
Nov 11, 2010, 5:39:43 AM11/11/10
to Ruby Debugger
Sometime after the next rubinius release, there probably will be the a release of the trepanning debugger for rubiniius.

Evan Phoenix has been very generous about making changes to facilitate debuggers. (This includes a couple of fixes to the rubinius "reference" debugger with regards to its handling of stepping.) 

Tomek "Tomash" Stachewicz

unread,
Nov 11, 2010, 3:09:29 PM11/11/10
to Ruby Debugger
Great news!

Will that help convincing 1.9 MRI team, or are they already convinced
and 1.9.3 will have trepanning support (I mean the threadframe patches
of course) included?

Tomash

On Nov 11, 11:39 am, Rocky Bernstein <roc...@rubyforge.org> wrote:
> Sometime after the next rubinius release, there probably will be the a
> release of the trepanning debugger for
> rubiniius<https://github.com/rocky/rbx-trepanning/wiki>
> .

Rocky Bernstein

unread,
Nov 14, 2010, 8:44:53 PM11/14/10
to ruby-d...@googlegroups.com
I think there is interested in having better debugging support built in. The problem is in the mechanics of how to get it in and the time needed to sort and integrate the 18 patches.

Ruby 1.9.2 and beyond is very stable. But debugging support in 1.9 is new. So there is some conflict here.

Also, I am continuing to understand what is necessary for debugging support and what's not. Ruby 1.9 is no longer a good platform to experiment with. But Rubinius is. 

Let me close by mentioning one area where I could really use help. Basically we need a project manager to track getting the patches from rb-threadframe/combined-patches into ruby-trunk. Back around 2000, Masatake YAMATO took on this role when I was doing the same thing for bash. And Masatake is the reason folks have a debugging support inside bash today.

When I was in Japan, Nobu (I think it was Nobu) had said that rb-threadframe/patches/trunk/01-get-sourceline.patch is okay, but I should the file an issue into the Ruby bug-tracking system.

I haven't yet, although I have recently entered a new one http://redmine.ruby-lang.org/issues/show/4046 [ruby-core:33146]
That patch is a rework of a 5-line change Evan Phoenix did in Rubinius in less than 5 minutes of discussion and about 5 minutes of coding. (My translation for ruby-trunk takes about 15 lines and took me something like an hour to code and test.)
Reply all
Reply to author
Forward
0 new messages