Does visual debugging work in 2.5 EAP 96.552?

I'm totally at loss.  I've played with both installing and uninstalling ruby-debug (per some threads here on the boards).

I can run apps with the IDE.
I can run apps in debug mode within the IDE.
It seems I can put a breakpoint in the code and stop processing there.  
But as soon as I try to step from that breakpoint, the IDE stops responding -- the various step, step into, etc. buttons go dim and the IDE never returns.  I can't even kill the debug process without using kill -9.

For installation of the ruby-debug-base19 gem, I use the following line: gem install ruby-debug-base19 --  --with-ruby-include=$HOME.rvm/src/ruby-1.9.2-rc1


For installation of the ruby-debug-ide19 gem, I use the following line: gem install ruby-debug-ide19 --  --with-ruby-include=$HOME.rvm/src/ruby-1.9.2-rc1

Help.

My environment:
  • Mac OSX 10.6.4 -- fully patched up
  • Ruby 1.9.2-rc1 via RVM
  • Gem list:
    • abstract (1.0.0)
    • actionmailer (3.0.0.beta4)
    • actionpack (3.0.0.beta4)
    • activemodel (3.0.0.beta4)
    • activerecord (3.0.0.beta4)
    • activeresource (3.0.0.beta4)
    • activesupport (3.0.0.beta4)
    • andand (1.3.1)
    • archive-tar-minitar (0.5.2)
    • arel (0.4.0)
    • autotest (4.3.2)
    • autotest-fsevent (0.2.2)
    • autotest-growl (0.2.4)
    • autotest-rails (4.1.0)
    • bcrypt-ruby (2.1.2)
    • builder (2.1.2)
    • bundler (0.9.26)
    • columnize (0.3.1)
    • daemons (1.1.0)
    • diff-lcs (1.1.2)
    • erubis (2.6.6)
    • git-topic (0.1.4)
    • haml (3.0.13)
    • hirb (0.3.2)
    • hpricot (0.8.2)
    • i18n (0.4.1)
    • linecache19 (0.5.11)
    • mail (2.2.5)
    • mime-types (1.16)
    • nokogiri (1.4.2)
    • pg (0.9.0)
    • polyglot (0.3.1)
    • rack (1.1.0)
    • rack-mount (0.6.9, 0.6.6)
    • rack-test (0.5.4)
    • rails (3.0.0.beta4)
    • railties (3.0.0.beta4)
    • rake (0.8.7)
    • rdoc (2.5.9)
    • redgreen (1.2.2)
    • rspec (2.0.0.beta.17, 2.0.0.beta.16)
    • rspec-core (2.0.0.beta.17, 2.0.0.beta.16)
    • rspec-expectations (2.0.0.beta.17, 2.0.0.beta.16)
    • rspec-mocks (2.0.0.beta.17, 2.0.0.beta.16)
    • rspec-rails (2.0.0.beta.17, 2.0.0.beta.16)
    • ruby-debug-base19 (0.11.23)
    • ruby-debug-ide19 (0.4.12)
    • ruby_core_source (0.1.4)
    • sys-uname (0.8.4)
    • thor (0.13.7)
    • treetop (1.4.8)
    • trollop (1.16.2)
    • tzinfo (0.3.22)
    • unicorn (1.1.2, 1.1.0)
    • warden (0.10.7)
    • webrat (0.7.1)
    • wirble (0.1.3)
    • ZenTest (4.3.3)
8 comments
Comment actions Permalink

Hi Hal,

What RubyMine version do you use?
Could you please attach thread dump as described here? http://devnet.jetbrains.net/docs/DOC-1144

Best regards,
Oleg

0
Comment actions Permalink

Rubymine (standalone version): EAP 96.552 (freshly reloaded as part of my testing process)

For the attached log, I cleared the log directory, started rubymine, set the breakpoint, and attempted to use the App.  The breakpoint was in the "Home" controller, so I hit it right away.
The code is:
def index
     x = 1 # breakpoint is here
     y = 2
