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:	<03c201c2e289$445c45d0$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	"Fabrizio Impagnatiello" <f DOT impagnatiello AT roma DOT alespazio DOT it>,
	<cygwin AT cygwin DOT com>
References:	<20030304195846 DOT 05EB79FC63 AT mail DOT roma DOT alespazio DOT it>
Subject:	Re: Malloc array size limit (2)
Date:	Tue, 4 Mar 2003 20:04:30 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

Fabrizio Impagnatiello wrote:
> Again on same issue.
> if I compile the following source with -mno-cygwin option, the EXE
> code allocating up to 1 GByte runs good.

> If the option is removed, the cygwin1.dll fails.

Well, obviously, if you don't use cygwin, then you don't get any limits it
imposes. I suggest you try setting heap_chunk_in_mb using the *exact*
regtool invocation given here:
http://cygwin.com/cygwin-ug-net/setup-maxmem.html

And then *make sure you have closed all cygwin processes*. Reboot if
necessary. Then retry.

Max.


--
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/

- Raw text -