ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 345 by ph10, Mon Apr 28 15:10:02 2008 UTC revision 418 by ph10, Fri Apr 24 09:17:18 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.7 28-Apr-08  Version 8.00 ??-???-??
5    ----------------------
7    1.  The table for translating pcre_compile() error codes into POSIX error codes
8        was out-of-date, and there was no check on the pcre_compile() error code
9        being within the table. This could lead to an OK return being given in
10        error.
13    Version 7.9 11-Apr-09
14    ---------------------
16    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
17        (pcretest), all targets were linked against these libraries. This included
18        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
19        libraries. This caused unwanted dependencies to be created. This problem
20        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
21        pcretest is linked with readline.
23    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
24        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
25        moved outside it again, because FALSE and TRUE are already defined in AIX,
26        but BOOL is not.
28    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
29        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
31    4.  The pcregrep documentation said spaces were inserted as well as colons (or
32        hyphens) following file names and line numbers when outputting matching
33        lines. This is not true; no spaces are inserted. I have also clarified the
34        wording for the --colour (or --color) option.
36    5.  In pcregrep, when --colour was used with -o, the list of matching strings
37        was not coloured; this is different to GNU grep, so I have changed it to be
38        the same.
40    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
41        each matching line was coloured. Now it goes on to look for further matches
42        of any of the test patterns, which is the same behaviour as GNU grep.
44    7.  A pattern that could match an empty string could cause pcregrep to loop; it
45        doesn't make sense to accept an empty string match in pcregrep, so I have
46        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
47        seems to be how GNU grep behaves.
49    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
50        start or after a newline", because the conditional assertion was not being
51        correctly handled. The rule now is that both the assertion and what follows
52        in the first alternative must satisfy the test.
54    9.  If auto-callout was enabled in a pattern with a conditional group whose
55        condition was an assertion, PCRE could crash during matching, both with
56        pcre_exec() and pcre_dfa_exec().
58    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
59        used for matching.
61    11. Unicode property support in character classes was not working for
62        characters (bytes) greater than 127 when not in UTF-8 mode.
64    12. Added the -M command line option to pcretest.
66    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
68    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
70    16. Added comments and documentation about mis-use of no_arg in the C++
71        wrapper.
73    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
74        from Martin Jerabek that uses macro names for all relevant character and
75        string constants.
77    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
78        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
79        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
80        these, but not everybody uses configure.
82    19. A conditional group that had only one branch was not being correctly
83        recognized as an item that could match an empty string. This meant that an
84        enclosing group might also not be so recognized, causing infinite looping
85        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
86        with the subject "ab", where knowledge that the repeated group can match
87        nothing is needed in order to break the loop.
89    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
90        exec(), but without supplying a callout function, matching went wrong.
92    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
93        leak if the size of the offset vector was greater than 30. When the vector
94        is smaller, the saved offsets during recursion go onto a local stack
95        vector, but for larger vectors malloc() is used. It was failing to free
96        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
97        error, in fact).
99    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
100        heapframe that is used only when UTF-8 support is enabled. This caused no
101        problem, but was untidy.
103    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
104        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
105        included within another project.
107    24. Steven Van Ingelgem's patches to add more options to the CMake support,
108        slightly modified by me:
110          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
111              not building pcregrep.
113          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
114              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
116    25. Forward references, both numeric and by name, in patterns that made use of
117        duplicate group numbers, could behave incorrectly or give incorrect errors,
118        because when scanning forward to find the reference group, PCRE was not
119        taking into account the duplicate group numbers. A pattern such as
120        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
122    26. Changed a few more instances of "const unsigned char *" to USPTR, making
123        the feature of a custom pointer more persuasive (as requested by a user).
125    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
126        pcretest.c, inside #ifndefs, because it seems they are sometimes already
127        pre-defined.
129    28. Added support for (*UTF8) at the start of a pattern.
131    29. Arrange for flags added by the "release type" setting in CMake to be shown
132        in the configuration summary.
135    Version 7.8 05-Sep-08
136    ---------------------
138    1.  Replaced UCP searching code with optimized version as implemented for Ad
139        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
140        stage table and inline lookup instead of a function, giving speed ups of 2
141        to 5 times on some simple patterns that I tested. Permission was given to
142        distribute the MultiStage2.py script that generates the tables (it's not in
143        the tarball, but is in the Subversion repository).
145    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
146        scripts.
148    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
149        a group with a zero qualifier. The result of the study could be incorrect,
150        or the function might crash, depending on the pattern.
152    4.  Caseless matching was not working for non-ASCII characters in back
153        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
154        It now works when Unicode Property Support is available.
156    5.  In pcretest, an escape such as \x{de} in the data was always generating
157        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
158        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
159        truncation.
161    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
163    7.  Added two (int) casts to pcregrep when printing the difference of two
164        pointers, in case they are 64-bit values.
166    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
167        test 2 if it fails.
169    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
170        and a #define of that name to empty if it is not externally set. This is to
171        allow users of MSVC to set it if necessary.
173    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
174        the convenience functions in the pcre_get.c source file.
176    11. An option change at the start of a pattern that had top-level alternatives
177        could cause overwriting and/or a crash. This command provoked a crash in
178        some environments:
180          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
182        This potential security problem was recorded as CVE-2008-2371.
184    12. For a pattern where the match had to start at the beginning or immediately
185        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
186        pcre_dfa_exec() could read past the end of the passed subject if there was
187        no match. To help with detecting such bugs (e.g. with valgrind), I modified
188        pcretest so that it places the subject at the end of its malloc-ed buffer.
190    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
191        exec() might read past the end of the data buffer in UTF-8 mode.
193    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
194        the data contained the byte 0x85 as part of a UTF-8 character within its
195        first line. This applied both to normal and DFA matching.
197    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
198        /^[^d]*?$/8 failed to match "abc".
200    16. Added a missing copyright notice to pcrecpp_internal.h.
202    17. Make it more clear in the documentation that values returned from
203        pcre_exec() in ovector are byte offsets, not character counts.
205    18. Tidied a few places to stop certain compilers from issuing warnings.
207    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
208        supplied by Stefan Weber. I made a further small update for 7.8 because
209        there is a change of source arrangements: the pcre_searchfuncs.c module is
210        replaced by pcre_ucd.c.
213    Version 7.7 07-May-08
214  ---------------------  ---------------------
216  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
# Line 103  Version 7.7 28-Apr-08 Line 312  Version 7.7 28-Apr-08
312      requested, but also to allow for it to be overridden. This patch came from      requested, but also to allow for it to be overridden. This patch came from
313      Daniel Bergström.      Daniel Bergström.
315    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
316        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
317        any errors with the current Unicode tables. Thanks to Peter Kankowski for
318        spotting this.
321  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08
322  ---------------------  ---------------------

Removed from v.345  
changed lines
  Added in v.418

  ViewVC Help
Powered by ViewVC 1.1.5