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.
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.)