X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 11 Mar 2011 14:14:40 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: ld: fatal error - cmalloc would have returned NULL Message-ID: <20110311131440.GG7064@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4D7A0E10 DOT 3000808 AT emrich-ebersheim DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4D7A0E10.3000808@emrich-ebersheim.de> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mar 11 12:57, Rainer Emrich wrote: > On Mar 1 18:39, Corinna Vinschen wrote: > > And then ld crashes, because, apparently, it neglects to check the > > return value of mmap. > > Yes it's a fault to not check the return value of mmap, but that wouldn't help > here either. > > So, the solution for me was to increase the cygheap size. The maximum seems to > be 1792 MBytes. This solves the issue for boostrapping gcc with libjava enabled, > but may fail for even larger libraries. I don't think you mean to change the size of the cygheap to 1792 Megs, do you? This sounds impossible to me. Keep in mind that you only have 2 Gigs total memory available per application. The cygheap size is usually 1 MByte, + the number of pages to align the end of the cygheap section to the next 64K boundary. In a case like this you can increase the cygheap to, say, 2 Megs + alignment, but that should be enough for all cases which fit into memory at all. Otherwise, ld should use temporary files to store intermediate data. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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