Your message dated Tue, 09 Mar 2010 09:29:12 +0100
with message-id <[email protected]>
and subject line Re: Bug#517167: sbcl has trouble starting a new swank server
has caused the Debian Bug report #517167,
regarding sbcl has trouble starting a new swank server
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
517167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517167
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: slime
Version: 1:20090217
Starting a new swank server with the following code
(require 'asdf)
(asdf:oos 'asdf:load-op 'swank)
;Specifically, this line\/
(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
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.
-- TheGZeus: Proof of Ferocious Will --
--- End Message ---
--- Begin Message ---
swank:start-server takes PORT-FILE as its first argument. So the call
(swank:start-server :dont-close t)
provides invalid arguments and the SBCL error response
odd number of &KEY arguments
is perfectly valid.
--- End Message ---
_______________________________________________
pkg-common-lisp-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel
