Re: is libkpatsea memory leak free ?
On 27.01.12 Jerome BENOIT (firstname.lastname@example.org) wrote:
> As concerns memory leaks, valgrind enables to get where a non freed
> object was allocated: function calls are traced back. To see where
> to properly free is missing is a human task.
So, the functions calls are visible?
> Is there any interest for the Debian TeX Task Force to get a memory
> leaks free kpathsea?
Well, kpathsea is mostly not used by server processes, which run
hours, days, etc. Hence a small memory leak is not *that* important
(IMHO). If you're willing to identify them feel free to do so and
report them upstream. But I'd rather use the kpathsea from TL 2011,
not the outdated version in Debian.
Would you *______really* want to get on a non-stop flight?
-- George Carlin