Memory leak in bison-generated code

2009-02-06 Thread Jean Delvare
Hi all, Valgrind tells me that there's a memory leak in libsensors [1], in code which is generated by flex/bison: ==15124== 72 bytes in 1 blocks are still reachable in loss record 1 of 1 ==15124==at 0x4C25741: realloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so) ==15124==by

Re: Memory leak in bison-generated code

2009-02-06 Thread Hans Aberg
On 6 Feb 2009, at 17:54, Jean Delvare wrote: Valgrind tells me that there's a memory leak in libsensors [1], in code which is generated by flex/bison: ... I upgraded to bison 2.4.1. Alas, the memory leak is still there, and as a matter of fact I don't see any call to yylex_destroy() in th

Re: Memory leak in bison-generated code

2009-02-06 Thread Joel E. Denny
On Fri, 6 Feb 2009, Jean Delvare wrote: > Valgrind tells me that there's a memory leak in libsensors [1], in code > which is generated by flex/bison: > As this seemed to be the same problem as documented in this changelog > entry: > > 2006-11-10 Joel E. Denny > > Fix memory leaks in sc