[pcre-dev] [Bug 1423] New: Bad condition when optimizing cha…

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1423
           Summary: Bad condition when optimizing character range checks
           Product: PCRE
           Version: N/A
          Platform: Other
        OS/Version: Windows
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Code
        AssignedTo: hzmester@???
        ReportedBy: hzmester@???
                CC: pcre-dev@???

Hi,

intended audience: maintainers of JIT enabled PCRE libraries.

when I reworked the character range checks, I noticed that I introduced a wrong
condition check in revision 992 (JIT only). According to the SVN, this revision
is between PCRE 8.31 (r895) and 8.32 (r1228). I refactored the code today, and
the new code is not affected by this bug anymore, but perhaps PCRE maintainers
might want to fix this issue in the previous PCRE revisions (including the
recent 8.34).

The effect can be shown by pcretest:

re> /[efij]/
data> e
0: e

re> /[efij]/S+
data> e
No match

I attach a temporary fix to this bug report, which can be used until a new PCRE
release with a fix appears. I am sorry for this issue.


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email