[
https://issues.apache.org/jira/browse/XERCESC-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov resolved XERCESC-740.
-------------------------------------
Resolution: Won't Fix
Assignee: (was: Xerces-C Developers Mailing List)
I don't think we will be supporting IRIX in any future versions unless someone
with knowledge and access will step up to maintain it (in which case feel free
to reopen this bug).
> IRIX and nonexistant schemas
> ----------------------------
>
> Key: XERCESC-740
> URL: https://issues.apache.org/jira/browse/XERCESC-740
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (Schema) (Xerces 1.5 or up only)
> Affects Versions: 2.1.0
> Environment: Operating System: Other
> Platform: Other
> Reporter: Richard Balint
>
> IRIX 6.5 will consistantly SIGSEGV or SIGBUS when cleaning up after it
> encounters the fatal error of a schema file not being able to be opened. (in
> my
> case via http). This of course assumes schema validation is turned on. :)
> Seems to be a bug where ~XMLReader is getting called too many times,
> particularly from ReaderMgr::reset. In this case it gets reset once, then the
> fCurReader is passed to it again with a non-null, and non-valid value. For
> example, calling ~XMLReader on a fCurReader who equals 0x4 will definitely
> cause
> a SIGSEGV. :)
> SOMETHING is overwriting the fCurReader in ReaderMgr to a completely invalid
> value.
> This is reproducable with PParse -n -s -f and any xml file that calls an
> invalid schema on IRIX. Seems to clean up fine in Linux.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
