On 12/5/11 2:46 PM, Steven Schveighoffer wrote: > But what's difficult is finding leaks which don't have any anchor to > search for. For example, how do you search for code that allocates an > array and *doesn't* deallocate it? By using a decent memory debugger/profiler like Valgrind? David