Valgrind claims there is unfreed memory. Is this bad?

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.

Answer 1

The valgrind message still reachable: 568 bytes in 1 blocks. means that there was memory freed in your application which is still "reachable", which means that you still have a pointer to it somewhere. At shutdown, this probably means a global variable of some kind. However, since the number of bytes "definitely leaked" or "probably leaked" is zero, this condition is completely benign. Don't worry about it.