[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Memory leak in bison 1.35

From: Akim Demaille
Subject: Re: Memory leak in bison 1.35
Date: 04 Sep 2002 14:05:22 +0200
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter)

>>>>> "Ignasi" == Ignasi Villagrasa <address@hidden> writes:

>> Hm, are you sure it is really yyparse per se which is guilty, and
>> not the user actions themselves?

Ignasi> Yes, I could isolate a program loop in order to test it with
Ignasi> and without yyparse.  When using yyparse, the memory leak
Ignasi> appears.

That's no proof that yyparse itself is guilty: it can be your
actions.  Check them, look where they allocate memory.  Make sure that
if the scanner does strdups or mallocs, then the parser gets these
memory bits and frees them.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]