Re: [eclipse-clp-users] Debugging and Development

From: Joachim Schimpf <joachim.schimpf_at_...44...>
Date: Sat, 13 Mar 2010 13:51:13 +1100
Christian Wirth wrote:
> Additional better debug capabilitys would be very handy ... but i assume 
> there is no other debugger ?

The debugger does have a number of clever features (they might need
better documentation), but if you have concrete suggestions for new
ones, please share them!

> But i hope there is a solution to a debug
> problem i have very often:
> When i get a "real" error, not something like predicate not found (a.E 
> instantiation fault in call(_8087) ), i want to know where and when .. 
> how to ?

The first thing is to start your program, select LEAVE from the
"To port" menu, and click the button.  This takes you to just after
the error was raised, and the source display should show where you are.

You can then refresh the goal stack to see the nesting of calls.
Look at the invocation number (the number in parentheses) of the
buggy call (or its parent).  Then re-run the program, and use
"To Invoc" to jump directly to the buggy call (or its parent).

As Kish said, the "Analyze failure" feature can also often bring
you to the point that caused the problem.

-- Joachim
Received on Sat Mar 13 2010 - 02:51:22 CET

This archive was generated by hypermail 2.3.0 : Sun Aug 25 2019 - 09:14:48 CEST