When you enter the Debugger tool, the Condition area displays a message describing the error. The Restarts menu lists a number of restart options, which offer you different ways to continue execution.
fubar) at the Listener prompt.
A number of restarts are displayed that offer you different ways in which to proceed. These are the same options as those displayed at the command line debugger before you invoked the debugger tool.
Two special restarts can be chosen: the abort and continue restarts. These are indicated by the prefixes (abort) and (continue) respectively. As a shortcut, you can use the Abort or Continue toolbar buttons to invoke them, instead of choosing the appropriate menu command.
In the case of the continue restart, different operations are performed in different circumstances. In this example, you can evaluate the form again. If you first set the variable to some value, and then invoke the continue restart, the debugger is exited.
fubar as follows:
(setq fubar 12)
The debugger tool disappears, and the command line debugger is exited in the Listener, and the value 12 is returned; the correct result if the variable had been bound in the first place.
You can also click Abort to invoke the abort restart. This restart always exits the current level of the debugger and returns to the previous one, ignoring the error which caused the present invocation of the debugger.
In general, you should use the continue restart if you have fixed the problem and want to continue execution, and the abort restart if you want to ignore the problem completely and stop execution.
LispWorks IDE User Guide (Unix version) - 12 Feb 2015