What tools for memory leaks?

[Graham Miller <mi...@reactivity.com>]

Hello everyone.
 
What tools does the Xerces-C team use to hunt down memory leaks?  We've
spent a little bit of time here trying to nail down what appears to be a
Xerces leak in validating documents.  We got to the point where a
compiling SAXPrint.cpp using the dmalloc library indicated that a few
hundred bytes were being leaked by each call to SAXParser::parse.
SAXPrint of course calls XMLPlatformUtils::Terminate, so in theory, any
object pools should be cleaned up by the time dmalloc does its
accounting.  However we'd like to be able to verify our results with the
tools that other people are using.
 
Also, we looked through the recent CVS logs to see if anything had fixed
this since version 1.5.1 (which is what we are running), without much
luck.  However if we missed anything, a pointer would be much
appreciated.
 
Thanks in advance for your help.
 
graham