Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
cmucl
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
Carl Shapiro
cmucl
Commits
a13747e0
Commit
a13747e0
authored
22 years ago
by
toy
Browse files
Options
Downloads
Patches
Plain Diff
Better describe using :encapsulate for tracing. From rpgoldman.
parent
fd4526c8
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/cmu-user/debugger.tex
+25
-1
25 additions, 1 deletion
docs/cmu-user/debugger.tex
with
25 additions
and
1 deletion
docs/cmu-user/debugger.tex
+
25
−
1
View file @
a13747e0
...
@@ -870,7 +870,7 @@ Displays all the frames from the current to the bottom. Only shows
...
@@ -870,7 +870,7 @@ Displays all the frames from the current to the bottom. Only shows
\end{Lentry}
\end{Lentry}
\section
{
Breakpoint Commands
}
\section
{
Breakpoint Commands
}
\cindex
{
breakpoints
}
\cmucl
{}
supports setting of breakpoints inside compiled functions and
\cmucl
{}
supports setting of breakpoints inside compiled functions and
stepping of compiled code. Breakpoints can only be set at at known
stepping of compiled code. Breakpoints can only be set at at known
...
@@ -1073,7 +1073,31 @@ function entry or exit.
...
@@ -1073,7 +1073,31 @@ function entry or exit.
otherwise. When encapsulation is used, forms are
{
\it
not
}
otherwise. When encapsulation is used, forms are
{
\it
not
}
evaluated in the function's lexical environment, but
evaluated in the function's lexical environment, but
\code
{
debug:arg
}
can still be used.
\code
{
debug:arg
}
can still be used.
Note that if you trace using
\kwd
{
encapsulate
}
, you will
only get a trace or breakpoint at the outermost call to the traced
function, not on recursive calls.
\end{Lentry}
\end{Lentry}
In the case of functions where the known return convention is used
to optimize, encapsulation may be necessary in order to make
tracing work at all. The symptom of this occurring is an error
stating
\begin{example}
Error in function
\var
{
foo
}
: :FUNCTION-END breakpoints are
currently unsupported for the known return convention.
\end{example}
in such cases we recommend using
\code
{
(trace
\var
{
foo
}
:encapsulate
t)
}
\cpsubindex
{
tracing
}{
errors
}
\cpsubindex
{
breakpoints
}{
errors
}
\cpsubindex
{
errors
}{
breakpoints
}
\cindex
{
function-end breakpoints
}
\cpsubindex
{
breakpoints
}{
function-end
}
\kwd
{
condition
}
,
\kwd
{
break
}
and
\kwd
{
print
}
forms are evaluated in
\kwd
{
condition
}
,
\kwd
{
break
}
and
\kwd
{
print
}
forms are evaluated in
the lexical environment of the called function;
\code
{
debug:var
}
and
the lexical environment of the called function;
\code
{
debug:var
}
and
...
...
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