#252 Prebuilt windows xalan 1.10 binaries can cause crash

open
nobody
5
2013-05-17
2013-05-17
Michael Chisholm
No

This crash was reported only on Windows.

The stacktrace as reported:

Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at xalanc_1_10.OutputString(basic_ostream<char\,std::char_traits<char> >* , UInt16* , MemoryManager* )
at xalanc_1_10.<<(basic_ostream<char\,std::char_traits<char> >* theStream, XalanDOMString* theString)
at XmlFileContentProbe.EvaluateXpath(XmlFileContentProbe* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* path, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* fileName, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* xpath)
at XmlFileContentProbe.CollectItems(XmlFileContentProbe* , Object* object)
at AbsProbe.Run(AbsProbe* , Object* object)
at AbsObjectCollector.ProcessObject(AbsObjectCollector* , Object* object)
at AbsObjectCollector.Process(AbsObjectCollector* , AbsObject* absObject)
at AbsObjectCollector.Run(AbsObjectCollector* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* objectId)
at AbsDataCollector.Run(AbsDataCollector* )
at main(Int32 argc, SByte** argv)
at _mainCRTStartup()

Simply rebuilding Xalan 1.10 from source using vc2010 solved the problem. So it doesn't appear to be an issue with ovaldi. Files which produced the crash are attached.

Discussion

  • Test definition

     
    Attachments
  • Target of test definition