Is this not working for anybody else?

It's in my Gemfile, in the right environment, etc.

In unicorn, everything works as expected. It breaks out at the line I put 
"debugger" on, inside some model code. Happy times.

In the Rails console ("rails c" and "rails c --debugger"), the "debugger" 
statement seems totally ignored. No output, no debugging. With a bit of 
printf debugging, I can see that inside the debugger gem, a call to 
Debugger.start_ is made, and I believe this method is implemented via the 
Ruby/C API and thus precludes me continuing my printf debugging without a 
lot of recompiling effort.

Fresh Rails project seemed to have the same problems.

I note that putting "debuggger" at any point during the Rails boot process 
seems to work as expected, too, even with "rails c". Just not once the 
console has booted fully.

Hair pully outy.
Greg

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/rails-oceania.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to