GLR C++ Parser leaks Memory

[Roland Kaminski]

Hi all,

I am using bison 2.6.5 and discovered that the GLR parser leaks memory when 
exceptions are used. I used the glr.cc skeleton and want to throw an exception 
after a certain amount of syntax errors. The memory is leaked by the glr-stack 
itself and not by any of my semantic values (they don't need destruction).

This is no show-stopper for me but it would be nice if the generated parser 
were exception safe. I attached some valgrind output that should indicate 
where the memory is leaked. Also note that if I switch to the larl1.cc 
skeleton, no memory is leaked. (But I cannot parse some input then.)

If you need a minimalistic example, I can create one. Just tell me.

Regards, Roland

valgrind.log
Description: Text Data

signature.asc
Description: This is a digitally signed message part.