A problem?

Paul Bowyer <[email protected]>
Newsgroups gmane.lisp.slime.devel
Message-ID <[email protected]>
Hello everyone,

Today I upgraded slime using "git clone 
https://github.com/slime/slime.git" after I upgraded sbcl from version 
1.1.17 to version 1.1.18. Slime completed the test suite without errors 
with emacs-23.4.1.

When I do ALT-x slime in emacs, a *sldb sbcl/1* window opens with the 
following:
Interrupt thread failed: thread #<THREAD "Swank 40905" FINISHED values: 
NIL {100343B723}> has exited.
    [Condition of type SB-THREAD:INTERRUPT-THREAD-ERROR]

Restarts:
  0: [ABORT] Abort thread (#<THREAD "Swank Sentinel" RUNNING {100343B343}>)

Backtrace:
   0: (SB-THREAD:INTERRUPT-THREAD #<SB-THREAD:THREAD "Swank 40905" 
FINISHED values: NIL {100343B723}> #<FUNCTION (LAMBDA NIL :IN 
SB-THREAD:TERMINATE-THREAD) {1001C9062B}>)
   1: (SWANK::SENTINEL-SERVE (:STOP-SERVER :SOCKET 
#<SB-BSD-SOCKETS:INET-SOCKET fd: -1 {100336FAB3}>))
   2: (SWANK::SENTINEL)
   3: ((FLET #:WITHOUT-INTERRUPTS-BODY-1226 :IN 
SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE))
   4: ((FLET SB-THREAD::WITH-MUTEX-THUNK :IN 
SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE))
   5: ((FLET #:WITHOUT-INTERRUPTS-BODY-660 :IN SB-THREAD::CALL-WITH-MUTEX))
   6: (SB-THREAD::CALL-WITH-MUTEX #<CLOSURE (FLET 
SB-THREAD::WITH-MUTEX-THUNK :IN 
SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE) {7FFFF675EC2B}> 
#<SB-THREAD:MUTEX "thread result lock" owner: #<SB-THREAD:THR..
   7: (SB-THREAD::INITIAL-THREAD-FUNCTION-TRAMPOLINE #<SB-THREAD:THREAD 
"Swank Sentinel" RUNNING {100343B343}> #S(SB-THREAD:SEMAPHORE :NAME 
"Thread setup semaphore" :%COUNT 0 :WAITCOUNT 0 :MUTEX #<SB-THREAD..
   8: ("foreign function: call_into_lisp")
   9: ("foreign function: new_thread_trampoline")

If I choose abort, it closes the sldb window and leaves me with a 
running repl, but I'm uncertain everything is OK.

Don't really know what to do next.

Thanks for any pointers,

Paul Bowyer
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.