| | | > 3. Are these sensible values? | | | > | | | > #define CSTACK_TOP 0x80000000 | | | > #define CSTACK_RANGE 0x40000000 | | | > | | | | | | Yes, It appears as if your C stack counts down from 0x80000000, | | | leaving the range above this value fair game for immediate fixnums. | | | | | | Actually it counts down from the values shown below in the default case: | | Sorry - I messed my Hex to Decimal conversion and got confused.
Actually I got confused in the last PS message - CSTACK counts down from the value in the example program run posted earlier - 2 Gig is definitely NOT where the Windows C stack starts. Sorry about that. This is also the cause of the GCL crash after configure - it tries to grab too much space and barfs on startup - I'll go further when I have some more time. Cheers (and thanks for all the great work) Mike Thomas. _______________________________________________ Gcl-devel mailing list Gcl-devel@gnu.org http://lists.gnu.org/mailman/listinfo/gcl-devel
