From: Nicholas N. <nj...@ca...> - 2003-10-30 13:13:58
|
On Thu, 30 Oct 2003, Attila wrote: > 'could have freed'? Where this uncertainty comes from if > "calls to malloc/new/free/delete are intercepted"? 'could have freed' means that they weren't lost -- ie. you still had pointers to them in scope -- but that you didn't free them. > How can I make sure that they are freed for sure? Actually free them. > In other words how can I get rid of the still reachable > message if possible in this case and in general? Reachable memory isn't necessarily bad. Eg. if you have malloc'd blocks that are used right up until your program ends, there's not much point manually freeing them; that will just take time. N |