Something in the changes on the 6th cause slime to freak out on sbcl 1.0.18 w/ threads on OS X. (This is sbcl from macports, if it might make a difference.)
cvs update -D '2008-08-06 17:50:37'
is the earliest change that reproduces the problem. (The preceding changeset won't start at all; changesets before that work fine.)
The symptom is a never-ending chain of these warnings:
WARNING: Releasing #S(SB-THREAD:MUTEX :NAME NIL :%OWNER NIL :LUTEX #<unknown pointer object, widetag=#x5E {11D7111F}>), owned by another thread: NIL
I haven't tried to track down the problem, yet. Does anything seem obvious to those responsible for the relevant changes?
Thanks, Thom
On Aug 11, 2008, at 8:42 PM, thom.goodsell@mac.com wrote:
Something in the changes on the 6th cause slime to freak out on sbcl 1.0.18 w/ threads on OS X. (This is sbcl from macports, if it might make a difference.)
cvs update -D '2008-08-06 17:50:37'
is the earliest change that reproduces the problem. (The preceding changeset won't start at all; changesets before that work fine.)
The symptom is a never-ending chain of these warnings:
WARNING: Releasing #S(SB-THREAD:MUTEX :NAME NIL :%OWNER NIL :LUTEX #<unknown pointer object, widetag=#x5E {11D7111F}>), owned by another thread: NIL
I haven't tried to track down the problem, yet. Does anything seem obvious to those responsible for the relevant changes?
This came up a few days ago (although it's still waiting for a reply from an SBCL hacker). The last thread had a workaround, at least: http://common-lisp.net/pipermail/slime-devel/2008-August/007501.html
-Andrew
Thanks, Thom
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
Oops; should have caught that. Thanks, Andrew.
Thom
On Aug 11, 2008, at 11:21 PM, Andrew Gasparovic wrote:
On Aug 11, 2008, at 8:42 PM, thom.goodsell@mac.com wrote:
Something in the changes on the 6th cause slime to freak out on sbcl 1.0.18 w/ threads on OS X. (This is sbcl from macports, if it might make a difference.)
cvs update -D '2008-08-06 17:50:37'
is the earliest change that reproduces the problem. (The preceding changeset won't start at all; changesets before that work fine.)
The symptom is a never-ending chain of these warnings:
WARNING: Releasing #S(SB-THREAD:MUTEX :NAME NIL :%OWNER NIL :LUTEX #<unknown pointer object, widetag=#x5E {11D7111F}>), owned by another thread: NIL
I haven't tried to track down the problem, yet. Does anything seem obvious to those responsible for the relevant changes?
This came up a few days ago (although it's still waiting for a reply from an SBCL hacker). The last thread had a workaround, at least: http://common-lisp.net/pipermail/slime-devel/2008-August/007501.html
-Andrew
Thanks, Thom
slime-devel site list slime-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/slime-devel
-
Andrew Gasparovic -
Thom Goodsell -
thom.goodsell＠mac.com