ld: fatal error - cmalloc would have returned NULL

Rainer Emrich rainer@emrich-ebersheim.de
Fri Mar 11 14:13:00 GMT 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> On Mar  11 12:57, Corinna Vinschen wrote:
> 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.
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

>
> Otherwise, ld should use temporary files to store intermediate data.
>
On Linux or *nix this not a problem at all. But to be honest, I have only few
knowledge about ld.

Rainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk16KVAACgkQoUhjsh59BL6u2QCfTCBnGmLz+G7CvLK4UtsvSmBF
RIYAn0eJaq/gkj26TNETFmywVya/VvyP
=0Y7W
-----END PGP SIGNATURE-----

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



More information about the Cygwin mailing list