X-Spam-Check-By: sourceware.org
Date: Sat, 31 Dec 2005 04:27:45 +0100
From: "Gerrit P. Haase" <gerrit AT familiehaase DOT de>
Reply-To: "Gerrit P. Haase" <gerrit AT familiehaase DOT de>
Message-ID: <105831618454.20051231042745@familiehaase.de>
To: "Dan Stratila" <dstrat AT MIT DOT EDU>
CC: cygwin AT cygwin DOT com
Subject: Re: gcc crash (memory?)
In-Reply-To: <000101c60db1$74b94830$43055f12@somerville>
References: <000101c60db1$74b94830$43055f12 AT somerville>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Dan,

>> I use gcc 3.4.4.  I have also this famous registry key defined:
>> In "HKLM\SOFTWARE\Cygnus Solutions\Cygwin" define a DWORD named
>> heap_chunk_in_mb and set the value to 1024 (decimal) or 400 (hex) or
>> even more.
>> 
>> This may require a reboot to take affect.

> It turns out (a part of) the problem was that malloc and new allocate twice
> the amount of memory requested (see the thread "malloc/new allocate twice as
> much?"). Installing the latest snapshot solves this problem, and I am now
> able to compile polymake with g++ taking at most ~600MB. (It took 1.5GB on
> Red Hat Enterprise Linux 4, but I guess that's because that machine is
> 64-bit.)

Interesting, so the next Cygwin release will always use only the half
amount of memory than before, sounds nice ;)  Glad to hear about this.


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


Gerrit
-- 
=^..^=



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