[STUMP] Lisp crashes with stumpwm

[Milan Zamazal]

I tried to run the latest StumpWM from the git repository on Debian
amd64.  It's great but I couldn't run it for very long.

With SBCL 1.0.12 it usually crashes within the first hour of its run
reporting the following error:

  Caught 'Recursive lock attempt #S(SB-THREAD:MUTEX
                                    :NAME "Scheduler lock"
                                    :%OWNER #<SB-THREAD:THREAD "initial thread" 
{1002697E61}>
                                    :STATE 1).' at the top level. Please report 
this.
  0: (SB-DEBUG:BACKTRACE
      100
      #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDOUT* {1000207F51}>)
  1: ((LAMBDA (C)) #<SIMPLE-ERROR {10031692E1}>)
  2: (SIGNAL #<SIMPLE-ERROR {10031692E1}>)
  3: (ERROR "Recursive lock attempt ~S.")
  4: (SB-THREAD:GET-MUTEX
      #<unavailable argument>
      #<unavailable argument>
      #<unavailable argument>)
  5: ((FLET SB-THREAD::%CALL-WITH-SYSTEM-MUTEX))
  6: (SB-UNIX::CALL-ALLOWING-WITH-INTERRUPTS
      #<CLOSURE (FLET SB-UNIX::ALLOW-WITH-INTERRUPTS-THUNK) {2B6285C6FDA9}>
      T)
  7: ((FLET SB-UNIX::WITHOUT-INTERRUPTS-THUNK) T)
  8: ((FLET SB-UNIX::RUN-WITHOUT-INTERRUPTS))
  9: (SB-UNIX::CALL-WITHOUT-INTERRUPTS
      #<CLOSURE (FLET SB-UNIX::WITHOUT-INTERRUPTS-THUNK) {2B6285C6FF89}>)
  10: (SB-THREAD::CALL-WITH-SYSTEM-MUTEX
       #<CLOSURE (LAMBDA #) {1003169279}>
       #S(SB-THREAD:MUTEX
          :NAME "Scheduler lock"
          :%OWNER #<SB-THREAD:THREAD "initial thread" {1002697E61}>
          :STATE 1)
       NIL)
  11: ((FLET SB-UNIX::WITH-INTERRUPTS-THUNK))
  12: ((FLET SB-UNIX::WITH-INTERRUPTS-THUNK))
  13: (SB-UNIX::CALL-WITH-INTERRUPTS
       #<CLOSURE (FLET SB-UNIX::WITH-INTERRUPTS-THUNK) {2B6285C702A9}>
       T)
  14: (SB-IMPL::RUN-EXPIRED-TIMERS)
  ...

With CLISP 2.43 the Lisp process starts eating a lot of CPU time after
several minutes of StumpWM run, so it's unusable as well.

Note I start several timers in my ~/.stumpwmrc for periodic update of
various information to be displayed in mode line.

So can anybody run StumpWM on Debian reliably?  How to do it?  Are the
problems known or should I report them to SBCL and CLISP developers?
StumpWM is highly addictive, it's hard for me to return back to
Ratpoison :-).

Thanks,

Milan Zamazal