On Aug 7, 2008, at 16:14 , Helmut Eller wrote:

...

WARNING: Releasing #S(SB-THREAD:MUTEX :NAME NIL :%OWNER NIL :LUTEX #<unknown pointer object, widetag=#x5E {11B7911F}>), owned by another thread: NIL

this is sbcl 1.0.18 with threads on mac os 10.5.4.

Do others see this too? On Linux with SBCL 1.0.4.15 and 1.0.18.debian everything works quietly.

I do see these messages, on the same setup as the original poster (sbcl w/ threads, OS X 10.5, Intel). However, they happen seldom for me, and mostly when I abort computations, or use restarts which throw me back to toplevel.

I did not investigate how to trigger the warnings reliably.

Cheers, Michael

* okflo@diesenbacher.net [2008-08-07 17:21+0200] writes:

Thanks for your investigation. I get these warnings 1-2 times per second, filling my repl-buffer, even when doing literal nothing :))

I suspect this is a SBCL problem. The message "by another thread: NIL" sounds a bit funny. But I leave the final judgement to the SBCL wizards.

As a workaround you can probably remove the SB-EXT:WITH-TIMEOUT form in RECEIVE-IF in swank-sbcl.lisp. Most things should work after that, but you may need to press slime-interrupt 3-4 times in row to trigger the debugger in a dangerous section.

Helmut.