[
https://issues.apache.org/jira/browse/XALANC-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569960#comment-13569960
]
Steven J. Hathaway commented on XALANC-736:
-------------------------------------------
I was hasty in my response.
Going through the debug process, the problem appears to be in the
XalanDOMString.cpp methods where the
effective length of RHS = zero and the RHS.m-data = null. This causes a fault
in the Microsoft VC10 runtime
libraries.
Temporary workaround is to "Ignore" the debug assertion. The release build
does not trigger the Microsoft
VC10 runtime assertion and therefore works properly.
I am preparing a patch that should avoid some of these assertions when
debugging projects using
Microsoft Studio 2010 (VC10).
Sincerely,
Steven J. Hathaway
> Assertion failure in debug mode
> -------------------------------
>
> Key: XALANC-736
> URL: https://issues.apache.org/jira/browse/XALANC-736
> Project: XalanC
> Issue Type: Bug
> Affects Versions: 1.11
> Environment: Visual Studio 2010
> Binary package of Xerces 3.1.1
> Binary package of Xalan 1.11.0
> Reporter: Claudia Baier
> Assignee: Steven J. Hathaway
> Attachments: 736.diff, XercesXalanDemo.zip
>
>
> I have a problem running applications in debug mode. I try to process a xslt
> file which includes
> another xslt file. In release mode everything works fine. But in debug mode
> the application
> crashes with the message:
> "Debug Assertion Failed!
> ...
> Expression: invalid null pointer"
> This happens when I call
> theXalanTransformer.transform(*parsedXML, *xslIn, std::cout);
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
