I have also seen the XercesC XML parsers fail when element content contains an invalid Unicode codepoint esp. octets in range of 0x80 - 0xBF that do not represent a true and valid UTF-8 encoding.
The problem is how to recover from XercesC XMLreader crashes. The XalanC processors uses XercesC for reading XML. - Steven J. Hathaway > Crash (pure virtual method call) when included file is not well formed XML > -------------------------------------------------------------------------- > > Key: XALANC-717 > URL: https://issues.apache.org/jira/browse/XALANC-717 > Project: XalanC > Issue Type: Bug > Components: XalanC > Affects Versions: 1.10 > Reporter: Christian Luidolt > Assignee: Brian Minchau > > > create a .xsl file which includes antoher .xsl file (using xsl:include) > which in not well-formed XML, e.g. has garbage at the end of the file. > > When executing XalanTransformer::transform() the program crashes (virtual > method call) because the locator has already been freed. > > The reason for the crash is that the Locator of the included file has been > pushed onto the locator stack by the StylesheetHandler but has not been > removed because the endDocument callback has not been called. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org > For additional commands, e-mail: xalan-dev-h...@xml.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org For additional commands, e-mail: xalan-dev-h...@xml.apache.org
