(room) leads to error on Windows
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
1.1.10 x86-64 Windows
$ sbcl --no-userinit
* (room)
Dynamic space usage is: 45,464,960 bytes.
Read-only space usage is: 5,584 bytes.
Static space usage is: 4,736 bytes.
Control stack usage is: 2,224 bytes.
Binding stack usage is: 864 bytes.
Control and binding stack usage is for the current thread only.
Garbage collection is currently enabled.
debugger invoked on a SB-INT:BUG in thread
#<THREAD "main thread" RUNNING {1002B4BA33}>:
failed AVER: (<= (GET-LISP-
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://
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-
0: [ABORT] Exit debugger, returning to top level.
(SB-INT:BUG "~@<failed AVER: ~2I~_~A~:>" (<= (SB-KERNEL:
VM::START) (SB-KERNEL:
0]
Changed in sbcl: | |
status: | Fix Committed → Fix Released |
In 556e61d75009be4 a9fb47a9754692e 428b026375.