Re: STACK_ADDRESS_RANGE: mingw: autoconf vs lispbibl.d

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

> * Bruno Haible <oe...@py...t> [2005-02-28 21:56:31 +0100]:
>
> Sam wrote:
>> lispbibl.d/win32:
>> #define STACK_ADDRESS_RANGE ~0UL
>>
>> unixconf on mingw:
>> /* address range of the C stack */
>> #define STACK_ADDRESS_RANGE 0x00000000UL
>>
>> when the unixconf definition is used, I get:
>>
>> warning: HEAP[lisp.exe]:
>> warning: Heap block at 003F5AE0 modified at 003F5B18 past requested size of
>> 30
>
> Ouch. And when you change it to
>   #define STACK_ADDRESS_RANGE 0xFF000000UL
> or
>   #define STACK_ADDRESS_RANGE ~0UL
> it works, right? Then the fix will be to change m4/address.m4 with a
> #ifdef __MINGW32__

actually, the crash happens

1. ... _not_ at the first lisp.exe invocation,
   but at the linking set creation:
base/lisp.exe -B . -M base/lispinit.mem -norc -q -i i18n/i18n -i syscalls/posix -i regexp/regexp -x (saveinitmem "base/lispinit.mem")
make: *** [base] Error 5
(after base/lispinit.mem is written)

2.  ... regardless of what I do to STACK_ADDRESS_RANGE in
    unixconf.h : keep 0UL, replace with ~0UL or 0xFF000000UL.

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.iris.org.il> <http://www.camera.org> <http://www.mideasttruth.com/>
<http://www.honestreporting.com> <http://www.memri.org/>
main(a){a="main(a){a=%c%s%c;printf(a,34,a,34);}";printf(a,34,a,34);}