Hi Dave, Yes I am. I downloaded and checked all my include paths and rebuilt it again. Happens only when I exit the application. The crash is in Xerces2_4::InputSource - the fMemoryManager seems to be already deleted. I am using VC6 debug build, and have set #define XML_PLATFORM_NEW_BLOCK_ALIGNMENT 16 in the xerces code. Thanks Kiran
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 11:33 AM To: [email protected] Subject: RE: Xalan 1.6 question Hi Kiran, OK, I just did some research on this, and it seems the fix is already in Xalan 1.6, and that it was a problem between 1.5 and 1.6. Are you sure you're using Xalan 1.6? Dave "Bagepalli, Kiran" To: <[email protected]> <[EMAIL PROTECTED] cc: (bcc: David N Bertoni/Cambridge/IBM) matica.com> Subject: RE: Xalan 1.6 question 12/08/2003 11:17 AM Sorry maybe I hit the reply all button. Is there a single file or few files which I can patch rather than bringing in the whole source again. Thanks Kiran -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 11:12 AM To: [email protected] Subject: Re: Xalan 1.6 question Hi Kiran, Please don't send questions directly to me -- it just gives me one more email to sort through. Yes, this is a known problem and is fixed in the latest CVS. You cannot use Xalan 1.6. with the Xerces-C 2.4, so you should either get the latest CVS, or use Xerces-C 2.3 until we can release compatible version of Xalan-C++. Dave "Bagepalli, Kiran" To: <[email protected]> <[EMAIL PROTECTED] cc: matica.com> Subject: Xalan 1.6 question 12/08/2003 10:52 AM is Xalan 1.6 compatible with xerces 2.4. I find that it crashes in XalanTransformer::terminate() that lands in InputSource::~InputSource with a bad pointer delete. Has anyone noticed this problem. Thanks Kiran
