[slime-devel] Re: trouble with connection being broken after loading an asdf system

[Alan Ruttenberg]

FYI: Tracked this down to an issue in swank-openmcl.lisp - a pathname  
rather than a string was being used in a location passed in a  
compiler note.
-Alan

On Sep 1, 2005, at 2:45 PM, Alan Ruttenberg wrote:

> This has been happening for a while - don't remember how long but  
> it's not something that has arisen in the last few days.
> I don't travel in this are of slime so perhaps one of you might  
> give me some hints on how to debug it.
>
> The symptom is a slime panic, followed by me having to control-g  
> interrupt. Then I need to do M-x slime to get it going again.
> I've including the *messages* buffer, the *slime-events* buffer,  
> and the emacs debugger stack trace below.
>
> Thanks,
> -Alan
>
> *messages*
>
> Polling "/tmp/slime.623".. (Abort with `M-x slime-abort- 
> connection'.) [22 times]
> Connecting to Swank on port 49856..
> Process bridge is installed
> Connected. Hack and be merry!
> (No files need saving)
> Performing ASDF "LOAD-OP" on system "kb"
> net-read error: (invalid-read-syntax "#")
> Lisp connection closed unexpectedly: deleted
>
> error in process filter: byte-code: PANIC!
> error in process filter: PANIC!
> Loading debug...done
> Entering debugger..
>
> Hangs, I hit control g - debugger buffer
>