Hello,
dyrathror wrote:
> Ok, as far as I understand, NB starts rake which starts a new ruby engine for the task. That is why the debugger stops in the rakefile but not in my code.
>
Yes, that's the case.
> Is there any possibility to attach the debugger automatically to the new ruby instance?
>
Unfortunately no automatic way at the moment. I can think of a couple of
ways to debug the rspec task, though nothing too practical: You can get
the command the rspec task runs and then run the command manually so
that you can attach the debugger to it as per the instructions here:
http://blogs.sun.com/martink/entry/remote_debugging_debug_whatever_ruby.
Or perhaps you can hack the task itself so that it runs through
rdebug-ide. There may be also better ways that don't come to my mind
right now.
Obviously it would be nice if the IDE handled this automatically, the
best would be if RSpec provided appropriate support for this - I'll need
to talk to the RSpec guys.
Cheers,
Erno
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...
