Hi,
How do I abort the debugger and return to the repl? When I enter an expression that is invalid into the repl slime opens a debug buffer:
CL-USER> (teddybear)
Opens a debugger containing:
Undefined function NO-SUCH-FUNCTION called with arguments () . [Condition of type CCL::UNDEFINED-FUNCTION-CALL]
Restarts: 0: [CONTINUE] Retry applying NO-SUCH-FUNCTION to NIL. 1: [USE-VALUE] Apply specified function to NIL this time. 2: [STORE-VALUE] Specify a function to use as the definition of NO-SUCH-FUNCTION. 3: [ABORT] Abort handling SLIME request. 4: [ABORT-BREAK] #<RESTART ABORT-BREAK #xA4BE06> 5: [ABORT] #<RESTART ABORT #xA4BE2E>
Backtrace: 0: (CCL::CALL-CHECK-REGS 'NO-SUCH-FUNCTION) --more--
In that buffer there is a list of restarts, the bottom three which seems like they might return to the repl. If I select number 3 I get another debugger, and if I continue to select the one described as "Abort handling SLIME request." openmcl eventually crash and enter the openmcl kernel debugger.
Restart 4 & 5 aborts, but all I get is (for restart 5, but the result for restart 4 is similar):
Invoking restart: #<RESTART ABORT #xA4BE2E> ; Evaluation aborted
I don't get any new repl-prompt.
What is going on? I run a version of slime updated just a few minutes ago and openmcl 0.14.2-p1.
// Anders
Anders Conradi beque@telia.com writes:
How do I abort the debugger and return to the repl?
Taking the ABORT restart should give you a new prompt. This is a bug. I don't have access to OpenMCL currently so I can't check it out, but hopefully someone else can.
I know we previously had a problem with restarts in SLDB on OpenMCL 0.14 but Gary and Alan fixed that one last month.
Meanwhile it could be interesting to see the contents of your *slime-events* buffer immediately after reproducing this bug.
-Luke
Luke Gorrie luke@bluetail.com writes:
Anders Conradi beque@telia.com writes:
How do I abort the debugger and return to the repl?
Taking the ABORT restart should give you a new prompt. This is a bug. I don't have access to OpenMCL currently so I can't check it out, but hopefully someone else can.
This is a bug in OpenMCL regarding with-simple-restart (which creates the ABORT restart).
Marco Baringer mb@bese.it writes:
Luke Gorrie luke@bluetail.com writes:
Taking the ABORT restart should give you a new prompt. This is a bug. I don't have access to OpenMCL currently so I can't check it out, but hopefully someone else can.
This is a bug in OpenMCL regarding with-simple-restart (which creates the ABORT restart).
Even in the latest version? The release notes 0.14.2 mention this bugfix:
Applying INVOKE-RESTART to a restart established by WITH-SIMPLE-RESTART didn't invoke the restart (fixed by Bryan O'Connor.)
-Luke
Luke Gorrie luke@bluetail.com writes:
Even in the latest version? The release notes 0.14.2 mention this bugfix:
at least in 0.14.2-p1, i haven't checked CVS lately.
On Tue, 22 Jun 2004, Luke Gorrie wrote:
Marco Baringer mb@bese.it writes:
Luke Gorrie luke@bluetail.com writes:
Taking the ABORT restart should give you a new prompt. This is a bug. I don't have access to OpenMCL currently so I can't check it out, but hopefully someone else can.
This is a bug in OpenMCL regarding with-simple-restart (which creates the ABORT restart).
Even in the latest version? The release notes 0.14.2 mention this bugfix:
Applying INVOKE-RESTART to a restart established by WITH-SIMPLE-RESTART didn't invoke the restart (fixed by Bryan O'Connor.)
-Luke
INVOKE-RESTART was indeed fixed a while ago.
It would have made far too much sense to have fixed the same bug in INVOKE-RESTART-INTERACTIVELY at the same time (and I assume that SLIME's calling INVOKE-RESTART-INTERACTIVELY.) As of a few minutes ago, INVOKE-RESTART-INTERACTIVELY seems to be fixed in OpenMCL's CVS; I hope that this fixes the problem.