"Matthew Jones" wrote: >> Maybe this software is garbage but I have >> found that you have to take the output of Purify and >> BoundsChecker will a grain of salt.
I have no purify experience, but I have to agree with you on the BoundsChecker front. It's brilliant for spotting buffer overruns, and 'reading uninitialised memory' type error's but I don't trust it on leaks. POC, if you're interested I have custom versions of prmem.c and prmem.h with a small and simple (read inefficient and slow) memory tracker written in. It's only useful if you do all your memory allocation/deallocation using PR_Malloc,PR_Calloc,PR_Realloc and PR_Free, and you'd have to be prepared to build the NSPR with it yourself......but it's helped me a lot in getting rid of leaks from a fairly heavily multithreaded middle tier type app. David Hicks ----------------- Software Engineer
