From: Pierre.Humblet@eurecom.fr (Pierre A. Humblet)
Subject: Re: Why would malloc return NULL?
14 Nov 1998 20:36:22 -0800
Message-ID: <3.0.5.32.19981114150252.00899740.cygnus.gnu-win32@pop.ne.mediaone.net>
References: Pierre.Humblet@eurecom.fr (Pierre A. Humblet)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Mumit Khan <khan@xraylith.wisc.edu>,
        Derrick Franceschini <francesd@adstii.com>
Cc: gnu-win32@cygnus.com

At 09:43 AM 11/13/98 -0600, Mumit Khan wrote:
>On Thu, 12 Nov 1998, Derrick Franceschini wrote:
>
>> We have ported a large Unix application to NT using Cygwin (b19) and
>> seem to have a problem with malloc returning NULL when there is still
>> plenty of unused memory.  
[]

>Anytime this happens, I first suspect bugs in the code instead of the
>runtime. 
>
>I have code using 400M of RAM, in small and big chunks on Cygwin, and it
>works as advertised. That of course doesn't preclude bugs in Cygwin, but
>at least it shows it's not completely broken ;-)
>

In a related message I had reported a similar malloc problem happening in
gnu spell 1.0  Upon further examination the problem is indeed due a bug in
spell 1.0 and not to a bug in Cygwin. My apologies to Cygwin. I have
reported the problem to bug-gnu-utils@prep.ai.mit.edu

Pierre

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
