Date: Fri, 18 Mar 2011 02:08:21 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: ld: fatal error - cmalloc would have returned NULL
Message-ID: <20110318060821.GB15594@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4D7A2951 DOT 1030002 AT emrich-ebersheim DOT de> <4D82F1D8 DOT 1020608 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D82F1D8.1020608@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
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 Fri, Mar 18, 2011 at 05:47:04AM +0000, Dave Korn wrote:
>On 11/03/2011 13:53, Rainer Emrich wrote:
>
>> I have to be more clear. I increased the heap_chunk_in_mb to 1792 using:
>> regtool -i set /HKLM/Software/Cygwin/heap_chunk_in_mb 1792
>
>  I run with this setting all the time, I guess that's why I haven't seen this
>problem.  Before I did that (couple of years back) I also used to get crashes
>building libjava.

That setting should have nothing to do with cmalloc().  cmalloc is for
Cygwin's internal heap which has nothing to do with that setting.

Didn't Corinna already mention this?

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple