Newly-installed Debian unstable Linux zotz 2.6.11-1-686 #1 Mon Jun 20 22:00:38 MDT 2005 i686 GNU/Linux SBCL 0.9.1.41, SLIME from CVS
Does not switch from *inferior-lisp* frame to listener in either mule or nomule XEmacs; hangs with e.g. ;; Swank started at port: 1033.
In the repl window, there is a message like debugger invoked on a UNDEFINED-FUNCTION in thread 5710: The function SWANK:SWANK-DEBUGGER-HOOK is undefined. and then a prompt, but entering anything at the prompt results in no action but a message in the modeline ; pipelined request... (swank:listener-eval " ")
C-h l shows Loading regexp-opt...done Loading regexp-opt... Loading cl-indent...done Loading cl-indent... Connecting to Swank on port 1035.. Polling "/tmp/liam/slime.5640".. (Abort with `M-x slime-abort-connection'.) Polling "/tmp/liam/slime.5640".. (Abort with `M-x slime-abort-connection'.) Polling "/tmp/liam/slime.5640".. (Abort with `M-x slime-abort-connection'.) Polling "/tmp/liam/slime.5640".. (Abort with `M-x slime-abort-connection'.) Polling "/tmp/liam/slime.5640".. (Abort with `M-x slime-abort-connection'.) Polling "/tmp/liam/slime.5640".. (Abort with `M-x slime-abort-connection'.) Polling "/tmp/liam/slime.5640".. (Abort with `M-x slime-abort-connection'.)
I've had no problems with slime on other computers, even other computers on this network. Any ideas? Hints on how to debug?
Thanks.
Liam
"Liam M. Healy" lnp@healy.washington.dc.us writes:
SBCL 0.9.1.41, SLIME from CVS
I'm not utterly convinced this is a combination currently supported if the SBCL is built with threads. Certainly the symptoms you describe could be a mismatch of expectations.
Christophe
I probalbly posted this before. Does anyone have encountered problems with that combination I'm using SBCL 0.9.2.51 and the CVS-Slime. the message I got is: implicitly creating new generic function STREAM-READ-CHAR-WILL-HANG-P ;; loading #P"/home/frido/.slime/fasl/sbcl-0.9.2.51-linux-x86-64/swank.fasl" WARNING: These Swank interfaces are unimplemented: (ACTIVATE-STEPPING CALLS-WHO DISASSEMBLE-FRAME INSPECT-FOR-EMACS RESTART-FRAME SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-BINDS WHO-CALLS WHO-MACROEXPANDS WHO-REFERENCES WHO-SETS WHO-SPECIALIZES) T * ;; Swank started at port: 33038.
33038 * Process inferior-lisp hangup
Is there anything I can do to get a multithreaded SBCL running with Slime?
Regards Friedrich
On Monday 18 July 2005 10:03, Friedrich Dominicus wrote:
I probalbly posted this before. Does anyone have encountered problems with that combination I'm using SBCL 0.9.2.51 and the CVS-Slime. the message I got is: implicitly creating new generic function STREAM-READ-CHAR-WILL-HANG-P ;; loading #P"/home/frido/.slime/fasl/sbcl-0.9.2.51-linux-x86-64/swank.fasl" WARNING: These Swank interfaces are unimplemented: (ACTIVATE-STEPPING CALLS-WHO DISASSEMBLE-FRAME INSPECT-FOR-EMACS RESTART-FRAME SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-BINDS WHO-CALLS WHO-MACROEXPANDS WHO-REFERENCES WHO-SETS WHO-SPECIALIZES) T
- ;; Swank started at port: 33038.
33038
Process inferior-lisp hangup
Is there anything I can do to get a multithreaded SBCL running with Slime?
Regards Friedrich _______________________________________________ slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
I'm sorry for replying so late. This problem was discussed on sbcl-devel some time ago. AFAICT it is present since the sbcl pthread merge (0.9.1.59) under some kernels.
The immediate cause is emacs sending a SIGHUP to sbcl that does not have a handler and promptly exits which is the right behaviour. My tests showed that even if :sigio or :fd-handler is used, the first thread exit makes emacs send sighup.
A possible workaround is:
(setq inferior-lisp-program "nohup sbcl")
or writing a little wrapper script around sbcl if you want *inferior-lisp* keep its sanity:
#!/bin/sh sbcl
But probably it is a kernel problem after all: for me the problem went away after a 2.6.8 -> 2.6.11 upgrade.
Cheers, Gábor
-
Christophe Rhodes -
Friedrich Dominicus -
Gábor Melis -
Liam M. Healy