3.5 The Graphical Debugger
AllApplicationManualNameSummaryHelp

  • Documentation
    • Reference manual
      • Initialising and Managing a Prolog Project
        • The Graphical Debugger
          • Invoking the window-based debugger
            • guitracer/0
            • noguitracer/0
            • gtrace/0
            • gdebug/0
            • gspy/1
    • Packages

3.5.1 Invoking the window-based debugger

Whether the text-based or window-based debugger is used is controlled using the predicates guitracer/0 and noguitracer/0. Entering debug mode is controlled using the normal predicates for this: trace/0 and spy/1. In addition, PceEmacs prolog mode provides the command Prolog/Break at (Control-c b) to insert a break-point at a specific location in the source code.

The graphical tracer is particularly useful for debugging threads. The tracer must be loaded from the main thread before it can be used from a background thread.

guitracer
This predicate installs the above-mentioned hooks that redirect tracing to the window-based environment. No window appears. The debugger window appears as actual tracing is started through trace/0, by hitting a spy point defined by spy/1 or a break point defined using the PceEmacs command Prolog/Break at (Control-c b).
noguitracer
Disable the hooks installed by guitracer/0, reverting to normal text console-based tracing.
gtrace
Utility defined as guitracer,trace.
gdebug
Utility defined as guitracer,debug.
gspy(+Predicate)
Utility defined as guitracer,spy(Predicate).