From jan@swi.psy.uva.nl  Fri Nov 10 10:10:06 2000
Received: from gollem.swi.psy.uva.nl (gollem [145.18.152.30])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id KAA02503;
	Fri, 10 Nov 2000 10:10:06 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]])
	by gollem.swi.psy.uva.nl (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id KAA05900;
	Fri, 10 Nov 2000 10:10:04 +0100
From: Jan Wielemaker <jan@swi.psy.uva.nl>
Organization: SWI, University of Amsterdam
To: leo@solvo.ru
Subject: Re: Q about GUI tracer
Date: Fri, 10 Nov 2000 09:56:07 +0100
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <20001110114221.A11760@solvo.ru>
In-Reply-To: <20001110114221.A11760@solvo.ru>
Cc: prolog@gollem.swi.psy.uva.nl
MIME-Version: 1.0
Message-Id: <00111010100400.05477@gollem>
Content-Transfer-Encoding: 8bit

On Fri, 10 Nov 2000, leo@solvo.ru wrote:
>Hi!
>I've just tried GUI tracer for debugging prolog and found it very usefull,
>but i have some questions:
>
>There is some difference between hot-keys in gui-tracer and native pl-tracer,
>why?

Because the view is a little different.  In the normal tracer you are
looking at the now-running predicate, while in the GUI tracer you are
looking at the parent calling the now-running predicate.  This resulted
in a slightly different command-set with the resulting hotkey bindings.

>And how can i pass 'fail' and 'ignore' commands to my debugging program from
>gui-tracer?

At the moment you can't.  Just have a look at the source and I think
you'll be able to sort out how to add it.  Additions and improvements
are welcome.  Comments too, but don't really expect this thing to be
as fool-proof as the Prolog environment itself.  I generally use it
to figure out non-determinism problems.

I must admit I only use it `now-and-then' for real debugging.  In
practice I see myself using trace/1 quite often, spy or inserting a
call to trace/0 and look around using the normal tracer for a few
calls as well. I use full-blown stepping around only in exceptional
cases on my own code and a little more often on code from other people.
(though I hardly ever poke around in code I receive to reproduce
bugs).

There is already some stuff on the twiki web on this.  There is a
good point extending that.

	Cheers --- Jan