[Sbcl-devel] potentially useful failed aver backtrace

[Attila L. <att...@gm...>]

dear SBCL developers,

take a look at the attached backtrace and see if you can extract any
useful information. the relevant part is also inlined below.

fyi, i provide this in the hope that it may help polishing SBCL, i'm
not worried about this transient error on my side.


 18: (SB-IMPL::%FAILED-AVER (NOT (EQ # T)))

 19: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK))

 20: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]324))

 21: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK #<CLOSURE (FLET
SB-THREAD::WITH-RECURSIVE-LOCK-THUNK) {7FFFF2F9BB19}>
#S(SB-THREAD:MUTEX :NAME "World Lock" :%OWNER #<SB-THREAD:THREAD "http
worker 4 / serving request 733 / HANDLE-LEVEL-1-ERROR /
HANDLE-TOPLEVEL-ERROR" RUNNING {100BB45691}> :STATE 2))

 22: (SB-PCL::CHECK-WRAPPER-VALIDITY #<error printing object:   failed AVER: #
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 #, 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/>.>)

 23: (SB-PCL::CACHE-MISS-VALUES #<error printing object:   failed AVER: #
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 #, 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/>.>)

 24: (SB-PCL::CACHING-MISS #<error printing object:   failed AVER: #
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 #, 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/>.>)

 25: (MAKE-INSTANCE #<unavailable &REST argument>)

 26: (HU.DWIM.WALKER::=LAYERED-FUNCTION-DEFINER-FOR-WALK-FORM=
#<unavailable argument> #<unavailable &REST argument>)

-- 
 attila

Notice your eroding (digital) freedom, and do something about it!

PGP: 2FA1 A9DC 9C1E BA25 A59C  963F 5D5F 45C7 DFCD 0A39
OTR XMPP: 8647EEAC EA30FEEF E1B55146 573E52EE 21B1FF06
BitCoin: 154uf86Vd9rpjMULd9CXa7nVwikknYZJiB