reassign 517167 cl-swank found 517167 1:20090217-1 thanks Hi there! Cc:ing the slime-devel@ mailing list, since I think there is a misinterpretation about the function you use. On Thu, 26 Feb 2009 06:49:48 +0100, A.W. wrote:
Package: slime
The bug is not in the slime package, but in the cl-swank one, reassigned.
Version: 1:20090217
This is not a proper Debian version, which is always in the form $UPSTREAM_VERSION-$DEBIAN_REVISION For the next time, can you please submit bugs using the reportbug tool, as explained in the following link? http://www.debian.org/Bugs/Reporting This also helps the environment in which you have experienced the bug, e.g. versions of other dependendent packages and so on.
Starting a new swank server with the following code
(require 'asdf)
This is not needed since ASDF is loaded by default on Debian Common Lisp implementations.
(asdf:oos 'asdf:load-op 'swank)
This works as expected.
;Specifically, this line\/
What does this mean?
(swank:start-server :dont-close t)
results in the following error:
debugger invoked on a SB-INT:SIMPLE-PROGRAM-ERROR in thread #<THREAD "initial thread" RUNNING {AA6A649}>: odd number of &KEY arguments
Are you sure that `start-server' is intended to be used from a CL implementation? The source code seems to disagree with this use: --8<---------------cut here---------------start------------->8--- (defun start-server (port-file &key (style *communication-style*) (dont-close *dont-close*) (coding-system *coding-system*)) "Start the server and write the listen port number to PORT-FILE. This is the entry point for Emacs." (setup-server 0 (lambda (port) (announce-server-port port-file port)) style dont-close (find-external-format-or-lose coding-system))) --8<---------------cut here---------------end--------------->8--- Leaving the rest of your mail for the slime-devel@ mailing list.
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level.
(SWANK:START-SERVER :DONT-CLOSE)[:EXTERNAL]
A longer backtrace when trying to load the same code from stumpwm via stumpwm-mode, though I think all relevant information is the same:
odd number of &KEY arguments0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE (LAMBDA #) {B95CCAD}>)[:EXTERNAL] 1: (SB-DEBUG:BACKTRACE 100 #<SB-IMPL::STRING-OUTPUT-STREAM {B95CC59}>) 2: (BACKTRACE-STRING) 3: (ERR "~A")[:EXTERNAL] 4: (EVAL-LINE "(swank:start-server :dont-close t)") 5: (CALL-INTERACTIVELY "eval" #S(ARGUMENT-LINE :STRING "eval (swank:start-server :dont-close t)" :START 39)) 6: (EVAL-COMMAND "eval (swank:start-server :dont-close t)" NIL) 7: (HANDLE-STUMPWM-COMMANDS #<XLIB:WINDOW :0 67>) 8: (HANDLE-EVENT)[:EXTERNAL] 9: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK)) 10: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]509)) 11: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK #<CLOSURE (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK) {B77FDCB5}> #S(SB-THREAD:MUTEX :NAME "CLX Event Lock" :%OWNER #<SB-THREAD:THREAD "initial thread" RUNNING {B696571}> :STATE 1)) 12: (XLIB:PROCESS-EVENT #<XLIB:DISPLAY :0 (The X.Org Foundation R10402000)>)[:EXTERNAL] 13: (STUMPWM-INTERNAL-LOOP) 14: (STUMPWM-INTERNAL ":0") 15: (STUMPWM ":0") 16: ((LAMBDA ())) 17: ((LABELS SB-IMPL::RESTART-LISP))
I don't have any suggestions at the moment, though perhaps the upstream slime will have a fix soon. It's possible that this is an sbcl bug, but what research I'm able to do points me to slime/swank.
I am using Debian GNU/Linux Sid, updated.