[ 
https://issues.apache.org/jira/browse/XALANC-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bill Blough updated XALANC-770:
-------------------------------
    Attachment: realworld1.xslt
                realworld1.xml
                realworld1.expected

To reproduce:

testXLST -validate -xsl realworld1.xslt -in realworld1.xml

> Possibly incorrect assertion in XalanSourceTreeDocument::createAttributes
> -------------------------------------------------------------------------
>
>                 Key: XALANC-770
>                 URL: https://issues.apache.org/jira/browse/XALANC-770
>             Project: XalanC
>          Issue Type: Bug
>          Components: XalanC
>    Affects Versions: 1.11
>         Environment: Debian GNU/Linux 8.6 (jessie), amd64
>            Reporter: Bill Blough
>            Assignee: Steven J. Hathaway
>            Priority: Minor
>         Attachments: realworld1.expected, realworld1.xml, realworld1.xslt
>
>
> As reported in Debian 
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783173), certain input 
> causes debug builds to fail with the following assertion error:
> debian_xalan-c_debug/xalan/t$ testXSLT -validate -xsl realworld1.xslt -in
> realworld1.xml
> xalan: 
> /tmp/buildd/xalan-1.11/c/src/xalanc/XalanSourceTree/XalanSourceTreeDocument.cpp:1206:
>  
> size_t
> xalanc_1_11::XalanSourceTreeDocument::createAttributes(xalanc_1_11::XalanSourceTreeAttr**,
> const AttributesType&, size_t, xalanc_1_11::XalanSourceTreeElement*,
> bool): Assertion `theColonIndex != length(theQName)' failed.
> However, release builds (with assertions disabled) process correctly and 
> yield the correct output.  This raises a question: Is the assertion logic  
> incorrect, or is the assertion logic correct and the successful processing  
> is the result of luck?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to