Re: Memory leak in flex generated file

John Millaway <johnmillaway@xxxxxxxxx> wrote:

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

> Hi, This was fixed years ago. The last work done on Flex can be found at
> http://lex.sourceforge.net/ -John

I think that the latest Flex version will still leak the character buffer
it allocates.

--
Hans Aberg
.

Relevant Pages

  • Re: Memory leak in flex generated file
    ... > I am using flex and bison to parse HTTP headers. ... > investigation i found a memory leak in flex generated file with ... > valgrind tool. ...
    (comp.compilers)
  • Memory leak in flex generated file
    ... I am using flex and bison to parse HTTP headers. ... investigation i found a memory leak in flex generated file with ... valgrind tool. ... Since the state stack is rarely large and is reused on subsequent runs, ...
    (comp.compilers)
  • Re: Memory leak in flex generated file
    ... There is no memory leak in the flex generated ... scanner. ... yyfree; ...
    (comp.compilers)
  • Re: Csup cvsmode build discussion
    ... lex and yacc files that I would like to discuss. ... I implemented the RCS parser required to operate on RCS files ... I've been compiling the parser and tokenizer with the help of bison ... Now, the base system already have flex, but the flex version in base is heavily ...
    (freebsd-hackers)
  • Csup cvsmode build discussion
    ... lex and yacc files that I would like to discuss. ... I implemented the RCS parser required to operate on RCS files ... I've been compiling the parser and tokenizer with the help of bison ... Now, the base system already have flex, but the flex version in base is heavily ...
    (freebsd-hackers)