|
From: Simone M. <sma...@gm...> - 2009-07-14 05:55:37
|
Hi Nicholas, Thanks for the hint. Good to know all this. Best, S. On Jul 14, 2009, at 3:49 AM, Nicholas Nethercote wrote: > On Mon, Jul 13, 2009 at 8:27 PM, simone > marras<sma...@gm...> wrote: >> ==18862== >> ==18862== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 >> from 0) >> ==18862== malloc/free: in use at exit: 4,436 bytes in 9 blocks. >> ==18862== malloc/free: 9 allocs, 0 frees, 4,436 bytes allocated. >> ==18862== For counts of detected errors, rerun with: -v >> ==18862== searching for pointers to 9 not-freed blocks. >> ==18862== checked 1,124,356 bytes. >> ==18862== >> ==18862== LEAK SUMMARY: >> ==18862== definitely lost: 0 bytes in 0 blocks. >> ==18862== indirectly lost: 0 bytes in 0 blocks. >> ==18862== possibly lost: 0 bytes in 0 blocks. >> ==18862== still reachable: 0 bytes in 0 blocks. >> ==18862== suppressed: 4,436 bytes in 9 blocks. > > The Mac libc allocates some memory with malloc() but never frees it. > There are some suppressions for this in darwin9.supp, which becomes > part of default.supp, so that these aren't reported as leaks, because > you have no control over them. > > The moral of the story is: the code you write is not the only code > being run. > > Nick |