[slime-devel] getting emacs debugger in latest slime with Allegro...?

Gary King gwking at metabang.com
Fri Oct 10 21:58:36 UTC 2008


This is with the cvs head of slime and Allegro Common Lisp.

Not always but often, when I choose to compile a file via c-x c-k, the  
compile happens and then I get tossed in the emacs lisp debugger with  
a message similar to:

Debugger entered: nil
   (condition-case error (slime-net-read) (error (debug) (slime-net- 
close process t) (error "net-read error: %S" error)))
   slime-net-read-or-lose(#<process SLIME Lisp>)
   slime-process-available-input(#<process SLIME Lisp>)
   slime-net-filter(#<process SLIME Lisp> "000029(:write-string \"; No  
value\" :repl-result)000017(:return (:ok nil) 961)")

once this has happened, just about every interaction with slime  
provides the same (or similar) bug. To stop it, I must quick the slime  
session and restart it.

This started happening a few days ago after I updated.

It's very irritating. (to say the least)
--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM








More information about the slime-devel mailing list