delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1998/11/14/20:36:22

From: Pierre DOT Humblet AT eurecom DOT 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 DOT Humblet AT eurecom DOT fr (Pierre A. Humblet)
Mime-Version: 1.0
To: Mumit Khan <khan AT xraylith DOT wisc DOT edu>,
Derrick Franceschini <francesd AT adstii DOT com>
Cc: gnu-win32 AT cygnus DOT 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 AT prep DOT ai DOT mit DOT edu

Pierre

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019