Hello List: On 27/01/12 10:12, Hilmar Preusse wrote:
On 26.01.12 Jerome BENOIT (g6299304p@rezozer.net) wrote: Hello List:is libkpathsea really subjet to numerous memory leaks ? If yes, is there any plan to fix them?I just asked google for an opinion and found at least one fixed in libkpathsea as of April 2011 (i.e. not yet packaged in Debian). Hoiw detailed are these valgrind reports. Is it even possible to determine the code block, which cause the leaks? This would it make more easy to determine if the problems are fixed in upsttream.
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. Is there any interest for the Debian TeX Task Force to get a memory leaks free kpathsea ? Regards,Jerome
Regards, Hilmar