Note that there are some explanatory texts on larger screens.

plurals
  1. POIntelliJ IDEA 12 not stopping at breakpoints in rails/ruby
    text
    copied!<p>I have IDEA 12 and cannot properly use debugger in Rails/Ruby [a similar question is this one <a href="https://stackoverflow.com/questions/15603921/debugger-intellij-idea-failing-when-hits-breakpoint-cucumber-ruby-rspec-ca">Idea 11 breakpoints &amp; ruby</a>]. When I pressed DEBUG the first time on a rails/ruby app it correctly installed the ruby-debug-base19x and ruby-debug-ide. Issuing a <code>gem list | grep debug</code> shows these gems:</p> <pre><code>debugger-ruby_core_source (1.2.2) ruby-debug-base19x (0.11.30.pre12) ruby-debug-ide (0.4.17.beta16) </code></pre> <p>The debug [local debug] is starting successfully and I have this in the console: </p> <pre><code>/home/user/.rvm/rubies/ruby-1.9.3-p194/bin/ruby -e at_exit{sleep(1)};$stdout.sync=true;$stderr.sync=true;load($0=ARGV.shift) /home/user/.rvm/gems/ruby-1.9.3-p194/gems/ruby-debug-ide-0.4.17.beta16/bin/rdebug-ide --port 55940 --dispatcher-port 37293 -- /home/user/work/IdeaProjects/rails/xtrade/script/rails server -b 0.0.0.0 -p 3000 -e development Fast Debugger (ruby-debug-ide 0.4.17.beta16, ruby-debug-base19x 0.11.30.pre12) listens on 127.0.0.1:55940 =&gt; Booting WEBrick =&gt; Rails 3.2.11 application starting in development on http://0.0.0.0:3000 =&gt; Call with -d to detach =&gt; Ctrl-C to shutdown server [2013-06-26 20:53:32] INFO WEBrick 1.3.1 [2013-06-26 20:53:32] INFO ruby 1.9.3 (2012-04-20) [x86_64-linux] [2013-06-26 20:53:32] INFO WEBrick::HTTPServer#start: pid=32688 port=3000 </code></pre> <p>The only thing is that the breakpoints are never hit. I tried to put breakpoints in Controllers and Views but nothing changed. I tried plenty of times to install uninstall gems but I never managed to have the debugger working in Rails/Ruby. Tried also with the remote debugging but nothing as well.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload