Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
cmucl-copy
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Richard M Kreuter
cmucl-copy
Commits
ec4a2af4
Commit
ec4a2af4
authored
18 years ago
by
rtoy
Browse files
Options
Downloads
Patches
Plain Diff
Document :wherein-only option for trace. Add a note on how to trace
local flet and labels functions.
parent
b2391606
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/cmu-user/debugger.tex
+12
-2
12 additions, 2 deletions
docs/cmu-user/debugger.tex
with
12 additions
and
2 deletions
docs/cmu-user/debugger.tex
+
12
−
2
View file @
ec4a2af4
...
...
@@ -1013,7 +1013,12 @@ function entry or exit.
printed at the beginning of each line of output. Printing verbosity
of arguments and return values is controlled by
\vindexed
{
debug-print-level
}
and
\vindexed
{
debug-print-length
}
.
Local functions defined by
\code
{
flet
}
and
\code
{
labels
}
can be
traced using the syntax
\code
{
(flet f f1 f2 ...)
}
or
\code
{
(labels f
f1 f2 ...)
}
where
\code
{
f
}
is the
\code
{
flet
}
or
\code
{
labels
}
function we want to trace and
\code
{
f1
}
,
\code
{
f2
}
, are the
functions containing the local function
\code
{
f
}
.
Invidiual methods can also be traced using the syntax
\code
{
(method
<name> <qualifiers> <specializers>)
}
.
See~
\ref
{
sec:method-tracing
}
for more information.
...
...
@@ -1045,7 +1050,12 @@ function entry or exit.
function (i.e. it would appear in a backtrace.) Anonymous
functions have string names like
\code
{
"DEFUN FOO"
}
. Individual
methods can also be traced. See section~
\ref
{
sec:method-tracing
}
.
\item
[\kwd{wherein-only} \var{names}]
If specified, this is just
like
\kwd
{
wherein
}
, but trace produces output only if the
immediate caller of the traced function is one of the functions
listed in
\var
{
names
}
.
\item
[
\kwd
{
break
}
\var
{
form
}
,
\kwd
{
break-after
}
\var
{
form
}
,
\kwd
{
break-all
}
\var
{
form
}
] If specified, and
\var
{
form
}
evaluates
to true, then the debugger is invoked at the start of the
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment