delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Message-ID: | <053001c2d2b3$a64a95c0$0202040a@catdog> |
From: | "Kris Warkentin" <kewarken AT qnx DOT com> |
To: | <dl AT cs DOT oswego DOT edu>, <cygwin AT cygwin DOT com> |
Subject: | Malloc failing too soon under XP/2000 |
Date: | Wed, 12 Feb 2003 11:27:34 -0500 |
MIME-Version: | 1.0 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2800.1106 |
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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |