Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <199904291459.JAA07415@modi.xraylith.wisc.edu>
X-Authentication-Warning: modi.xraylith.wisc.edu: localhost.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol
To: Chris Faylor <cgf AT cygnus DOT com>
cc: cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: malloc and free mixing in VC++ and cygwin 
In-reply-to: Your message of "Thu, 29 Apr 1999 10:50:50 EDT."
             <19990429105050 DOT A772 AT cygnus DOT com> 
Date: Thu, 29 Apr 1999 09:59:28 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Chris Faylor <cgf AT cygnus DOT com> writes:
> 
> You could use these routines to free the memory but you'd end
> up with a severely corrupted heap as far as cygwin is concerned.
> Cygwin's free() command does more than (potentially) return memory
> to the system.  In fact, it usually doesn't even return memory to
> the system.  It also keeps a list of all allocated memory for reuse
> by other malloc calls.  This is a pretty standard way of doing things.

Thanks for the clarification. I missed the ramifications.

Regards,


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com