Is there a way to set a debug point in an ACTION such that when you
trigger this via use of a web browser it will effective stop at this
point, after which you can then interrogate values of variables etc?
Ideally then STEP through the code?
Is this possible, or does one really need to use logger.debug
statements?
Is the concept that this then stops the console I’m running webbrick in,
after which I can issue ruby commands is it? Can I issue a CONTINUE to
keep things moving after I’ve done a brief manual inspection?
Tks Mark - I’ll try this this eveningIs the concept that this then stops the
console I’m running webbrick in, after which I can issue ruby commands
is it?
Can I issue a CONTINUE to keep things moving after I’ve done a brief
manual
inspection?
Almost.
If you run ./script/breakpointer (or ‘ruby script\breakpointer’ on
win32) while
the server is running, then when a breakpoint is hit you will be dropped
into an
irb session in the console where the breakpointer is running. The server
will
freeze until the breakpointer session is closed using ‘exit’ or Ctrl-D.
You can
do all the inspection and stuff you like from that breakpoint
Gareth
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.