-
Notifications
You must be signed in to change notification settings - Fork 80
ruby2: next command not stepping to next line #89
Comments
As stated in the readme , 2.0 isn't fully working. See #47 and #69 for context. More work needs to be done to port debugger to support 2.0. I will leave this open for others who encounter this until 2.0 support comes. I encourage anyone to work on this and the prerequisite tickets as I don't have the bandwidth or the need. |
As an alternative, I have been using the byebug debugger, which doesn't have this issue. |
@cldwalker Any improvement on full ruby 2.0 support ? Especially for this next / step issue ? I believe byebug will become the default debugger for many developers in the short term if the debugger gem does not fix this ... |
@bartocc I rarely use ruby at work so this is prioritized accordingly. If you've read the above links to #47 and #69, then you're aware I've put a call out to the community. So far the community has responded with partial support and a pseudo-fork with byebug. If you're interested in this, please contribute or encourage others to do so. |
Closing since I'm scoping debugger to just 1.9.2 and 1.9.3. For more see #125 (comment) |
The "next" command used to reliably step over the calls in the current line, leaving you on the next line. Now debugger seems to step into some methods when you use it.
For example, here it's stepped inside the #exceptions method, which happens to be an ActiveRecord attribute method; it doesn't step inside #empty? though, so it sometimes works.
(I've removed some lines of our real code from this backtrace)
The text was updated successfully, but these errors were encountered: