Re: [STUMP] Crash in Arch Linux with SBCL 1.0.55

Stephen Balousek Thu, 05 Apr 2012 18:10:57 -0700

Hi,

I managed to get a repeat of this crash - this time with more information about the point of failure.

Judging from the functions involved, I am guessing this might be an issue with CLX. Any other ideas would be appreicated.


- Steve

Caught 'The value -25040316 is not of type UNSIGNED-BYTE.' at the top level. Please report this.

0: (SB-DEBUG::MAP-BACKTRACE
    #<CLOSURE (LAMBDA #) {10043F95D9}>
    :START
    0
    :COUNT
    100)
1: (SB-DEBUG:BACKTRACE 100 #<SB-IMPL::STRING-OUTPUT-STREAM {10043F9531}>)
2: (BACKTRACE-STRING)
3: (PERFORM-TOP-LEVEL-ERROR-ACTION
    #<TYPE-ERROR expected-type: UNSIGNED-BYTE datum: -25040316>)
4: (SIGNAL #<TYPE-ERROR expected-type: UNSIGNED-BYTE datum: -25040316>)
5: (ERROR TYPE-ERROR :DATUM -25040316 :EXPECTED-TYPE UNSIGNED-BYTE)
6: (SB-KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER
    #<unavailable argument>
    #.(SB-SYS:INT-SAP #X7FFFF6CD6E98)
    #<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #X7FFFF6CD6880 :TYPE (*

(SB-ALIEN:STRUCT SB-VM::OS-CONTEXT-T-STRUCT))>

    (84 21))
7: (SB-KERNEL:INTERNAL-ERROR
    #.(SB-SYS:INT-SAP #X7FFFF6CD6880)
    #<unavailable argument>)
8: ("foreign function: call_into_lisp")
9: ("foreign function: funcall2")
10: ("foreign function: interrupt_internal_error")
11: ("foreign function: handle_trap")
12: ("foreign function: #x4104D3")
13: (GET-INTERNAL-REAL-TIME)
14: (SB-SYS:DECODE-TIMEOUT NIL)
15: (SB-SYS:WAIT-UNTIL-FD-USABLE 4 :INPUT NIL T)
16: (XLIB::BUFFER-INPUT-WAIT-DEFAULT
     #<XLIB:DISPLAY :0 (The X.Org Foundation R11200000)>
     NIL)
17: (XLIB::BUFFER-INPUT-WAIT
     #<XLIB:DISPLAY :0 (The X.Org Foundation R11200000)>
     NIL)
18: (XLIB::READ-INPUT
     #<XLIB:DISPLAY :0 (The X.Org Foundation R11200000)>
     NIL
     NIL
     #<FUNCTION (LAMBDA #) {100259B509}>
     #S(XLIB::PENDING-COMMAND
        :SEQUENCE 6705
        :REPLY-BUFFER NIL
        :PROCESS #<SB-THREAD:THREAD "initial thread" RUNNING {1003B08E11}>
        :NEXT NIL))
19: (XLIB::READ-REPLY #<unavailable argument> #<unavailable argument>)
20: (XLIB:DISPLAY-FINISH-OUTPUT
     #<XLIB:DISPLAY :0 (The X.Org Foundation R11200000)>)
21: (HANDLE-EVENT
     :DISPLAY
     #<XLIB:DISPLAY :0 (The X.Org Foundation R11200000)>
     :EVENT-KEY
     :PROPERTY-NOTIFY
     :EVENT-CODE
     28
     :SEND-EVENT-P
     NIL
     :SEQUENCE
     6704
     :WINDOW
     #<XLIB:WINDOW :0 100000F>
     :EVENT-WINDOW
     #<XLIB:WINDOW :0 100000F>
     :ATOM
     :_NET_WM_USER_TIME
     :TIME
     283134
     :STATE
     :NEW-VALUE)
22: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK))
23: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]333))
24: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK
     #<CLOSURE (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK) {7FFFF6CD7839}>
     #<SB-THREAD:MUTEX "CLX Event Lock"
         owner: #<SB-THREAD:THREAD "initial thread" RUNNING {1003B08E11}>>)
25: (XLIB:PROCESS-EVENT
     #<XLIB:DISPLAY :0 (The X.Org Foundation R11200000)>
     :HANDLER
     #<FUNCTION HANDLE-EVENT>
     :TIMEOUT
     NIL
     :PEEK-P
     NIL
     :DISCARD-P
     NIL
     :FORCE-OUTPUT-P
     T)
26: (STUMPWM-INTERNAL-LOOP)
27: (STUMPWM-INTERNAL ":0")
28: (STUMPWM ":0")
29: ((LAMBDA ()))
30: ((FLET #:WITHOUT-INTERRUPTS-BODY-[RESTART-LISP]38))
31: ((LABELS SB-IMPL::RESTART-LISP))

debugger invoked on a TYPE-ERROR in thread #<THREAD "initial thread" RUNNING
                                              {1003B08E11}>:
  The value -25040307 is not of type UNSIGNED-BYTE.

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

(no restarts: If you didn't do this on purpose, please report it as a bug.)

(GET-INTERNAL-REAL-TIME)
0]



On 02/28/2012 06:15 AM, Stephen Balousek wrote:

Hi,

I am getting a strange, intermittent crash of StumpWM and I am looking for pointers on how to resolve it, or possible workarounds.


The relevant information from ~/.xsession-errors is:

    Caught 'The value -28580123 is not of type UNSIGNED-BYTE.' at the
    top level. Please report this.
    0: (SB-DEBUG::MAP-BACKTRACE
        #<CLOSURE (LAMBDA # :IN SB-DEBUG:BACKTRACE) {100555C56B}>
        :START
        0
        :COUNT
        100)
    1: (SB-DEBUG:BACKTRACE 100 #<SB-IMPL::STRING-OUTPUT-STREAM
    {100555C463}>)
    2: (BACKTRACE-STRING)
    3: (PERFORM-TOP-LEVEL-ERROR-ACTION
        #<TYPE-ERROR expected-type: UNSIGNED-BYTE datum: -28580123>)
    4: (SIGNAL #<TYPE-ERROR expected-type: UNSIGNED-BYTE datum:
    -28580123>)
    5: (ERROR TYPE-ERROR :DATUM -28580123 :EXPECTED-TYPE UNSIGNED-BYTE)
    6: (SB-KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER
        #<unavailable argument>
        #.(SB-SYS:INT-SAP #X7FFFF704E9F8)
        #<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #X7FFFF704E3C0 :TYPE (*

(SB-ALIEN:STRUCT SB-VM::OS-CONTEXT-T-STRUCT))>

        (84 21))
    7: (SB-KERNEL:INTERNAL-ERROR
        #.(SB-SYS:INT-SAP #X7FFFF704E3C0)
        #<unavailable argument>)
    8: ("foreign function: #x4180DF")

    debugger invoked on a TYPE-ERROR in thread
    #<THREAD "initial thread" RUNNING {1003BA8E23}>:
      The value -28580118 is not of type UNSIGNED-BYTE.

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

    (no restarts: If you didn't do this on purpose, please report it
    as a bug.)

    (SB-KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER
     #<unavailable argument>
     #.(SB-SYS:INT-SAP #X7FFFF704EEB0)
     #<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #X7FFFF704E880 :TYPE (*
                                                                 (STRUCT

SB-VM::OS-CONTEXT-T-STRUCT))>

     (84 21))
    0]

Can anyone tell if this is a StumpWM issue or an SBCL issue? I am thinking it is an issue with the FFI layer in SBCL, but any other interpretations would be appreciated.


Thanks,
- Steve

smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/stumpwm-devel

Re: [STUMP] Crash in Arch Linux with SBCL 1.0.55

Reply via email to