Hi all, I'm seeing a crash when an IGXMLScanner held statically is destroyed. I'm using Xerces 2.3.0 on linux compiled with gcc 3.2. The stack trace is as follows:
#0 0x4123e679 in chunk_free (ar_ptr=0x412f2500, p=0x810da08) at malloc.c:3243 #1 0x4123e424 in __libc_free (mem=0x810da10) at malloc.c:3155 #2 0x08072783 in operator delete(void*) (ptr=0xbbaa050) at #3 0x40d38c39 in xercesc_2_3::MemoryManagerImpl::deallocate(void*) () #4 0x40dd6991 in xercesc_2_3::XMemory::operator delete(void*) () #5 0x40d2b4e3 in xercesc_2_3::RefVectorOf<xercesc_2_3::KVStringPair>::~RefVectorOf() () #6 0x40d25806 in xercesc_2_3::IGXMLScanner::cleanUp() () #7 0x40d24dfd in xercesc_2_3::IGXMLScanner::~IGXMLScanner() () I don't know if this is the cause of the crash, but it seems that the wrong type of delete is called on the memory in fRawAttrList. It's allocated using placement new with fMemoryManager (in buildAttList), but it's deleted with the normal delete operator (in ~RefVectorOf), which doesn't seem correct. I'm not customising the memory management in any way. Any insight would be appreciated. cheers, Graham. -- Graham Bennett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
