Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	"Richard Stanton" <stanton AT haas DOT berkeley DOT edu>
To:	"Cygwin" <cygwin AT sources DOT redhat DOT com>
Subject:	Limit on memory allocation?
Date:	Sat, 13 Jan 2001 11:55:00 -0800
Message-ID:	<LNBBKMIKMNGEJNEJICPHMEECELAA.stanton@haas.berkeley.edu>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2919.6700

Does cygwin/gcc have a limit on how much memory it can allocate under Win2k?

In particular, from my testing it seems that if the total amount of memory I
allocate in my C program using malloc calls exceeds the total amount of
PHYSICAL memory on my system (128MB), the allocation fails, even though I
asked Win2k to set up a 1GB paging file on my hard drive. Is there any way
to avoid this restriction, and have malloc take the virtual memory into
account?

Thanks.

Richard Stanton


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -