/usr/lib/swi-prolog/doc/Manual/debug.html is in swi-prolog-nox 6.6.4-2ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>SWI-Prolog 7.1.10 Reference Manual: Section A.10</title><link rel="home" href="index.html">
<link rel="contents" href="Contents.html">
<link rel="index" href="DocIndex.html">
<link rel="summary" href="summary.html">
<link rel="previous" href="csv.html">
<link rel="next" href="gensym.html">
<style type="text/css">
/* Style sheet for SWI-Prolog latex2html
*/
dd.defbody
{ margin-bottom: 1em;
}
dt.pubdef, dt.multidef
{ color: #fff;
padding: 2px 10px 0px 10px;
margin-bottom: 5px;
font-size: 18px;
vertical-align: middle;
overflow: hidden;
}
dt.pubdef { background-color: #0c3d6e; }
dt.multidef { background-color: #ef9439; }
.bib dd
{ margin-bottom: 1em;
}
.bib dt
{ float: left;
margin-right: 1.3ex;
}
pre.code
{ margin-left: 1.5em;
margin-right: 1.5em;
border: 1px dotted;
padding-top: 5px;
padding-left: 5px;
padding-bottom: 5px;
background-color: #f8f8f8;
}
div.navigate
{ text-align: center;
background-color: #f0f0f0;
border: 1px dotted;
padding: 5px;
}
div.title
{ text-align: center;
padding-bottom: 1em;
font-size: 200%;
font-weight: bold;
}
div.author
{ text-align: center;
font-style: italic;
}
div.abstract
{ margin-top: 2em;
background-color: #f0f0f0;
border: 1px dotted;
padding: 5px;
margin-left: 10%; margin-right:10%;
}
div.abstract-title
{ text-align: center;
padding: 5px;
font-size: 120%;
font-weight: bold;
}
div.toc-h1
{ font-size: 200%;
font-weight: bold;
}
div.toc-h2
{ font-size: 120%;
font-weight: bold;
margin-left: 2em;
}
div.toc-h3
{ font-size: 100%;
font-weight: bold;
margin-left: 4em;
}
div.toc-h4
{ font-size: 100%;
margin-left: 6em;
}
span.sec-nr
{
}
span.sec-title
{
}
span.pred-ext
{ font-weight: bold;
}
span.pred-tag
{ float: right;
padding-top: 0.2em;
font-size: 80%;
font-style: italic;
color: #fff;
}
div.caption
{ width: 80%;
margin: auto;
text-align:center;
}
/* Footnotes */
.fn {
color: red;
font-size: 70%;
}
.fn-text, .fnp {
position: absolute;
top: auto;
left: 10%;
border: 1px solid #000;
box-shadow: 5px 5px 5px #888;
display: none;
background: #fff;
color: #000;
margin-top: 25px;
padding: 8px 12px;
font-size: larger;
}
sup:hover span.fn-text
{ display: block;
}
/* Lists */
dl.latex
{ margin-top: 1ex;
margin-bottom: 0.5ex;
}
dl.latex dl.latex dd.defbody
{ margin-bottom: 0.5ex;
}
/* PlDoc Tags */
dl.tags
{ font-size: 90%;
margin-left: 5ex;
margin-top: 1ex;
margin-bottom: 0.5ex;
}
dl.tags dt
{ margin-left: 0pt;
font-weight: bold;
}
dl.tags dd
{ margin-left: 3ex;
}
td.param
{ font-style: italic;
font-weight: bold;
}
/* Index */
dt.index-sep
{ font-weight: bold;
font-size: +1;
margin-top: 1ex;
}
/* Tables */
table.center
{ margin: auto;
}
table.latex
{ border-collapse:collapse;
}
table.latex tr
{ vertical-align: text-top;
}
table.latex td,th
{ padding: 2px 1em;
}
table.latex tr.hline td,th
{ border-top: 1px solid black;
}
table.frame-box
{ border: 2px solid black;
}
</style>
</head>
<body style="background:white">
<div class="navigate"><a class="nav" href="index.html"><img src="home.gif" alt="Home"></a>
<a class="nav" href="Contents.html"><img src="index.gif" alt="Contents"></a>
<a class="nav" href="DocIndex.html"><img src="yellow_pages.gif" alt="Index"></a>
<a class="nav" href="summary.html"><img src="info.gif" alt="Summary"></a>
<a class="nav" href="csv.html"><img src="prev.gif" alt="Previous"></a>
<a class="nav" href="gensym.html"><img src="next.gif" alt="Next"></a>
</div>
<h2 id="sec:debug"><a id="sec:A.10"><span class="sec-nr">A.10</span> <span class="sec-title">library(debug):
Print debug messages and test assertions</span></a></h2>
<p><a id="sec:debug"></a>
<dl class="tags">
<dt class="tag">author</dt>
<dd>
Jan Wielemaker
</dd>
</dl>
<p>This library is a replacement for <a class="pred" href="format.html#format/3">format/3</a>
for printing debug messages. Messages are assigned a <i>topic</i>. By
dynamically enabling or disabling topics the user can select desired
messages. Debug statements are removed when the code is compiled for
optimization.
<p>See manual for details. With XPCE, you can use the call below to
start a graphical monitoring tool.
<pre class="code">
?- prolog_ide(debug_monitor).
</pre>
<p>Using the predicate <a class="pred" href="debug.html#assertion/1">assertion/1</a>
you can make assumptions about your program explicit, trapping the
debugger if the condition does not hold.
<dl class="latex">
<dt class="pubdef"><span class="pred-tag">[semidet]</span><a id="debugging/1"><strong>debugging</strong>(<var>+Topic</var>)</a></dt>
<dt class="pubdef"><span class="pred-tag">[nondet]</span><a id="debugging/1"><strong>debugging</strong>(<var>-Topic</var>)</a></dt>
<dt class="pubdef"><span class="pred-tag">[nondet]</span><a id="debugging/2"><strong>debugging</strong>(<var>?Topic,
?Bool</var>)</a></dt>
<dd class="defbody">
Examine debug topics. The form <code>debugging(+Topic)</code> may be
used to perform more complex debugging tasks. A typical usage skeleton
is:
<pre class="code">
( debugging(mytopic)
-> <perform debugging actions>
; true
),
...
</pre>
<p>The other two calls are intended to examine existing and enabled
debugging tokens and are typically not used in user programs.</dd>
<dt class="pubdef"><span class="pred-tag">[det]</span><a id="debug/1"><strong>debug</strong>(<var>+Topic</var>)</a></dt>
<dt class="pubdef"><span class="pred-tag">[det]</span><a id="nodebug/1"><strong>nodebug</strong>(<var>+Topic</var>)</a></dt>
<dd class="defbody">
Add/remove a topic from being printed. <code>nodebug(_)</code> removes
all topics. Gives a warning if the topic is not defined unless it is
used from a directive. The latter allows placing debug topics at the
start of a (load-)file without warnings.
<p>For <a class="pred" href="debug.html#debug/1">debug/1</a>, <var>Topic</var>
can be a term <var>Topic</var> <var>></var> Out, where Out is either
a stream or stream-alias or a filename (atom). This redirects debug
information on this topic to the given output.</dd>
<dt class="pubdef"><span class="pred-tag">[det]</span><a id="list_debug_topics/0"><strong>list_debug_topics</strong></a></dt>
<dd class="defbody">
List currently known debug topics and their setting.</dd>
<dt class="pubdef"><span class="pred-tag">[det]</span><a id="debug_message_context/1"><strong>debug_message_context</strong>(<var>+What</var>)</a></dt>
<dd class="defbody">
Specify additional context for debug messages. <var>What</var> is one of
+Context or -Context, and Context is one of <code>thread</code>, <code>time</code>
or
<code>time(Format)</code>, where Format is a format specification for
<a class="pred" href="system.html#format_time/3">format_time/3</a>
(default is <code>%T.%3f</code>). Initially, <a class="pred" href="debug.html#debug/3">debug/3</a>
shows only thread information.</dd>
<dt class="pubdef"><span class="pred-tag">[det]</span><a id="debug/3"><strong>debug</strong>(<var>+Topic,
+Format, :Args</var>)</a></dt>
<dd class="defbody">
<var>Format</var> a message if debug topic is enabled. Similar to <a class="pred" href="format.html#format/3">format/3</a>
to <code>user_error</code>, but only prints if <var>Topic</var> is
activated through
<a class="pred" href="debug.html#debug/1">debug/1</a>. <var>Args</var>
is a meta-argument to deal with goal for the @-command. Output is first
handed to the hook
<a class="pred" href="debug.html#prolog:debug_print_hook/3">prolog:debug_print_hook/3</a>.
If this fails, <var>Format</var>+<var>Args</var> is translated to text
using the message-translation (see
<a class="pred" href="exception.html#print_message/2">print_message/2</a>)
for the term <code>debug(Format, Args)</code> and then printed to every
matching destination (controlled by <a class="pred" href="debug.html#debug/1">debug/1</a>)
using <a class="pred" href="exception.html#print_message_lines/3">print_message_lines/3</a>.
<p>The message is preceded by '% ' and terminated with a newline.
<dl class="tags">
<dt class="tag">See also</dt>
<dd>
<a class="pred" href="format.html#format/3">format/3</a>.
</dd>
</dl>
</dd>
<dt class="multidef"><span class="pred-tag">[semidet,multifile]</span><a id="prolog:debug_print_hook/3"><span class="module">prolog</span>:<strong>debug_print_hook</strong>(<var>+Topic,
+Format, +Args</var>)</a></dt>
<dd class="defbody">
Hook called by <a class="pred" href="debug.html#debug/3">debug/3</a>.
This hook is used by the graphical frontend that can be activated using <a class="pred" href="idepreds.html#prolog_ide/1">prolog_ide/1</a>:
<pre class="code">
?- prolog_ide(debug_monitor).
</pre>
</dd>
<dt class="pubdef"><span class="pred-tag">[det]</span><a id="assertion/1"><strong>assertion</strong>(<var>:Goal</var>)</a></dt>
<dd class="defbody">
Acts similar to C <code>assert()</code> macro. It has no effect if <var>Goal</var>
succeeds. If <var>Goal</var> fails or throws an exception, the following
steps are taken:
<p>
<ul class="latex">
<li>call <a class="pred" href="debug.html#prolog:assertion_failed/2">prolog:assertion_failed/2</a>.
If <a class="pred" href="debug.html#prolog:assertion_failed/2">prolog:assertion_failed/2</a>
fails, then:
<p>
<ul class="latex">
<li>If this is an interactive toplevel thread, print a message, the
stack-trace, and finally trap the debugger.
<li>Otherwise, throw <code>error(assertion_error(Reason, G),_)</code>
where Reason is one of <code>fail</code> or the exception raised.
</ul>
</ul>
</dd>
<dt class="multidef"><span class="pred-tag">[semidet,multifile]</span><a id="prolog:assertion_failed/2"><span class="module">prolog</span>:<strong>assertion_failed</strong>(<var>+Reason,
+Goal</var>)</a></dt>
<dd class="defbody">
This hook is called if the <var>Goal</var> of <a class="pred" href="debug.html#assertion/1">assertion/1</a>
fails. <var>Reason</var> is unified with either <code>fail</code> if <var>Goal</var>
simply failed or an exception call otherwise. If this hook fails, the
default behaviour is activated. If the hooks throws an exception it will
be propagated into the caller of <a class="pred" href="debug.html#assertion/1">assertion/1</a>.
</dd>
</dl>
<p></body></html>
|