This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Malloc failing too soon under XP/2000
- From: Ronald Landheer-Cieslak <ronald at landheer dot com>
- To: Kris Warkentin <kewarken at qnx dot com>
- Cc: dl at cs dot oswego dot edu, <cygwin at cygwin dot com>
- Date: Wed, 12 Feb 2003 18:01:00 +0100 (CET)
- Subject: Re: Malloc failing too soon under XP/2000
Charles Werner explains this pretty well in:
http://sources.redhat.com/ml/cygwin/2003-02/msg00234.html
he also explains how to change the settings
ciao
rlc
On Wed, 12 Feb 2003, Kris Warkentin wrote:
> I'm running Windows XP with 1/2GB RAM and 2GB swap. Running Cygwin 1.3.18.
> Consider the following program to use as much memory as possible:
>
> #include <stdio.h>
> #include <malloc.h>
>
> int
> main()
> {
> void *x;
> unsigned long long mem=0;
>
> while((x=malloc(500000)) != NULL){
> mem += 500000;
> memset(x, 0, 500000);
> printf("allocated %u\n", mem);
> }
> return 0;
> }
>
> If I compile and run this, it consistently stops at about 780MB. If I
> compile with -mno-cygwin, it doesn't fail until almost 2GB have been
> allocated.
>
> Any comment? Is there some sort of flag I can compile with to make the
> allocator more aggressive? The situation it's failing in is one where a
> very large library is being linked and ld is running out of memory in spite
> of quite a bit being available.
>
> cheers,
>
> Kris
>
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/