zl:1 - FTP

619 dbg :with-erri ng-frame
You also use sys:with-aborts-enabled when you don't need the automatic
sys:without-aborts created by unwind-protect. For example,
(unwind-protect (do-something)
(sys:with-aborts-enabled (unwind-protect)
(clean-up-something»)
If the cleanup form contained an explicit sys:without-aborts, to specify. a
specific reason why it should not be aborted instead of the default generic
reason, the sys:with-aborts-enabled must specify the identifiers of both the
explicit and the implicit sys:without-aborts. For example,
(unwind-protect (do-something)
(sys:without-aborts
(faa HThe floor is being cleaned up.
Aborting now could leave a serious mess that will cause
trouble if you enter this room again later. H )
(do-something-not-abortable)
(sys:with-aborts-enabled (faa unwind-protect)
(do-something-abortable»»
See the macro sys:without-aborts, page 620.
For a table of related items: See the section "Nonlocal Exit Functions" in
Symbolics Common Lisp: Language Concepts.
dbg:with-erring-frame (frame-uar condition) &body body Macro
dbg:with-erring-frame sets up an environment with appropriate bindings
for using the rest of the functions that examine the stack. It binds
frame-uar with the frame pointer to the stack frame that signalled the error.
frame-uar is always a pointer to an interesting stack frame.
condition is the condition object for the error, which was the first argument
given to the condition-bind handler.
(defun my-handler (condition-object)
(dbg:with-erring-frame (frame-ptr condition-object)
body ... ) )
Inside body, the variable frame-var is bound to the frame pointer of the
frame that got the error.
Sometimes, you might want to use the special variable
dbg:*current-frame* as frame-uar because some functions expect this special
variable to be bound to the stack frame that signalled the error.
You would use this special variable if you are sending the
:bug-report-description message to the condition object, which calls stack-
•