segfault during build with CVS latest

[Jack U. <jd...@gm...>]

I'm experiencing what appears to be stack corruption during a MinGW
build. This is with CVS latest as of today. My environment is:

WinXP SP2 / gcc 3.4.5 (mingw special) / libsigsegv 2.4

My configure command-line is:

CFLAGS="-g" ./configure --with-mingw --build build
--with-libsigsegv-prefix=/usr/local --with-module=bindings/win32
--with-module=gdi --with-module=dirkey --with-module=rawsock
--with-module=wildcard

This is the point during the build in which the crash happens:

[...snip preceding output...]
rm -f deprecated.lisp
ln -s ../src/deprecated.lisp deprecated.lisp
cp -p ../src/cfgwin32.lisp config.lisp
rm -f interpreted.mem
lisp.exe -B . -N locale -E 1:1 -Efile UTF-8 -Eterminal UTF-8 -norc -m 1800KW -x
"(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit)) (ext::exit t)"
        i
i i i i I i i i i     ooooo    o        ooooooo   ooooo   ooooo
I I I I I I I I I    8     8   8           8     8     o  8    8
I I  \ `+' /  I I    8         8           8     8        8    8
I  \  `-+-'  /  I    8         8           8      ooooo   8oooo
 \  `-__|__-'  /     8         8           8           8  8
  `--___|___--'      8     o   8           8     o     8  8
        |             ooooo    8oooooo  ooo8ooo   ooooo   8
--------+--------


*** - handle_fault error2 ! address = 0xce37cc88 not in [0x5ad70000,0x5ad70000)
!
SIGSEGV cannot be cured. Fault address = 0xce37cc88.
Permanently allocated: 88544 bytes.
Currently in use: 202300 bytes.
Free space: 321988 bytes.
make: *** [interpreted.mem] Error 5



When I run this stage under gdb, I get a stack trace that indicates
stack corruption with numerous stack frames showing addresses
0x00000000 and 0xffffffff and then this message from gdb:

  Previous frame inner to this frame (corrupt stack?)

During compilation, I see the following warning issues for various files,
perhaps it's related?

  lispbibl.d:9115: warning: register used for two global register variables

-- 
Jack Unrue