end

  • The app stopped at the breakpoint
  • I attempted to single step


After attempting to single step, Rubymine freezes up and the all of the "step" and the STOP buttons are grey'ed out.  I'm forced to use use one form or another of a forced kill and restart rubymine from here.

I've attached the log file.  There were no files in the thread* directory.

Hal



Attachment(s):
idea.log.zip
0
Comment actions Permalink

I have been experiencing the same behaviour when trying to debug. My log file is attached.

Also, after hitting any breakpoint, expanding local variables just shows "Collecting data...".
Adding anything that should be able to be evaluated to the Watches produces "Couldn't evaluate: ..."

My environment:

  • Mac OSX 10.6.4 -- fully patched up
  • Ruby  1.9.2-rc2 via RVM
  • Gem list:

abstract (1.0.0)
actionmailer (3.0.0.beta4)
actionpack (3.0.0.beta4)
activemodel (3.0.0.beta4)
activerecord (3.0.0.beta4)
activeresource (3.0.0.beta4)
activesupport (3.0.0.beta4)
archive-tar-minitar (0.5.2)
arel (0.4.0)
builder (2.1.2)
bundler (0.9.26)
capybara (0.3.9)
columnize (0.3.1)
configuration (1.1.0)
cucumber (0.8.5)
cucumber-rails (0.3.2)
culerity (0.2.10)
database_cleaner (0.5.2)
diff-lcs (1.1.2)
erubis (2.6.6)
faker (0.3.1)
ffi (0.6.3)
gherkin (2.1.4)
i18n (0.4.1)
json_pure (1.4.3)
launchy (0.3.5)
linecache19 (0.5.11)
machinist (1.0.6)
mail (2.2.5)
mime-types (1.16)
mysql (2.8.1)
nokogiri (1.5.0.beta.1, 1.4.2)
pickle (0.3.0)
polyglot (0.3.1)
rack (1.1.0)
rack-mount (0.6.9)
rack-test (0.5.4)
rails (3.0.0.beta4)
railties (3.0.0.beta4)
rake (0.8.7)
rcov (0.9.8)
rdoc (2.5.9)
rspec (2.0.0.beta.15)
rspec-core (2.0.0.beta.15)
rspec-expectations (2.0.0.beta.15)
rspec-mocks (2.0.0.beta.15)
rspec-rails (2.0.0.beta.15)
ruby-debug-base19 (0.11.23)
ruby-debug-ide19 (0.4.12)
ruby-debug19 (0.11.6)
ruby_core_source (0.1.4)
selenium-webdriver (0.0.24)
spork (0.8.4)
term-ansicolor (1.0.5)
thor (0.13.8)
treetop (1.4.8)
trollop (1.16.2)
tzinfo (0.3.22)
webrat (0.7.1)



Attachment(s):
idea.log.zip
0
Comment actions Permalink

I think that's a problem with the debug gem for 1.9 ruby versions. with ruby 1.8.7 everything works fine.

0
Comment actions Permalink

If it's a 1.9 problem, then everyone would be having it.

Any help from the RubyMine guys?  Having to debug via rdebug is so painful that it's insulting to the word painful.

0
Comment actions Permalink

Hi guys,

According to your logs this problem has already been reported: http://youtrack.jetbrains.net/issue/RUBY-6337
Please vote, comment and track progress of it.

Best regards,
Oleg

0
Comment actions Permalink

Just to get a clearer picture of this:

Did anybody manage to get visual debugging to workwith any ruby 1.9-version? As I mentioned above, debugging with RubyMine DOES work with 1.8.7 for me, but it never did with 1.9-version thus i thought it may have something to do with the 1.9 gem.

Am I the only one who's seeing this behaviour?

0
Comment actions Permalink

I've voted and added a note that this issue impacts 2.5 in addition to 2.0.2 (which is the listed version in the bug report).

I can't stress enough how important an issue this is.

0

Please sign in to leave a comment.