Related articles |
---|
Memory leak in flex generated file pavel.orehov@gmail.com (pavel.orehov@gmail.com) (2005-10-20) |
Re: Memory leak in flex generated file haberg@math.su.se (2005-10-23) |
Re: Memory leak in flex generated file gneuner2@comcast.net (George Neuner) (2005-10-23) |
Re: Memory leak in flex generated file johnmillaway@yahoo.com (John Millaway) (2005-10-26) |
Re: Memory leak in flex generated file Markus.Elfring@web.de (2005-10-26) |
Re: Memory leak in flex generated file haberg@math.su.se (2005-10-27) |
Re: Memory leak in flex generated file haberg@math.su.se (2005-10-27) |
Re: Memory leak in flex generated file johnmillaway@yahoo.com (John Millaway) (2005-10-27) |
Re: Memory leak in flex generated file johnmillaway@yahoo.com (John Millaway) (2005-10-29) |
Memory leak in flex generated file pierreir@look.ca (Pierre Innocent) (2007-08-20) |
[1 later articles] |
From: | John Millaway <johnmillaway@yahoo.com> |
Newsgroups: | comp.compilers |
Date: | 26 Oct 2005 14:18:14 -0400 |
Organization: | Compilers Central |
References: | 05-10-140 |
Keywords: | lex, comment |
Posted-Date: | 26 Oct 2005 14:18:14 EDT |
Hi, This was fixed years ago. The last work done on Flex can be found at
http://lex.sourceforge.net/ -John
--- "pavel.orehov@gmail.com" <pavel.orehov@gmail.com> wrote:
> Hi,
> I am using flex and bison to parse HTTP headers. After some
> investigation i found a memory leak in flex generated file with
> valgrind tool.
[This is a variant version of flex, not the one that is distributed
with the GNU tools. They've made a lot of changes to it and I haven't
looked at them in enough detail to know how much I like what they've
done. -John]
Return to the
comp.compilers page.
Search the
comp.compilers archives again.