@@ -2,8 +2,8 @@ Change Log for PCRE2
22--------------------
33
44
5- Version 10.31 13-January -2018
6- -----------------------------
5+ Version 10.31 12-February -2018
6+ ------------------------------
77
881. Fix typo (missing ]) in VMS code in pcre2test.c.
99
@@ -42,7 +42,7 @@ full path file names, which may be up to 2047 characters long.
424212. When an assertion contained (*ACCEPT) it caused all open capturing groups
4343to be closed (as for a non-assertion ACCEPT), which was wrong and could lead to
4444misbehaviour for subsequent references to groups that started outside the
45- recursion . ACCEPT in an assertion now closes only those groups that were
45+ assertion . ACCEPT in an assertion now closes only those groups that were
4646started within that assertion. Fixes oss-fuzz issues 3852 and 3891.
4747
484813. Multiline matching in pcre2grep was misbehaving if the pattern matched
@@ -129,18 +129,18 @@ call with zero length.
129129element. Their actual memory is obtained dynamically, giving an ovector of
130130appropriate length. However, they are defined in the structure as
131131ovector[NUMBER], where NUMBER is large so that array bound checkers don't
132- grumble. The value of NUMBER was 10000, but a fuzzer exceeded 5000 capturing
133- groups, making the ovector larger than this. The number has been increased to
134- 131072, which allows for the maximum number of captures (65535) plus the
132+ grumble. The value of NUMBER was 10000, but a fuzzer exceeded 5000 capturing
133+ groups, making the ovector larger than this. The number has been increased to
134+ 131072, which allows for the maximum number of captures (65535) plus the
135135overall match. This fixes oss-fuzz issue 5415.
136136
137- 31. Auto-possessification at the end of a capturing group was dependent on what
138- follows the group (e.g. /(a+)b/ would auto-possessify the a+) but this caused
139- incorrect behaviour when the group was called recursively from elsewhere in the
137+ 31. Auto-possessification at the end of a capturing group was dependent on what
138+ follows the group (e.g. /(a+)b/ would auto-possessify the a+) but this caused
139+ incorrect behaviour when the group was called recursively from elsewhere in the
140140pattern where something different might follow. This bug is an unforseen
141141consequence of change #1 for 10.30 - the implementation of backtracking into
142142recursions. Iterators at the ends of capturing groups are no longer considered
143- for auto-possessification if the pattern contains any recursions. Fixes
143+ for auto-possessification if the pattern contains any recursions. Fixes
144144Bugzilla #2232.
145145
146146
0 commit comments