slime-devel May 2014

slime-devel@common-lisp.net

9 participants
13 discussions

[Slime-devel] SLIME 2.6 released
by Luís Oliveira 04 May '14

04 May '14

Hello all, SLIME 2.6 is released! https://github.com/slime/slime/releases/tag/v2.6 Cheers, -- Luís Oliveira http://kerno.org/~luis/

1 0

[Slime-devel] A problem?
by Paul Bowyer 02 May '14

02 May '14

Hello everyone, This morning after I started my computer, I tried slime again and to my surprise it came up without a whimper. What ever was the problem yesterday that was causing the sldb window cleared itself after this morning's boot. I hope you haven't spent a lot of time searching for a non-existent problem and I apologize for the faulty report. Paul Bowyer

1 0

[Slime-devel] A problem?
by Paul Bowyer 01 May '14

01 May '14

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

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel May 2014