Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
> (defun test-crash ()
> (loop for i from 0 to 100 do
> (format t "test: ~a~%" i)
> (loop for j from 0 to 1000 do
> (sb-alien::load-shared-object "kernel32.dll")
> The message before SBCL exits:
was missing in the last post:
fatal error encountered in SBCL pid 1284:
GC invariant lost, file "gencgc.c", line 812
The system is too badly corrupted or confused to continue at the Lisp
level. If the system had been compiled with the SB-LDB feature, we'd drop
into the LDB low-level debugger now. But there's no LDB in this build, so
we can't really do anything but just exit, sorry.
Is the LDB debugger available for win32?
Frank Buss, fb@...
"Frank Buss" <fb@...> writes:
>> (defun test-crash ()
>> (loop for i from 0 to 100 do
>> (format t "test: ~a~%" i)
>> (loop for j from 0 to 1000 do
>> (sb-alien::load-shared-object "kernel32.dll")
> fatal error encountered in SBCL pid 1284:
> GC invariant lost, file "gencgc.c", line 812
After some poking around I managed to reproduce this with an MSYS
build running under cmd.exe. (This is a heisenbug, so if you're
trying to reproduce it twiddling with the test-case is probably
going to be necessary. For me adding a few WRITE-STRINGs and
removing the CLOSE-SHARED-OBJECTS did it.)
...no clues on the cause yet beyond the failed assert, though.
> Is the LDB debugger available for win32?
You can build SBCL with SB-LDB by adding :SB-LDB in
customize-target-features.lisp (see INSTALL file), but LDB doesn't
seem to helpful here for me.
By the way, what do you need CLOSE-SHARED-OBJECTS for?
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."