Allegro CL FAQ 3.7: The stepper

3.7: The stepper

#Q 3.7-1) The step macro does not step through compiled code, but only sees interpreted functions. How can I step through compiled functions?

Q 3.7-1) The step macro does not step through compiled code, but only sees interpreted functions. How can I step through compiled functions?

A 3.7-1) Obtain the patch p0a003.nnn, (where nnn is the latest version) and build or load it into an Allegro 5.0 lisp. This patch implements the excl:step-fun macro, which is similar to step in most ways.

Warning: do not mix step and excl:step-fun operations, other than the :scont and :sover top-level commands; to stop function-level stepping, always use (excl:step-fun nil). There is no top-level command associated with excl:step-fun; it is intended that excl:step-fun might replace the old stepper in some future release. Here is a description of excl:step-fun.

step-fun

Macro

Arguments: &rest args

Package: excl

With no arguments or an argument of nil, stepping is disabled globally, regardless of the current stepping state.

With an argument of t, function-level stepping is enabled globally.

If the first argument is a symbol, then all arguments are assumed to be functions wherein stepping should occur. Currently only symbolic function names are allowed.

If the first argument is a list, it is assumed to be a form to step through. Function-level stepping is enabled during the execution of that form.

During function-level stepping, the :scont and :sover top-level commands work as documented for the :step command. Do not use the :step command or the step macro while doing function-level stepping; the two implementations are incompatible.