Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <03c201c2e289$445c45d0$78d96f83@pomello> From: "Max Bowsher" To: "Fabrizio Impagnatiello" , References: <20030304195846.05EB79FC63@mail.roma.alespazio.it> Subject: Re: Malloc array size limit (2) Date: Tue, 4 Mar 2003 20:04:30 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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/