[slime-devel] unhooking from slime before saving sbcl core?

Michael Hannemann mrh3 at pobox.com
Sat Feb 28 01:08:35 UTC 2009


Hi all,

I'm new to SLIME, although a co-worker has been prodding me to look 
at it for a year.  I'm also new to SBCL, although I used CMUCL a fair 
amount several years ago.

I apologize if the following is a FAQ -- I scoured the manual and 
searched through the gmane archives of this list, but I could've 
missed something.


When I write a core image out from SBCL which I'm talking to via 
SLIME, then try to load it from the command line without SLIME, I get 
a long stream of warning messages.  This happens immediately on 
startup.  I've deleted my .sbclrc file so user init is not to blame. 
(Also, when I start up SBCL from the shell, this doesn't happen.)

The lisp is not dead, just injured; I can get out of the break loop. 
However, any time I get back into a break loop, I'm in trouble again.

My co-worker suggested setting *debugger-hook* to nil, so I tried 
that, to no avail.  I still get the errors (example below), and once 
I get back to a usable prompt in the lisp, I see that it's set to 
SWANK:SWANK-DEBUGGER-HOOK again.


I've copied the first chunk of what I see on startup to the end of 
this message.  This is MacOSX, SLIME from CVS a day or two ago, SBCL 
1.0.23.


Any advice?


Thanks,

Michael


---
* Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded.
0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE # {128E6F6D}>)[:EXTERNAL]
1: (BACKTRACE 536870911 #<SYNONYM-STREAM :SYMBOL SB-SYS:*TTY* {128E6DE9}>)
[...]
17: (FORMAT #<SB-SYS:FD-STREAM for \"a socket\" {10026331}> 
\"~6,'0x\")[:EXTERNAL]
18: (SWANK::ENCODE-MESSAGE (:DEBUG 0 11 (\"Couldn't write to 
#<SB-SYS:FD-STREAM for \\\"a socket\\\" {10026331}>:
   Bad file descriptor\" \"   [Condition of type 
SB-INT:SIMPLE-STREAM-ERROR]\" NIL) ((\"ABORT\" \"Return to sldb level 
10.\") [... and a lot more ...])
19: (SWANK::SLDB-LOOP 11)
20: (SWANK::SLDB-LOOP 11)[:EXTERNAL]
21: (SWANK::CALL-WITH-BINDINGS ((*PRINT-PRETTY* . T) (*PRINT-LEVEL* . 
4) (*PRINT-LENGTH* . 10) (*PRINT-CIRCLE* . T) (*PRINT-READABLY*) 
(*PRINT-PPRINT-DISPATCH* . #<SB-PRETTY:PPRINT-DISPATCH-TABLE 
{10224B19}>) (*PRINT-GENSYM* . T) (*PRINT-BASE* . 10) (*PRINT-RADIX*) 
(*PRINT-ARRAY* . T) (*PRINT-LINES*) (*PRINT-ESCAPE* . T) 
(*PRINT-RIGHT-MARGIN* . 65) (SWANK::*SLDB-BITVECTOR-LENGTH* . 25) 
(SWANK::*SLDB-STRING-LENGTH* . 50)) #<FUNCTION (LAMBDA NIL) 
{10245C55}>)
22: ((LAMBDA (SWANK-BACKEND::DEBUGGER-LOOP-FN)) #<FUNCTION (LAMBDA 
NIL) {10245C05}>)
23: (SWANK::DEBUG-IN-EMACS #<SB-INT:SIMPLE-STREAM-ERROR {12771809}>)
24: (SWANK:INVOKE-SLIME-DEBUGGER #<SB-INT:SIMPLE-STREAM-ERROR {12771809}>)
25: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION 
SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL) {12771A2D}>)
26: (SWANK:SWANK-DEBUGGER-HOOK #<SB-INT:SIMPLE-STREAM-ERROR 
{12771809}> #<unavailable argument>)
27: (INVOKE-DEBUGGER #<SB-INT:SIMPLE-STREAM-ERROR {12771809}>)
28: (INVOKE-DEBUGGER #<SB-INT:SIMPLE-STREAM-ERROR {12771809}>)[:EXTERNAL]
[... and on for hundreds of lines ...]




More information about the slime-devel mailing list