[erlang-questions] Can interactive debugger break on exceptions?

[Convey Christian J NPRI]

I'm using the graphical debugger (for the first time).  I'd like it to break at whatever point in my code something goes seriously wrong.  For example, an "if" statement in which no clause evaluates to true.  Is there some way I can get the debugger to stop there?

My general goal is to identify exactly where I'm getting runtime errors.  Perhaps I just don't know how to properly read an Erlang error report, but when I get an error like the following, I just don't know exactly where in my code the error occurred:

10> ray_trace:advance_ray_through_dband(0, 151, (math:pi() / 4), low_range_boundary, 200, 100, 1500, 1400, 10000).

=ERROR REPORT==== 28-Feb-2008::11:40:06 ===
Error in process <0.77.0> with exit value: {if_clause,[{ray_trace,advance_ray_through_dband,[0,151,7.853982e-01,low_range_boundary,200,100,1500,1400,10000]}]}

** exited: {if_clause,[{ray_trace,advance_ray_through_dband,
                                  [0,
                                   151,
                                   0.785398,
                                   low_range_boundary,
                                   200,
                                   100,
                                   1500,
                                   1400,
                                   10000]}]} **




Thanks for any help or suggestions.

- Christian

Christian Convey
Scientist, Naval Undersea Warfare Centers
Newport, RI