Re: Odd Error: 'coudn't commit memory for cygwin heap' during configuration of binutils

[Robert Collins]

Interesting!

I'd say that this is because cygwin allocates head for the command line, and
doesn't have a built-in limit (AFAIK).

libtoolers - perhaps the max command line test should stop somewhere before
the multi-megabyte point ?

Rob

----- Original Message -----
From: "Max Bowsher" <address@hidden>
To: "Cygwin Maillist" <address@hidden>
Sent: Tuesday, July 10, 2001 9:28 PM
Subject: Odd Error: 'coudn't commit memory for cygwin heap' during
configuration of binutils


> Whilst configuring binutils for cross-compilation, I encountered the above
> error.
> (Binutils version is latest as of date of this mail)
>
> Whilst configuring libtool, the computer almost crashed, at the line
> 'findinf maximum length of command line arguments' or similar. (CPU
> utilization so high that mouse could only respond every ~10secs). This
ended
> with the error 'coudn't commit memory for cygwin heap Win32 error 8'.
Later,
> the same configure step showed the result '(cached) 2359297'
>
> This is hardly a critical error, since the build proceeded, but I thought
I
> would just bring it to your attention.
>
> Max.
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>