Re: Memory Leak?

Hi Chris,

There are two MAJOR core issues with XML-Xerces at the moment:
1) Memory leaks
2) Multiple Inheritance strangeness with the DOMNode hierarchy

Because I've been unable to debug these in the past, I've taken a new
approach - completely re-build XML-Xerces from the ground up. This is
not a code rewrite because all I am doing is constructing a SWIG
interface file, Xerces.i, which enables SWIG to autowrap Xerces-C. 

Xerces is a rather large API - at last count I am wrapping 108
different header files. 

So to make debugging simple I am starting over from scratch - only
wrapping the barest minimum of files to get working tests - and then
testing all aspects of the system - including memory leaks.

With only 10 headers wrapped, I get the basic XercesDOMParser
implementation, and the good news is:

  NO MEMORY LEAKS!!

So I am going to slowly add the other DOM components and check my
progress until I have recreated the complete API and located the
problems.

I am building this against the Xerces-C-2.6 from CVS, and I am happy
to make my intermediate builds available for your testing. What are
the API's which you desperately need for your application - I will be
happy to include them in my testing.

Cheers,
jas.