Re: [Valgrind-users] When I test ls using valgrind, Why are malloc/free numbers mistaken?

[Dave S. <dav...@fa...>]

On Thu, 24 May 2007 00:57:48 +0900, "임근식"
<in...@ha...> said:
> ==9049== malloc/free: in use at exit: 13,165 bytes in 10 blocks. 

10 blocks in use at exit.

> ==9049== malloc/free: 85 allocs, 75 frees, 27,309 bytes allocated. 

85 allocs - 75 frees = 10 blocks in use at exit.

> ==9049== LEAK SUMMARY: 
> ==9049==    definitely lost: 0 bytes in 0 blocks. 
> ==9049==      possibly lost: 0 bytes in 0 blocks. 
> ==9049==    still reachable: 13,165 bytes in 10 blocks. 
> ==9049==         suppressed: 0 bytes in 0 blocks. 

10 blocks still reachable at exit.  So 10 blocks could have been freed
by the app, because it had a pointer to them, but weren't.

Dave.
-- 
  Dave Slutzkin
  Melbourne, Australia
  dav...@fa...