> Hi.
>
> I am using 1.7.0 in multithread environment. Each thread has it's
> own SAXParser and according to xerces FAQ the SAXParser is thread
> safe when no multithread accesses to one SAXParser instance. But
> if I do not synchronize the call to parse method, the module cores.
> See below the core stack.
>
> Any ideas why?
>
> Tnx a lot.
>
> [1] DOMStringHandle::operator new(0x4000, 0x3c00, 0x3f68,
> 0xffffffff7b863950, 0x1034477e7, 0x1034477e7), at
> 0xffffffff7b627c34
> [2] DOMStringHandle::createNewStringHandle(0x25, 0x0,
> 0xffffffff7b8d7190, 0x24, 0x0, 0x2f), at 0xffffffff7b627da4
> [3] DOMString::DOMString(0xffffffff76602d88, 0x1013fb190,
> 0x5, 0xffffffff7af630b0, 0xffffffff7b207958,
> 0xffffffff7b30bf18), at 0xffffffff7b627f20
A number of thread-safety bugs have been fixed since Xerces-C 1.7,
including this race condition in DOMStringHandle. I suggest you upgrade to
the latest version. That version is quite old.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
