Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

RubyMine Debugger.start is not called yet

I faced this exception when debugging with RubyMine...

Debugger.start is not called yet.
like image 912
Mustafah Avatar asked Jul 23 '12 10:07

Mustafah


2 Answers

After a while of trying other proposed solutions, I found that I had the following in the gem file:

gem "debugger"

This causes a conflict somehow for the debugger... Removing this line solved it to me...

Thanks...


Source: Debugger crashes when it hits the first breakpoint

like image 90
Mustafah Avatar answered Nov 02 '22 15:11

Mustafah


As an addendum to Mustafah's comment, it took me a while to track down this variant of the issue:

gem 'pry-full'
gem 'debugger'

Both of these lines were causing the problem, so I had to change to:

unless ENV['RM_INFO']
  gem 'pry-full'
  gem 'debugger'
end

How do you know which gems might indirectly be loading the debugger gem? Look in your Gemfile.lock for entries which suggest this depedency:

pry-debugger (0.2.2)
  debugger (~> 1.3)
  pry (~> 0.9.10)
like image 37
Nick Marden Avatar answered Nov 02 '22 16:11

Nick Marden