This is the mail archive of the
mailing list for the Cygwin project.
RE: large memory allocation via new causes segmentation fault in G++ compiled programs
- To: cygwin at sourceware dot cygnus dot com
- Subject: RE: large memory allocation via new causes segmentation fault in G++ compiled programs
- From: NOE Nicolas <n dot noe at cstb dot fr>
- Date: Tue, 8 Aug 2000 09:35:54 +0200
I've raised the same problem some time ago on the list. I haven't
seen any answer on the list, but I've found a way to solve it. By the
way, I'm still interested in other people explanations !
Here's my answer, hope it helps !
>>I'm using cygwin & gcc on a 512 Mb PC running NT, and
>>it seems that I cannot allocate more than (roughly)
>>128 MegaBytes of total memory (either with a single
>>malloc call, or with lots of them). Is there's a memory
>>allocation limit in cygwin & gcc or am I missing something ?
>>(the same program works fine with Watcom C, and I'm using
>>cygwin latest release)
>>Thanks in advance if anyone can help !
>I can't fully answer my question, but I've found a way to malloc
>more than 128 Mb. I've read than cygwin uses Doug Lea's malloc
>(http://gee.cs.oswego.edu/pub/misc/malloc.c), and I've compiled
>it and linked it with my programs, and then, it works.
>For instance, the following program fails if compiled with gcc,
>and works when linked with Doug Lea's malloc.
> void *p = malloc(128 * 1024 * 1024);
> return 0;
>Using that other malloc solves my problem, but I'd still like to
>know if it's something wrong with my system or a problem with gcc.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org