... or maybe I'm just doing something wrong, but every time a break is evaluated, the following happens:
CL-USER> (break)
Error: No applicable methods for #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> with args (#<ENVIRONMENT:TTY-ENVIRONMENT 10218C3F> :CONDITION #<SIMPLE-ERROR 100ACE73> :RESTARTS (#<RESTART CONTINUE 100ABE1B> #<RESTART CONTINUE 100F55F7> #<RESTART CONTINUE 100FF51F> #<RESTART CONTINUE 10107FEB> #<RESTART CONTINUE 100E9EDF> #<RESTART CONTINUE 100E04F3> #<RESTART CONTINUE 100E4427> #<RESTART CONTINUE 10CEFB8B> #<RESTART ABORT 10CEFBC3>)) 1 (continue) Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 2 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 3 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 4 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 5 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 6 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 7 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 8 Call #<STANDARD-GENERIC-FUNCTION ENVIRONMENT-INTERNALS:ENVIRONMENT-DISPLAY-NOTIFIER 102376E2> again 9 Return from break. 10 (abort) Return to SLIME toplevel.
Type :b for backtrace, :c <option number> to proceed, or :? for other options
CL-USER 6 : 9 >
I have tried bothe with the latest SLIME and FAIRLY-STABLE and both Lispworks 4.2 and 4.3, but it breaks every time I try. I'm baffled, and any hints about what might be wrong is most welcome.
I'm running Lispworks/Solaris and Emacs 21.2.1 btw.
I have tried playing around in order to understand what goes wrong, an it seems to me like Lispworks is in error. However breaking works fine outside of SLIME, ie. from the *inferior-lisp*. Here's the backtrace in case anyone can see anything interesting.
Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to ERROR Call to CERROR Call to (METHOD NO-APPLICABLE-METHOD (T)) Call to CLOS::APPLY-NO-APPLICABLE-METHOD Call to ENVIRONMENT:DISPLAY-NOTIFIER Call to INVOKE-DEBUGGER Call to BREAK Call to EVAL Call to SWANK::EVAL-REGION Call to SWANK:LISTENER-EVAL Call to EVAL Call to SWANK::EVAL-FOR-EMACS Call to FUNCALL Call to SWANK::READ-FROM-EMACS Call to (SUBFUNCTION 2 SWANK::HANDLE-REQUEST) Call to SWANK::CALL-WITH-REDIRECTED-IO Call to SWANK::HANDLE-REQUEST Call to (SUBFUNCTION 1 SWANK::DISPATCH-EVENT) Call to (SUBFUNCTION MP::PROCESS-SG-FUNCTION MP::INITIALIZE-PROCESS-STACK)
CL-USER 7 : 9 >
Bjørn Nordbø wrote:
... or maybe I'm just doing something wrong, but every time a break is evaluated, the following happens:
Sorry to bother you all again, but after some reading and thinking, I have come to believe that I am mostly misguided. As break rebinds *debugger-hook* to NIL, it will never cause SLDB to be invoked, and except for all the Lispworks errors everything is working fine.
If this is correct, I have one simple question:
How do I set a breakpoint for SLDB in a source fragment (ie. what do I use instead of break)?
And thanks for the SLIME manual by the way; a great read! :-)