Package: libprocps0
Version: 1:3.3.3-7
We're using libprocps as below:
PROCTAB* proc = openproc(PROC_FILLARG | PROC_FILLSTAT);
proc_t proc_info;
// zero out the allocated proc_info memory
memset(&proc_info, 0, sizeof(proc_info));
while (readproc(proc, &proc_info) != NULL) { // <<!!!!!! here is the
leak !!!!!!
// do something
}
closeproc(proc);
When run:
valgrind --trace-children=yes --track-fds=yes -v --leak-check=full
--show-reachable=yes program
It report memory leak:
==11397== 131,072 bytes in 1 blocks are still reachable in loss record 6
of 7
==11397== at 0x4C2C5DB: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==11397== by 0x5056267: xmalloc (in /lib64/libprocps.so.1.1.0)
==11397== by 0x505A938: openproc (in /lib64/libprocps.so.1.1.0)
==11397== 131,072 bytes in 1 blocks are still reachable in loss record 7
of 7
==11397== at 0x4C2C5DB: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==11397== by 0x5056267: xmalloc (in /lib64/libprocps.so.1.1.0)
==11397== by 0x505A949: openproc (in /lib64/libprocps.so.1.1.0)
I look into the code in readproc.c , it looks
memory is alloc for static char src_buffer,
dst_buffer;
define MAX_BUFSZ 1024642, but no free found
We are using Debian squeeze,libc6 2.11.3-4. self compiled kernel 3.4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
