Ruby-debug

ruby-talk
1

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.

- Thanks in advance.

2

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.

- Thanks in advance.

Best,

···

--
Marnen Laibow-Koser
http://www.marnen.org
marnen@marnen.org
--
Posted via http://www.ruby-forum.com/\.

3

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

···

--
Posted via http://www.ruby-forum.com/\.