Re: [naviserver-devel] make memcheck / valgrind

[Bernd E. <eid...@we...>]

> > But the results on my local box are... a little bit scary right now.
>
> ... scary is relative. So, how scary is your "scary", really?

Scary for me, the ignorant :-)


==3781== ERROR SUMMARY: 18 errors from 9 contexts (suppressed: 106 from 1)
==3781== malloc/free: in use at exit: 148,617,748 bytes in 4,027 blocks.
==3781== malloc/free: 6,481 allocs, 2,454 frees, 183,008,167 bytes allocated.
==3781== For counts of detected errors, rerun with: -v
==3781== searching for pointers to 4,027 not-freed blocks.
==3781== checked 258,234,212 bytes.

==3781== LEAK SUMMARY:
==3781==    definitely lost: 72 bytes in 5 blocks.
==3781==    indirectly lost: 120 bytes in 10 blocks.
==3781==      possibly lost: 139,672,920 bytes in 2,504 blocks.
==3781==    still reachable: 8,944,636 bytes in 1,508 blocks.
==3781==         suppressed: 0 bytes in 0 blocks.

(this is the non-vtmalloc-default result)

> (BTW, if I were you, I would turn ANY "clever" memory allocator and use
> malloc/free everywhere when debugging memory.)

My idea was: Give vtmalloc a try (as freeing memory always is nice, we have 
lots of memory intense XML import stuff to do) - but as I've never used it 
before, i ran into this appealing "memcheck" option ...

> As from our experience... if we leak (which is not unlikely) then
> it is far from scary, as otherwise I'd already pull-out all my hair.
> However, when looking in the mirror, I can say we are not leaking.

There is no correlation, believe me: We ware not leaking also, but our 
hairs... :-)

cu
BE