X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Mon, 14 Mar 2016 15:26:08 +0100 (CET)
X-X-Sender: igor2 AT igor2priv
To: geda-user AT delorie DOT com
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] pcb: more memory leaks (Bonus track: a short story
 on valgrinding the parser)
In-Reply-To: <alpine.DEB.2.00.1603141421160.7885@igor2priv>
Message-ID: <alpine.DEB.2.00.1603141522570.7885@igor2priv>
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1603130700180 DOT 7885 AT igor2priv> <alpine DOT DEB DOT 2 DOT 00 DOT 1603141421160 DOT 7885 AT igor2priv>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On Mon, 14 Mar 2016, gedau AT igor2 DOT repo DOT hu wrote:

>
> 1. Easy

> - there's still a leak by flex; it keeps a buffer allocated, but I don't see 
> any trivial way to free it.

Turned out it's simpler than I thought: just need to call yylex_destroy() 
at the end (r1288). Should be easy to do in mainline as well.

(This allocation is for the lex buffer stack. It's allocated once then 
grown as needed, but potentially reaches some top early on, and the top 
should be a few 10 bytes. Shouldn't depend on the number of parses. Not a 
critical leak.)