Re: x86_64: SIGSEGV cannot be cured!

[Sam S. <sd...@gn...>]

> * Bruno Haible <oe...@py...t> [2004-10-27 19:48:33 +0200]:
>
> From the fact that you could load 5 GB of data before the thing
> crashed, I guess it's either a low-probability GC crash that you best
> debug in an image built with -g but without -DDEBUG_SPVW.

OK, I built a binary with -O replaced with -g (sAFETY=0 &c).
at about the same spot where it segfaulted with -O, I got this:

*** - CLOS::%MAKE-INSTANCE: A true list must not end with #<ADDRESS #x002800000020>

I am under gdb - would you like me to call (EXT:GC)?
I will probably land in gdb with a segfault.

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
A poet who reads his verse in public may have other nasty habits.