Date:	Wed, 25 Aug 1999 13:24:50 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Dan Gold <TedMat AT CoastNet DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Free is not working? Anyone else having this problem?
In-Reply-To:	<199908241024.GAA09663@delorie.com>
Message-ID:	<Pine.SUN.3.91.990825132143.2834Q-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 25 Aug 1999, Dan Gold wrote:

> I have tested and tested to see if there is still memory allocated after I
> malloc() it and free() it.  The result is always yes!

See section 15.2 of the FAQ, it explains this.

> wanted to know if anyone else has the same problem, I think there may have
> been a thread earlier  about malloc or something in that area having a bug.
> Well if there is a patch or something, could someone let me know?

It's not a bug, so don't bother looking for a patch.  The FAQ explains 
why this happens and why you shouldn't bother.

> and
> another thing, when updating to a newer version of gcc and gpp is the only
> thing you have to do unzipping them and replacing the old files...?

It is always safer to remove the old compiler files completely before 
installing the new ones.  Section 4.8 of the FAQ shows one easy way of 
doing that.

- Raw text -