Valgrind claims there is unfreed memory. Is this b

Question

Valgrind gives me the following leak summary on my code. However, I have freed all malloc'ed memory. Is this a bad thing, or is this normal? My program is in c.

==3513== LEAK SUMMARY:

==3513== definitely lost: 0 bytes in 0 blocks.

==3513== possibly lost: 0 bytes in 0 blocks.

==3513== still reachable: 568 bytes in 1 blocks.

==3513== suppressed: 0 bytes in 0 blocks.

Answer 1

Personally, I always keep forgetting and checking like valgrind make test which always adds at least couple of additional still reachable bytes... Make sure that Your application is being ran directly by valgrind... :)