Le 11/03/2013 14:42, Kornel Benko a écrit :
==11211== LEAK SUMMARY:
==11211== definitely lost: 33,700 bytes in 189 blocks
==11211== indirectly lost: 59,454 bytes in 1,606 blocks
==11211== possibly lost: 15,783 bytes in 59 blocks
==11211== still reachable: 1,721,311 bytes in 8,392 blocks
==11211== suppressed: 0 bytes in 0 blocks
==11211== Rerun with --leak-check=full to see details of leaked memory
I see, I should rerun, oh well ... this may take a while ...
I am not sure there is so many leaks to find...
Another possibility is to use the 'massif' tool of valgrind. It will
tell you where the data is allocated.
JMarc
