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 From: "Dave Korn" To: Subject: RE: I: G77 160 MB memory allocation limit Date: Fri, 29 Apr 2005 10:39:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" In-Reply-To: <20050429082749.GM2572@calimero.vinschen.de> Message-ID: X-OriginalArrivalTime: 29 Apr 2005 09:39:54.0999 (UTC) FILETIME=[66508070:01C54C9F] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j3T9eZbH012415 ----Original Message---- >From: Corinna Vinschen >Sent: 29 April 2005 09:28 > On Apr 27 17:19, Impagnatiello Fabrizio wrote: >> again >> >> -----Messaggio originale----- >> Da: Impagnatiello Fabrizio >> Inviato: mercoledì 27 aprile 2005 17.15 >> No error message, just exit. >> >> After investigation (WEB/mailing list) and testing programs I discovered >> and verified that a new near 160 MByte allocation limit is induced by >> cygwin1.dll >> >> Simple programs compiled with -mno-cygwin flag may allocate up to 1920 >> MByte. > Please try the latest Cygwin snapshot from http://cygwin.com/snapshots/. > I tested it with a large array of 1500 Megs in a pretty small application. I can confirm that it fixes the NULL dereference in set_myself that I was investigating! cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/