|
From: Tom H. <to...@co...> - 2005-09-12 13:08:56
|
In message <200...@ge...>
Christian Parpart <tr...@ge...> wrote:
> I guess it's time to ask what the difference between those leaks is.
> definitely lost, I guess, means that my own app mmap()d them,
> indirectly lost, I guess, is memory that's lost because something else has not
> been freed (however vg detects this).
> and still reachable? all lost bytes shall be reachable somehow.
It's quite simple:
- Definitely lost means that a block of memory has not been freed
and valgrind cannot find any pointers to it
- Possibly lost eans that a block of memory has not been freed
and valgrind cannot find any pointers to the start of it but
can find at least one pointer into the middle of it
- Indirectly lost means that a block of memory has not been freed
and all the pointers to it that valgrind can find are in other
blocks marked as lost
- Still reachable means that a block of memory has not been freed
but there are still valid pointers to the start of that block in
registers or memory that has not been freed
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|