Re: Malloc array size limit (3)

2003-03-05 Thread Larry Hall (RFK Partners, Inc.)
Fabrizio Impagnatiello wrote: Thanks again, but even with heap_chunk the very simple code does not run. I would to emphatise that the same EXE (gcc 3.2) correctly allocates memory if run-time linked to cygwin1.dll v1.3.12 but run fails if I use DLL versions between 1.3.17 and 1.3.20. uname -a: CYG

Re: Malloc array size limit (2)

2003-03-04 Thread Max Bowsher
Fabrizio Impagnatiello wrote: > Again on same issue. > if I compile the following source with -mno-cygwin option, the EXE > code allocating up to 1 GByte runs good. > If the option is removed, the cygwin1.dll fails. Well, obviously, if you don't use cygwin, then you don't get any limits it impose

Re: Malloc array size limit

2003-03-04 Thread Igor Pechtchanski
On Tue, 4 Mar 2003, Fabrizio Impagnatiello wrote: > I experienced run-time array memory allocation failure using cygwin1.dll > versions 1.3.14, 1.3.17, 1.3.18, 1.3.19, 1.3.20. > This trouble does not reveals using 1.3.12. > > In particular the largest allocable array (from both gcc and g77) size i

Re: Malloc array size limit

2003-03-04 Thread Fabrizio Impagnatiello
Thanks a lot. I tried. Sorry, but the suggestion to define the heap_chunk key in Windows registry did not work. My application globally allocates about 560 Mbyte memory but no single data structure can be larger than 128 MB. IT is compiled with gcc 3.2-3 under cygwin 1.3.20-1 environment. Neverthe

Re: Malloc array size limit

2003-03-04 Thread Ronald Landheer-Cieslak
See if this helps http://cygwin.com/cygwin-ug-net/setup-maxmem.html rlc On Tue, 4 Mar 2003, Fabrizio Impagnatiello wrote: > I experienced run-time array memory allocation failure using cygwin1.dll > versions 1.3.14, 1.3.17, 1.3.18, 1.3.19, 1.3.20. > This trouble does not reveals using 1.3.12. >