[STUMP] Stumpwm build fails at commit 920995

[Paulo J. Matos]

It says it might be an SBCL error but I always tend to doubt about 
compiler bugs first.

Is this Stumpwm or SBCL 1.0.45 (end of log):
; --> LET XLIB::WITH-BUFFER MACROLET LET XLIB::HOLDING-LOCK
; --> SB-THREAD:WITH-RECURSIVE-LOCK SB-INT:DX-FLET FLET BLOCK
; --> MULTIPLE-VALUE-PROG1 XLIB::WITHOUT-ABORTS PROGN
; --> XLIB::WITH-BUFFER-REQUEST-INTERNAL XLIB::WITH-BUFFER-OUTPUT LET LET*
; --> XLIB::BUFFER-NEW-REQUEST-NUMBER BLOCK SETF LET* 
MULTIPLE-VALUE-BIND LET
; --> LDB SB-KERNEL:%LDB
; ==>
;   (LOGAND (ASH INT (- SB-C::POSN)) (ASH 18446744073709551615 (- 
SB-C::SIZE 64)))
;
; note: forced to do static-fun Two-arg-and (cost 53)
;       unable to do inline fixnum arithmetic (cost 1) because:
;       The first argument is a INTEGER, not a FIXNUM.
;       unable to do inline fixnum arithmetic (cost 2) because:
;       The first argument is a INTEGER, not a FIXNUM.
;       etc.
ASDF could not load stumpwm because   failed AVER:
                                        (AND (NULL (TN-READS TN))
                                             (NULL (TN-WRITES TN)))
                                    This is probably a bug in SBCL itself.
                                    (Alternatively, SBCL might have been
                                    corrupted by bad user code, e.g. by an
                                    undefined Lisp operation like
                                    (FMAKUNBOUND 'COMPILE), or by stray
                                    pointers from alien code or from unsafe
                                    Lisp code; or there might be a bug 
in the
                                    OS or hardware that SBCL is running 
on.) If
                                    it seems to be a bug in SBCL 
itself, the
                                    maintainers would like to know 
about it.
                                    Bug reports are welcome on the SBCL 
mailing
                                    lists, which you can find at
                                    <http://sbcl.sourceforge.net/>..

debugger invoked on a SB-INT:BUG in thread #<THREAD "initial thread" RUNNING
                                             {1002D200E1}>:
    failed AVER: (AND (NULL (TN-READS TN)) (NULL (TN-WRITES TN)))
  This is probably a bug in SBCL itself. (Alternatively, SBCL might 
have been
  corrupted by bad user code, e.g. by an undefined Lisp operation like
  (FMAKUNBOUND 'COMPILE), or by stray pointers from alien code or from 
unsafe
  Lisp code; or there might be a bug in the OS or hardware that SBCL is 
running
  on.) If it seems to be a bug in SBCL itself, the maintainers would 
like to
  know about it. Bug reports are welcome on the SBCL mailing lists, 
which you
  can find at <http://sbcl.sourceforge.net/>.

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [TRY-RECOMPILING] Try recompiling requests
  1: [RETRY          ] Retry compiling component ("clx" "requests").
  2: [ACCEPT         ] Continue, treating
                       compiling component ("clx" "requests") as having 
been
                       successful.
  3: [CONTINUE       ] Ignore runtime option --load "./make-image.lisp".
  4: [ABORT          ] Skip rest of --eval and --load options.
  5:                   Skip to toplevel READ/EVAL/PRINT loop.
  6: [QUIT           ] Quit SBCL (calling #'QUIT, killing the process).

(SB-INT:BUG
 "~@<failed AVER: ~2I~_~A~:>"
 (AND (NULL (SB-C::TN-READS SB-C:TN)) (NULL (SB-C::TN-WRITES SB-C:TN))))
0]

Can I get you more info about this?

Cheers,
--
PMatos