trivial-gamekit
trivial-gamekit copied to clipboard
borodust
issue on quickload (windows 10)
failed AVER: (EQ SB-C::ENV (SB-C::LAMBDA-ENVIRONMENT (SB-C::LAMBDA-VAR-HOME SB-C::THING))) 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/. [Condition of type SB-INT:BUG]
Restarts: 0: [RETRY] Retry compiling #<CL-SOURCE-FILE "bodge-canvas" "canvas">. 1: [ACCEPT] Continue, treating compiling #<CL-SOURCE-FILE "bodge-canvas" "canvas"> as having been successful. 2: [RETRY] Retry ASDF operation. 3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration. 4: [RETRY] Retry ASDF operation. 5: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration. 6: [ABORT] Give up on "trivial-gamekit" 7: [REGISTER-LOCAL-PROJECTS] Register local projects and try again. 8: [RETRY] Retry SLY mREPL evaluation request. 9: [*ABORT] Return to SLY's top level. 10: [ABORT] abort thread (#<THREAD "sly-channel-1-mrepl-remote-1" RUNNING {1001D60133}>)
I'm getting the same error on Linux (an arch linux container running on a nixos host).
[csos95@arch csos95]$ sbcl
This is SBCL 2.3.1, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.
SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
* (ql:quickload :trivial-gamekit)
To load "trivial-gamekit":
Load 1 ASDF system:
trivial-gamekit
; Loading "trivial-gamekit"
.............................................
debugger invoked on a SB-INT:BUG @52AACEF0 in thread
#<THREAD "main thread" RUNNING {10013A0073}>:
failed AVER:
(EQ SB-C::ENV
(SB-C::LAMBDA-ENVIRONMENT (SB-C::LAMBDA-VAR-HOME SB-C::THING)))
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:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY ] Retry
compiling #<CL-SOURCE-FILE "bodge-canvas" "canvas">.
1: [ACCEPT ] Continue, treating
compiling #<CL-SOURCE-FILE "bodge-canvas" "canvas">
as having been successful.
2: Retry ASDF operation.
3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the
configuration.
4: Retry ASDF operation.
5: Retry ASDF operation after resetting the
configuration.
6: [ABORT ] Give up on "trivial-gamekit"
7: [REGISTER-LOCAL-PROJECTS ] Register local projects and try again.
8: Exit debugger, returning to top level.
(SB-C::FIND-IN-ENVIRONMENT #<SB-C::LAMBDA-VAR :%SOURCE-NAME DEFAULT-FONT-DATA-STATIC {1004BD33B3}> #<SB-C::ENVIRONMENT :LAMBDA #<SB-C::CLAMBDA :%SOURCE-NAME SB-THREAD::WITH-RECURSIVE-LOCK-THUNK :%DEBUG-NAME (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK :IN DEFAULT-FONT-STATIC-DATA) :KIND NIL :TYPE #<SB-KERNEL:FUN-TYPE (FUNCTION NIL (VALUES T &OPTIONAL))> :WHERE-FROM :DEFINED :VARS NIL {1004BD6643}> :CLOSURE (#<SB-C::LAMBDA-VAR :%SOURCE-NAME DEFAULT-FONT-DATA :FLAGS (SB-C::INDIRECT SB-C::EXPLICIT-VALUE-CELL) {1004BD32B3}>) {1004C27E83}>)
0]
It looks like its been fixed in sbcl itself ( see https://bugs.launchpad.net/sbcl/+bug/1981607 ) although launchpad leaves a lot to be desired about tracking that fix into a git commit.
