|
From: Sree H. T. <tot...@in...> - 2012-09-11 10:23:41
|
Hello,
I couldn't understand the following leak reported by Valgrind:
==26780== 304 bytes in 1 blocks are still reachable in loss record 51 of 59
==26780== at 0x402CE68: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==26780== by 0x41DD1C5: make_request (check_pf.c:249)
==26780== by 0x41DD63E: __check_pf (check_pf.c:342)
==26780==
==26780==
==26780== ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ---- y
{
<insert_a_suppression_name_here>
Memcheck:Leak
fun:malloc
fun:make_request
fun:__check_pf
}
==26780== LEAK SUMMARY:
==26780== definitely lost: 0 bytes in 0 blocks
==26780== indirectly lost: 0 bytes in 0 blocks
==26780== possibly lost: 0 bytes in 0 blocks
==26780== still reachable: 304 bytes in 1 blocks
==26780== suppressed: 11,542 bytes in 156 blocks
==26780==
==26780== For counts of detected and suppressed errors, rerun with: -v
==26780== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
There is no file check_pf.c as part of my source code. It seems to be a
part of glibc. Does this mean that there is a leak in libc?
I'm using Valgrind-3.7.0 and libc 2.15.
Regards,
Sree Harsha
|