You do not give much info about what is leaking, so it could just as
well be in your actions. The Bison generated parser used to leak for
various strings that had not been translated from the C-subset of C++
to say using std::string, but I am not sure about the matter nowadays.
On 27 Apr 2006, at 14:44, Steffen Köhler wrote:
Hi,
I'am using Visual C++.Net 7.1 and Bison 2.1.
Now I have found out, that every call of yyparse() created a lot of
blocks which are 28bytes long.
I'am using
_CrtMemState s1;
_CrtMemCheckpoint(&s1);
yyparse();
_CrtMemDumpAllObjectsSince(&s1);
to detect this memory leak.
Is the an function to clear the memory allocated by bison? What can
I do, or it is a bug?
Thanks for any help
Steffen
_______________________________________________
[email protected] http://lists.gnu.org/mailman/listinfo/help-bison
_______________________________________________
[email protected] http://lists.gnu.org/mailman/listinfo/help-bison