The requirements are spelled out explicitly here:
http://xml.apache.org/xalan-c/index.html Later Service Packs may not need the Dinkumware fixes, but you will need to rebuild the binaries to use a later version of the compiler. This bug has nothing to do with the Dinkumware fixes. You're mixing run-times: http://xml.apache.org/xerces-c/faq-build.html#faq-11 Dave "Shang, Crystal" <Cshang@rsasecur To: [EMAIL PROTECTED] ity.com> cc: "Huynh, Dung" <[EMAIL PROTECTED]>, (bcc: David N Bertoni/Cambridge/IBM) Subject: XalanDOMString::trancode() crashes 04/05/2002 04:08 PM Please respond to xalan-dev Hi, The following code crashes on my system: XalanDOMString myString = XalanDOMString("Xalan String"); myString .transcode(); The call stack is as follows: NTDLL! 77f762e8() NTDLL! 77f83274() KERNEL32! 77f12dfd() _CrtIsValidHeapPointer(const void * 0x009963a0) line 1606 _free_dbg(void * 0x009963a0, int 0x00000001) line 1011 + 9 bytes operator delete(void * 0x009963a0) line 49 + 16 bytes std::allocator<char>::deallocate(void * 0x009963a0, unsigned int 0x00000008) line 64 + 38 bytes std::vector<char,std::allocator<char> >::~vector<char,std::allocator<char> >() line 60 XALAN_XPATH::DoXPathEvaluation(DOMSupport * 0x0012fe64, XalanDocument * 0x009966a0) line 99 -- this is where transcode() is being called. Am I doing things in the right sequence/configuration? Is this a bug? Do I need to have Dinkum C++ library fixes installed? Thanks a lot! - Crystal
