/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1465 by ph10, Fri Mar 14 15:58:19 2014 UTC revision 1515 by ph10, Tue Feb 3 17:08:54 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.35-RC1 14-March-2014  Version 8.37 xx-xxx-201x
5    ------------------------
6    
7    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
8        for those parentheses to be closed with whatever has been captured so far.
9        However, it was failing to mark any other groups between the hightest
10        capture so far and the currrent group as "unset". Thus, the ovector for
11        those groups contained whatever was previously there. An example is the
12        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
13    
14    2.  If an assertion condition was quantified with a minimum of zero (an odd
15        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
16    
17    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
18        unrecognized modifier, a crash could occur.
19    
20    4.  An attempt to do global matching in pcretest with a zero-length ovector
21        caused a crash.
22    
23    
24    
25    Version 8.36 26-September-2014
26  ------------------------------  ------------------------------
27    
28    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
29        -Wmissing-field-initializers and -Wunused-parameter.
30    
31    2.  The tests for quantifiers being too big (greater than 65535) were being
32        applied after reading the number, and stupidly assuming that integer
33        overflow would give a negative number. The tests are now applied as the
34        numbers are read.
35    
36    3.  Tidy code in pcre_exec.c where two branches that used to be different are
37        now the same.
38    
39    4.  The JIT compiler did not generate match limit checks for certain
40        bracketed expressions with quantifiers. This may lead to exponential
41        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
42        issue should be resolved now.
43    
44    5.  Fixed an issue, which occures when nested alternatives are optimized
45        with table jumps.
46    
47    6.  Inserted two casts and changed some ints to size_t in the light of some
48        reported 64-bit compiler warnings (Bugzilla 1477).
49    
50    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
51        an empty string, which sometimes were behaving incorrectly in the
52        interpreter (though correctly in the JIT matcher). This pcretest input is
53        an example:
54    
55          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
56          NON QUOTED "QUOT""ED" AFTER "NOT MATCHED
57    
58        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
59        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
60        for an empty string was breaking the inner loop and carrying on at a lower
61        level, when possessive repeated groups should always return to a higher
62        level as they have no backtrack points in them. The empty string test now
63        occurs at the outer level.
64    
65    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
66        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
67    
68    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
69        doesn't).
70    
71    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
72        to hold a pattern to be incorrectly computed (too small) when there were
73        named back references to duplicated names. This could cause "internal
74        error: code overflow" or "double free or corruption" or other memory
75        handling errors.
76    
77    11. When named subpatterns had the same prefixes, back references could be
78        confused. For example, in this pattern:
79    
80          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
81    
82        the reference to 'Name' was incorrectly treated as a reference to a
83        duplicate name.
84    
85    12. A pattern such as /^s?c/mi8 where the optional character has more than
86        one "other case" was incorrectly compiled such that it would only try to
87        match starting at "c".
88    
89    13. When a pattern starting with \s was studied, VT was not included in the
90        list of possible starting characters; this should have been part of the
91        8.34/18 patch.
92    
93    14. If a character class started [\Qx]... where x is any character, the class
94        was incorrectly terminated at the ].
95    
96    15. If a pattern that started with a caseless match for a character with more
97        than one "other case" was studied, PCRE did not set up the starting code
98        unit bit map for the list of possible characters. Now it does. This is an
99        optimization improvement, not a bug fix.
100    
101    16. The Unicode data tables have been updated to Unicode 7.0.0.
102    
103    17. Fixed a number of memory leaks in pcregrep.
104    
105    18. Avoid a compiler warning (from some compilers) for a function call with
106        a cast that removes "const" from an lvalue by using an intermediate
107        variable (to which the compiler does not object).
108    
109    19. Incorrect code was compiled if a group that contained an internal recursive
110        back reference was optional (had quantifier with a minimum of zero). This
111        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
112        caused segmentation faults because of stack overflows at compile time.
113    
114    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
115        group that is quantified with an indefinite repeat, caused a compile-time
116        loop which used up all the system stack and provoked a segmentation fault.
117        This was not the same bug as 19 above.
118    
119    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
120        Patch by Mike Frysinger.
121    
122    
123    Version 8.35 04-April-2014
124    --------------------------
125    
126  1.  A new flag is set, when property checks are present in an XCLASS.  1.  A new flag is set, when property checks are present in an XCLASS.
127      When this flag is not set, PCRE can perform certain optimizations      When this flag is not set, PCRE can perform certain optimizations
128      such as studying these XCLASS-es.      such as studying these XCLASS-es.
# Line 27  Version 8.35-RC1 14-March-2014 Line 146  Version 8.35-RC1 14-March-2014
146    
147  6.  Improve character range checks in JIT. Characters are read by an inprecise  6.  Improve character range checks in JIT. Characters are read by an inprecise
148      function now, which returns with an unknown value if the character code is      function now, which returns with an unknown value if the character code is
149      above a certain treshold (e.g: 256). The only limitation is that the value      above a certain threshold (e.g: 256). The only limitation is that the value
150      must be bigger than the treshold as well. This function is useful, when      must be bigger than the threshold as well. This function is useful when
151      the characters above the treshold are handled in the same way.      the characters above the threshold are handled in the same way.
152    
153  7.  The macros whose names start with RAWUCHAR are placeholders for a future  7.  The macros whose names start with RAWUCHAR are placeholders for a future
154      mode in which only the bottom 21 bits of 32-bit data items are used. To      mode in which only the bottom 21 bits of 32-bit data items are used. To
# Line 116  Version 8.35-RC1 14-March-2014 Line 235  Version 8.35-RC1 14-March-2014
235  24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT  24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
236      compiler.      compiler.
237    
238    25. Change all the temporary files used in RunGrepTest to be different to those
239        used by RunTest so that the tests can be run simultaneously, for example by
240        "make -j check".
241    
242    
243  Version 8.34 15-December-2013  Version 8.34 15-December-2013
244  -----------------------------  -----------------------------

Legend:
Removed from v.1465  
changed lines
  Added in v.1515

  ViewVC Help
Powered by ViewVC 1.1.5