Ruby Debug Step Over Not Working Follow Sam Ramsden Created June 23, 2009 00:19 The Ruby Debugger will not step over ... step over is treated as a step into.I am using IntelliJ build #9886 with Ruby Plugin 2.0.235166
I think several people have this problem (I have it in RubyMine) but the bug over in JIRA (http://www.jetbrains.net/jira/browse/RUBY-4187) has been closed. I've already added a comment to it as my Google search revealed other occurences of this in Netbeans. There it seemed to only occur for JRuby.
For me, the most annoying thing with that is that the debug session tends to crash the deeper you dig into the internals of Rails (as you're always stepping into and 'step out' also does not work very often). My workaround is to set another breakpoint at the next relevant line and then proceed to that...
Run to cursor is another quick workaround, saves creating extra breakpoints.
We've intergrated the latest version of intermediate-java library used to communicate with debugger from java. Fix will be available in coming RubyMine 1.1.1, new Ruby plugin and RubyMine 1.5 EAPs.
Cool, should have posted this here earlier (instead of just adding a comment to JIRA).
Any idea when RubyMine 1.1.1 will be released?
We plan to release it in a couple of days.
I know this post is almost 3 years old, and the issue is supposed to be fixed, but I just started using Rubymine 4.0 about a month ago, and I'm having the same exact issue. Step over actually steps into the code. Step out doesn't work. Is this still a known issue? Are there any workarounds (other than creating a bunch of breakpoints and continuing or using Run to Cursor)?
RUBYGEMS VERSION: 1.5.1
RUBY VERSION: 1.8.7 (2011-08-23 patchlevel 330) [java]
INSTALLATION DIRECTORY: C:/jruby-1.6.4/lib/ruby/gems/1.8
RUBY EXECUTABLE: C:/jruby-1.6.4/bin/jruby.exe
EXECUTABLE DIRECTORY: C:/jruby-1.6.4/bin
:update_sources => true
:verbose => true
:benchmark => false
:backtrace => false
:bulk_threshold => 1000
"install" => "--no-rdoc --no-ri --env-shebang"
"update" => "--no-rdoc --no-ri --env-shebang"
IDE: JetBrains RubyMine 4.0.2, build #RM-113.31
OS: Windows 7 6.1[x86]
RubyMine SDK Environment:
Sdk Version: ver.1.6.4 (ruby-1.8.7-p330, 17ea768, Java HotSpot(TM) 64-Bit Server VM 1.6.0_30) p330
Ruby Interpreter: C:/jruby-1.6.4/bin/jruby.exe
RVM Sdk: no
Sdk Language Level: 1.8
Sdk Load Path:
C:/Program Files (x86)/JetBrains/RubyMine 4.0.2/rubystubs18
Sdk Gem paths:
Gems used for 'consensus5':
looks like a regression. I've found the issue and fix will be available in the next bugfix update. In the meanwhile you can add following as Ruby arguments for your run configuration:
-J-Djruby.reflection=true -J-Djruby.compile.mode=OFF -J-Djruby.debug.fullTrace=true
Thanks for the quick response. This did fix the step over issue. Note, for anyone else who may be reading this, the arguments need to be separated with a semicolon.
However, Step Out still seems to be broken. When I try to step out, the step cursor just disappears, and the continue button is grayed out. It's as if the debugger has still paused execution of the app, but RubyMine doesn't realize it. As a result, the app is stuck in a paused state with no way that I can see to continue, and I have to shut down the app and restart it in order to continue running it.
I am on RubyMine 188.8.131.52.1, Ruby 2.0.0-p247 and I am seeing this issue. The configuration arguments do not resolve the issue. Is there some other workaround?