Date: Tue, 7 Sep 1999 14:23:27 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Jongwhan Lee <leejw51 AT hitel DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: flex bison bug?
In-Reply-To: <7r2hvn$ja5$1@news2.kornet.net>
Message-ID: <Pine.SUN.3.91.990907142140.27853Q-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 7 Sep 1999, Jongwhan Lee wrote:

> Detected memory leaks!
> Dumping objects ->
> {45} normal block at 0x00346E38, 16386 bytes long.
>  Data: <  rtex {  1 1  2> 00 00 72 74 65 78 20 7B 0A 09 31 20 31 20 20 32
> {44} normal block at 0x00431F70, 40 bytes long.
>  Data: < h% 8n4 8n4  @  > 08 68 25 10 38 6E 34 00 38 6E 34 00 00 40 00 00
> Object dump complete.
> The thread 0x199 has exited with code 0 (0x0).

I don't understand these messages.  How does VC decide that these are 
leaks?  A buffer that isn't freed when the program exits isn't 
necessarily a leak: it might have been used all the time before exit.