From:	"Jongwhan Lee" <leejw51 AT hitel DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	flex bison bug?
Date:	Tue, 7 Sep 1999 17:35:54 +0900
Organization:	Korea Telecom
Message-ID:	<7r2hvn$ja5$1@news2.kornet.net>
NNTP-Posting-Host:	210.121.173.60
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2314.1300
Lines:	22
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I am using flex and bison with visual c++ 6.0

in debug mode,
I encounter this message when I close the window.

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).

Somewhere in Lex, the buffer allocated by malloc isn't freed.(my guess)

Should I ignore this notice?
Am should I override FLEX and BISON definition and function to avoid this
error message?

- Raw text -