[Valgrind-users] Interpretation of reachable in log file

[Barrie W. <bw...@cs...>]

Hi,

I wonder if someone can help me interpret the following:

==11846== 428184 bytes in 1839 blocks are still reachable in loss record 345
of 347
==11846==    at 0x4002965E: malloc (vg_replace_malloc.c:153)
==11846==    by 0x40C3D07C: pn_malloc (in /projects/.....so)
==11846==    by 0x807C6D2: DN_List_New (dn_list.c:38)
==11846==    by 0x80813F6: HelmList_Init (helm_list.c:44)
==11846==    by 0x808DA5A: Helm_InitGlobals (helm_globals.c:58)
==11846==    by 0x8075385: dn_initialise (dn_main.c:950)
==11846==    by 0x80740B7: main (main.c:145)
==11846==    by 0x41189A46: __libc_start_main (in /lib/libc-2.3.2.so)
==11846==    by 0x8062250: ??? (start.S:81)

This call tree should definitely be being called only once.

==11846== Startup, with flags:
==11846==    --suppressions=/usr/mlocal/lib/valgrind/default.supp
==11846==    -v
==11846==    --logfile=diag.val
==11846==    --num-callers=20
==11846==    --leak-check=yes
==11846==    --show-reachable=yes
==11846==    --alignment=8

Thanks
Barrie