From ok@atlas.otago.ac.nz Tue Jan 30 01:47:41 2001
Received: from atlas.otago.ac.nz (atlas.otago.ac.nz [139.80.32.250])
	by swi.psy.uva.nl (8.11.2/8.11.2) with ESMTP id f0U0leZ05724
	for <prolog@swi.psy.uva.nl>; Tue, 30 Jan 2001 01:47:40 +0100 (MET)
Received: (from ok@localhost)
	by atlas.otago.ac.nz (8.9.3/8.9.3) id NAA04898;
	Tue, 30 Jan 2001 13:47:27 +1300 (NZDT)
Date: Tue, 30 Jan 2001 13:47:27 +1300 (NZDT)
From: "Richard A. O'Keefe" <ok@atlas.otago.ac.nz>
Message-Id: <200101300047.NAA04898@atlas.otago.ac.nz>
To: prolog@swi.psy.uva.nl, sunriseat28@yahoo.com
Subject: Re:  [SWIPL] The use of 'spy' in SWI-Prolog

David Yang wrote:
	I have prolems in tracing predicates in SWI-Prolog. I
	spy on one predicate but all other predicates get
	spied on too.

If there is a spypoint on a predicate, then
 - tracing is switched ON when control enters a call to that predicate
 - tracing is NOT switched OFF unless you say so
 - you can "leap" to the next spypoint using "l"
 - non-spied predicates are NOT removed from the trace.

It sounds as though you expect non-spied predicates to be hidden.
Thing is, you have the choice of seeing them ("creep") or not ("leap").

This is really just like break-points in a C debugger.
When control reaches a break-point, the debugger "wakes up", but if
you then start single-stepping ("creeping" in Prolog terminology)
a C debugger won't hide all the statements that don't have break-points.
But you _can_ continue to the next break-point, and that's like "leap".

