Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: localhost.localdomain: ronald owned process doing -bs Date: Wed, 12 Feb 2003 18:01:00 +0100 (CET) From: Ronald Landheer-Cieslak X-X-Sender: ronald AT localhost DOT localdomain To: Kris Warkentin cc: dl AT cs DOT oswego DOT edu, Subject: Re: Malloc failing too soon under XP/2000 In-Reply-To: <053001c2d2b3$a64a95c0$0202040a@catdog> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 > #include > > 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/