<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=US-ASCII"> <meta name="generator" content="hevea 2.05"> <meta name="Author" content="Daniel Diaz"> <meta name="Keywords" content="GNU Prolog, manual, Prolog, compiler, constraints, finite domains"> <link rel="icon" type="image/x-icon" href="/gprolog.ico"><link rel="stylesheet" type="text/css" href="gprolog.css"> <title>Introduction</title> </head> <body TEXT=black BGCOLOR=white> <a href="gprolog010.html"><img src="contents_motif.gif" alt="Up"></a> <a href="gprolog012.html"><img src="next_motif.gif" alt="Next"></a> <hr> <h3 class="subsection" id="sec23">5.1  Introduction</h3> <p> The GNU Prolog debugger provides information concerning the control flow of the program. The debugger can be fully used on consulted predicates (i.e. byte-code). For native compiled code only the calls/exits are traced, no internal behavior is shown. Under the debugger it is possible to exhaustively trace the execution or to set spy-points to only debug a specific part of the program. Spy-points allow the user to indicate on which predicates the debugger has to stop to allow the user to interact with it. The debugger uses the “procedure box control flow model”, also called the Byrd Box model since it is due to Lawrence Byrd.</p> <hr class="c011"> Copyright (C) 1999-2013 Daniel Diaz Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. <a href="index.html#copyright">More about the copyright</a> <hr> <a href="gprolog010.html"><img src="contents_motif.gif" alt="Up"></a> <a href="gprolog012.html"><img src="next_motif.gif" alt="Next"></a> </body> </html>
distrib
>
Mageia
>
5
>
i586
>
media
>
core-release
>
by-pkgid
>
dd944237d71cf5527cc206c9e89c95e0
>
files
>
57
