Question:
I was wondering if there was a way to instruct the ruby debug
framework to stop/break/freeze on any error so I can investigate the
call stack to diagnose the problem?
Background:
I am using ‘ruby-debug’ and know that I can insert breakpoints with
the debugger() method call in my code. I have run into errors within
unexpected callbacks and often have no idea why the code traversed
that path. Because I don’t understand the code path it’s hard to know
where to put the breakpoint to troubleshoot the problem.
RubyNewbie wrote:
Question:
I was wondering if there was a way to instruct the ruby debug
framework to stop/break/freeze on any error so I can investigate the
call stack to diagnose the problem?
Background:
I am using ‘ruby-debug’ and know that I can insert breakpoints with
the debugger() method call in my code. I have run into errors within
unexpected callbacks and often have no idea why the code traversed
that path. Because I don’t understand the code path it’s hard to know
where to put the breakpoint to troubleshoot the problem.
Then what you need is not a debugger; you need to understand the code
better (more tests?). Or put the breakpoint before the branch and watch
what happens to make the program choose it’s path.
Best,
–Â
Marnen Laibow-Koser
http://www.marnen.org
[email protected]
Background:
I am using ‘ruby-debug’ and know that I can insert breakpoints with
the debugger() method call in my code. I have run into errors within
unexpected callbacks and often have no idea why the code traversed
that path. Because I don’t understand the code path it’s hard to know
where to put the breakpoint to troubleshoot the problem.
You could try
(rdb:) catch Exception
or running it like
rdebug --trace # run it with a tracer.
-r