DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22031>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22031 memory leak when terminate Xalan ------- Additional Comments From [EMAIL PROTECTED] 2003-07-31 21:20 ------- I would suggest the following strategy for testing on Solaris, to determine if this really is a leak: 1. Choose one of these extension functions for testing and add a dummy copy constructor. 2. Put testing code in the destructor, and all constructors of this function so you can track what is created and destroyed. Part of this information should be the this pointer, so you can correlate that to the memory leaks that are being reported. 3. Verify that all instances created are also deleted. 4. If leaks are reported you should be able to compare the this pointers to the memory blocks that are "leaking." They may not be exact, but they should be close. If there are no mismatched constructor/destructor pairs, I think you can assume this is a false positive.
