On Jueves 20 Noviembre 2008, Benjamin Lambert wrote:
Dear SLIME,
I've been having this problem, in one way or another, for a long time now. But, I think, I'd always found some combination of SLIME and SBCL that worked together. Now, I'm stuck.
I'm running SBCL 1.0.22, on Linux x86-64. I believe I have a very recent version of SLIME, checked out from CVS within the last few weeks.
SLIME seems to work fine with the SBCL binary distribution. But, when I recompile it with ":sb-thread" enabled, Slime won't start. So, it seems that the threading is interfering with SLIME?
When I starts Slime, this is the error I see see this in mini-buffer: List connection closed unexpectedly: exited abnormally with code 256 And, in the *inferior-lisp* buffer I see: " Implicitly creating new generic function STREAM-READ-CHAR-WILL- HANG-P. ; loading #P"/home/benlambert/.slime/fasl/2008-11-02/sbcl-1.0.22-linux- x86-64/swank.fasl" WARNING: These Swank interfaces are unimplemented: (CALLS-WHO DISASSEMBLE-FRAME SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-SPECIALIZES) ;; Swank started at port: 41099. 41099
Process inferior-lisp hangup"
I'm glad to provide any more debugging information that I can. Is there any fix, or workaround, that I could try? That is, short of just not using threading.
Thanks for any help you might be able to give.
Check if this relevant to you: http://common-lisp.net/pipermail/slime-devel/2006-March/012444.html
Ben Lambert
P.S. I'm a long time user and a big fan of Slime. Good work, all.
-- Benjamin Lambert Graduate Student of Computer Science Carnegie Mellon University www.cs.cmu.edu/~belamber Mobile: 617-869-1844