Hi Elliott,Could you please try to build and use the latest SBCL, as described here: http://sbcl-internals.cliki.net/Build%20on%20Windows ?It may be that some issues are fixed since 1.0.37. In case you see the same on 1.0.46, please create tickets in Launchpad.Thank you,Roman2011/2/21 Elliott Slaughter <email@example.com>
------------------------------------------------------------------------------Hi all,I recently managed to produce 3 separate crashes on 64-bit Windows 7 while using quicklisp.The crashes seem to be intermittent, although I have been able to reproduce them semi-reliably by deleting my ~/quicklisp directory and installing a fresh copy.Let me know if I should create a bug report for this or if I can in any way help debug this.First crash:$ sbclThis is SBCL 1.0.37, 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 underBSD-style licenses. See the CREDITS and COPYING files in thedistribution for more information.This is experimental prerelease support for the Windows platform: useat your own risk. "Your Kitten of Death awaits!"* (ql:quickload "cl-zmq")fatal error encountered in SBCL pid 2216:GC invariant lost, file "gencgc.c", line 936Welcome to LDB, a low-level debugger for the Lisp runtime environment.ldb> backtraceBacktrace:ldb>Second crash:GC invariant lost, file "gencgc.c", line 936* (ql:system-apropos "zmq")fatal error encountered in SBCL pid 3080:--
Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb>Third crash:* (ql:quickload "lispbuilder-sdl")Final object pointer FB840001, start FB840001, end 02A90525fatal error encountered in SBCL pid 4620:GC invariant lost, file "gc-common.c", line 211Welcome to LDB, a low-level debugger for the Lisp runtime environment.
"Don't worry about what anybody else is going to do. The best way to predict the future is to invent it." - Alan Kay
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
Sbcl-devel mailing list