I have a c++ code and I am checking the memory leak via valgrind. The result is as follows:
==== LEAK SUMMARY:
==== definitely lost: 0 bytes in 0 blocks
==== indirectly lost: 0 bytes in 0 blocks
==== possibly lost: 5,068,885 bytes in 341 blocks
==== still reachable: 0 bytes in 0 blocks
==== suppressed: 0 bytes in 0 blocks
====
I have read about the "possibly lost" case in the manual, but I am not sure if it is a big problem. Do you know what can cause this lost? Where should I check in my code to eliminate it? Is it a good action to leave as is?
Thanks