This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: Cygwin 128MB Registry Hack Fix - Is there a UPPER Limit?
- To: "'SaurabhMisra at Agere dot com'" <SaurabhMisra at Agere dot com>, cygwin at sourceware dot cygnus dot com
- Subject: RE: Cygwin 128MB Registry Hack Fix - Is there a UPPER Limit?
- From: Heribert Dahms <heribert_dahms at icon-gmbh dot de>
- Date: Wed, 6 Jun 2001 22:50:29 +0200
Hi Saurabh,
the registry setting is heap_chunk_in_mb and 0x1010 is 4096+16,
so you obviously (haven't tried nor read the sources) overflow 32bit
and effectively get only 16MB!
Bye, Heribert (heribert_dahms@icon-gmbh.de)
> -----Original Message-----
> From: Saurabh Misra [SMTP:saurabhmisra@lucent.com]
> Sent: Tuesday, June 05, 2001 23:25
> To: cygwin@sourceware.cygnus.com
> Subject: Cygwin 128MB Registry Hack Fix - Is there a UPPER Limit?
>
>
>
>
> I read the tip on how to get a "GCC-Under-Cygwin" compiled program to be
> able to malloc more than 128MB. I tried successfully setting the
> value to 1GB (1024), but after that, it seems the next value that worked
> was approx 4GB (Hex 1010). But I could not get any value in between to
> work - if I tried it (for example, 2048), upon trying to open a cygwin
> terminal (a bash terminal), it would immediately quit fatally.
>
> Is there a particular piece of information I am missing?
>
> Thanks.
> Saurabh.
>
> << File: Card for Saurabh Misra >> << File: ATT19389.txt >>
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple