Date: Fri, 30 Dec 2005 22:31:49 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: gcc crash (memory?)
Message-ID: <20051231033148.GA2322@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <000101c60db1$74b94830$43055f12 AT somerville> <105831618454 DOT 20051231042745 AT familiehaase DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <105831618454.20051231042745@familiehaase.de>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Sat, Dec 31, 2005 at 04:27:45AM +0100, Gerrit P. Haase wrote:
>> By the way, g++, as well as a program I wrote and compiled with g++, are
>> able to allocate 1GB, so I don't think the memory limitation / registry
>> switch issue exists in the latest snapshot.
>
>Well, at least it worked for me using the registry hack with the
>released Cygwin version 1.5.18.

The registry setting is still in the latest snapshot.  The latest
snapshot is quicker to use shared memory when it runs out of memory or
when a large chunk of memory is requested.  Corinna's recent changes to
shared memory handling in the snapshot have made using shared memory for
this purpose more attractive so we're using the same shared memory
settings in malloc as a normal UNIX system.

cgf


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