|
From: | Ivan Vučica |
Subject: | Re: Memory leaks galore! |
Date: | Wed, 20 Feb 2013 19:50:47 +0100 |
A quick response via phone: On 20. 2. 2013., at 19:00, Jamie Ramone <address@hidden> wrote:
You will have to look up the old thread, or wait for someone with more understanding to chime in.
If my understanding is correct, the code isn't even there. You could write something using a C++ destructor trick using a global variable that will get destructed at exit no matter what (well, unless you have a very nasty crash). But you'd have to write code to perform these free()s. There is probably some way of telling Valgrind to ignore certain leaks, right?
I'm afraid I cannot help more than this. Who knows how much Valgrind would help with Cocoa?
|
[Prev in Thread] | Current Thread | [Next in Thread] |