[
https://issues.apache.org/jira/browse/XERCESC-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Massari resolved XERCESC-1021.
--------------------------------------
Resolution: Fixed
Fix Version/s: 3.1.0
Assignee: Alberto Massari (was: Xerces-C Developers Mailing List)
A fix is in SVN
> RegularExpression: wrong Match end for fixed string match
> ---------------------------------------------------------
>
> Key: XERCESC-1021
> URL: https://issues.apache.org/jira/browse/XERCESC-1021
> Project: Xerces-C++
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 2.3.0
> Environment: Operating System: All
> Platform: All
> Reporter: Dave Cohrs
> Assignee: Alberto Massari
> Fix For: 3.1.0
>
> Attachments: xercesbug.cpp
>
>
> RegularExpression::matches() calls context->fMatch->setEndPos()
> with the wrong value when doing a fFixedStringOnly match and not
> in XMLSCHEMA_MODE (i.e. a fixed string match using a Perl-like pattern).
> The problem is this line of code (line 546 of RegularExpression.cpp in
> the 2.3 src distro):
> context->fMatch->setEndPos(0, ret +
> strLength);
> strLength is the length of the "expression" parameter passed to matches().
> I believe the value really should be the length of fFixedString. As it
> currently exists, the call to setEndPos() generally sets a value that is
> beyond the end of "expression".
> This bug has no effect on XMLSCHEMA_MODE, which never uses this code.
--
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: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
