Dear Maintainer,

Slime 2:2.28+dfsg-1 will result in
Lisp connection closed unexpectedly: connection broken by remote peer
as soon as I evaluate a Lisp file.

../../usr/share/emacs/site-lisp/elpa/slime-2.28/contrib/slime-references.el: Warning: ‘case’ is an obsolete alias (as of 27.1); use ‘cl-case’ instead.
Polling "/tmp/slime.87709" .. 1 (Abort with ‘M-x slime-abort-connection’.)
Polling "/tmp/slime.87709" .. 2 (Abort with ‘M-x slime-abort-connection’.)
Polling "/tmp/slime.87709" .. 3 (Abort with ‘M-x slime-abort-connection’.)
Connecting to Swank on port 42941..
Connected. Let the hacking commence!
Open my.lisp
Lisp connection closed unexpectedly: connection broken by remote peer

A work around is to go back to 2:2.27 where this disconnect doesn't occur.

some more info


emacs -q --debug-init

evaluate this:

(require 'slime)
(setq inferior-lisp-program "sbcl")

m-x slime

load some lisp code, and see the connection closed.

This is reported in *Messages*:

Lisp connection closed unexpectedly: connection broken by remote peer

Error during redisplay: (eval (slime-modeline-string)) signaled (error "Connection closed.") [2 times]



M-x slime also returns 19 warnings from the native compiler..

It looks like I managed to resolve this by cleaning out

.cache/common-lisp/

which forces the rebuilding of

.cache/common-lisp/2.3.7.debian-linux-x64/

when I restarted Emacs, and M-x slime