ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 200 by ph10, Wed Aug 1 09:10:40 2007 UTC revision 507 by ph10, Wed Mar 10 16:08:01 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 05-Jul-07  Version 8.02 10-Mar-2010
5    ------------------------
7    1.  The Unicode data tables have been updated to Unicode 5.2.0.
9    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
10        configured.
12    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
13        original author of that file, following a query about its status.
15    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
16        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
18    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
19        quantifier applied to a forward-referencing subroutine call, could compile
20        incorrect code or give the error "internal error: previously-checked
21        referenced subpattern not found".
23    6.  Both MS Visual Studio and Symbian OS have problems with initializing
24        variables to point to external functions. For these systems, therefore,
25        pcre_malloc etc. are now initialized to local functions that call the
26        relevant global functions.
28    7.  There were two entries missing in the vectors called coptable and poptable
29        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
30        I've fixed the data, and added a kludgy way of testing at compile time that
31        the lengths are correct (equal to the number of opcodes).
33    8.  Following on from 7, I added a similar kludge to check the length of the
34        eint vector in pcreposix.c.
36    9.  Error texts for pcre_compile() are held as one long string to avoid too
37        much relocation at load time. To find a text, the string is searched,
38        counting zeros. There was no check for running off the end of the string,
39        which could happen if a new error number was added without updating the
40        string.
42    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
44    11. \K was not working if it appeared in an atomic group or in a group that
45        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
46        \K is "not well defined" if used in an assertion. PCRE now accepts it if
47        the assertion is positive, but not if it is negative.
49    12. Change 11 fortuitously reduced the size of the stack frame used in the
50        "match()" function of pcre_exec.c by one pointer. Forthcoming
51        implementation of support for (*MARK) will need an extra pointer on the
52        stack; I have reserved it now, so that the stack frame size does not
53        decrease.
55    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
56        item in branch that calls a recursion is a subroutine call - as in the
57        second branch in the above example - was incorrectly given the compile-
58        time error "recursive call could loop indefinitely" because pcre_compile()
59        was not correctly checking the subroutine for matching a non-empty string.
61    14. The checks for overrunning compiling workspace could trigger after an
62        overrun had occurred. This is a "should never occur" error, but it can be
63        triggered by pathological patterns such as hundreds of nested parentheses.
64        The checks now trigger 100 bytes before the end of the workspace.
66    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
69    Version 8.01 19-Jan-2010
70    ------------------------
72    1.  If a pattern contained a conditional subpattern with only one branch (in
73        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
74        computed the wrong minimum data length (which is of course zero for such
75        subpatterns). This could cause incorrect "no match" results.
77    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
78        the pattern is reset in the first branch, pcre_compile() failed with
79        "internal error: code overflow at offset...". This happened only when
80        the reset was to the original external option setting. (An optimization
81        abstracts leading options settings into an external setting, which was the
82        cause of this.)
84    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
85        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
86        assertion pattern did not match (meaning that the assertion was true), it
87        was incorrectly treated as false if the SKIP had been reached during the
88        matching. This also applied to assertions used as conditions.
90    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
91        assertion subpattern, including such a pattern used as a condition,
92        unpredictable results occurred, instead of the error return
95    5.  The C++ GlobalReplace function was not working like Perl for the special
96        situation when an empty string is matched. It now does the fancy magic
97        stuff that is necessary.
99    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
100        removed. (These were left over from very, very early versions of PCRE.)
102    7.  Some cosmetic changes to the code to make life easier when compiling it
103        as part of something else:
105        (a) Change DEBUG to PCRE_DEBUG.
107        (b) In pcre_compile(), rename the member of the "branch_chain" structure
108            called "current" as "current_branch", to prevent a collision with the
109            Linux macro when compiled as a kernel module.
111        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
112            prevent a collision with the Linux macro when compiled as a kernel
113            module.
115    8.  In pcre_compile() there are some checks for integer overflows that used to
116        cast potentially large values to (double). This has been changed to that
117        when building, a check for int64_t is made, and if it is found, it is used
118        instead, thus avoiding the use of floating point arithmetic. (There is no
119        other use of FP in PCRE.) If int64_t is not found, the fallback is to
120        double.
122    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
123        2005 (difference between two addresses compared to an unsigned value).
125    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
126        custom one, because of the following reported problem in Windows:
128          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
129              under Win32.
130          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
131              therefore missing the function definition.
132          - The compiler thus generates a "C" signature for the test function.
133          - The linker fails to find the "C" function.
134          - PCRE fails to configure if asked to do so against libbz2.
136    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
137        messages were output:
139          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
140          rerunning libtoolize, to keep the correct libtool macros in-tree.
141          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
143        I have done both of these things.
145    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
146        most of the time, it *can* run out if it is given a pattern that contains a
147        runaway infinite recursion. I updated the discussion in the pcrestack man
148        page.
150    13. Now that we have gone to the x.xx style of version numbers, the minor
151        version may start with zero. Using 08 or 09 is a bad idea because users
152        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
153        interpreted as invalid octal numbers. I've updated the previous comment in
154        configure.ac, and also added a check that gives an error if 08 or 09 are
155        used.
157    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
158        causing partial matching to fail when the end of the subject matched \W
159        in a UTF-8 pattern where \W was quantified with a minimum of 3.
161    15. There were some discrepancies between the declarations in pcre_internal.h
162        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
163        their definitions. The declarations used "const uschar *" and the
164        definitions used USPTR. Even though USPTR is normally defined as "const
165        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
166        reported that: "This difference in casting confuses some C++ compilers, for
167        example, SunCC recognizes above declarations as different functions and
168        generates broken code for hbpcre." I have changed the declarations to use
169        USPTR.
171    16. GNU libtool is named differently on some systems. The autogen.sh script now
172        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
173        (FreeBSD).
175    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
176        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
177        comment: "Figure out how to create a longlong from a string: strtoll and
178        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
179        instance, but it only takes 2 args instead of 3!"
181    18. A subtle bug concerned with back references has been fixed by a change of
182        specification, with a corresponding code fix. A pattern such as
183        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
184        refers, was giving matches when it shouldn't. For example, xa=xaaa would
185        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
186        same bug. Such groups have to be quantified to be useful, or contained
187        inside another quantified group. (If there's no repetition, the reference
188        can never match.) The problem arises because, having left the group and
189        moved on to the rest of the pattern, a later failure that backtracks into
190        the group uses the captured value from the final iteration of the group
191        rather than the correct earlier one. I have fixed this in PCRE by forcing
192        any group that contains a reference to itself to be an atomic group; that
193        is, there cannot be any backtracking into it once it has completed. This is
194        similar to recursive and subroutine calls.
197    Version 8.00 19-Oct-09
198    ----------------------
200    1.  The table for translating pcre_compile() error codes into POSIX error codes
201        was out-of-date, and there was no check on the pcre_compile() error code
202        being within the table. This could lead to an OK return being given in
203        error.
205    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
206        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
207        in a Windows environment.
209    3.  The pcregrep --count option prints the count for each file even when it is
210        zero, as does GNU grep. However, pcregrep was also printing all files when
211        --files-with-matches was added. Now, when both options are given, it prints
212        counts only for those files that have at least one match. (GNU grep just
213        prints the file name in this circumstance, but including the count seems
214        more useful - otherwise, why use --count?) Also ensured that the
215        combination -clh just lists non-zero counts, with no names.
217    4.  The long form of the pcregrep -F option was incorrectly implemented as
218        --fixed_strings instead of --fixed-strings. This is an incompatible change,
219        but it seems right to fix it, and I didn't think it was worth preserving
220        the old behaviour.
222    5.  The command line items --regex=pattern and --regexp=pattern were not
223        recognized by pcregrep, which required --regex pattern or --regexp pattern
224        (with a space rather than an '='). The man page documented the '=' forms,
225        which are compatible with GNU grep; these now work.
227    6.  No libpcreposix.pc file was created for pkg-config; there was just
228        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
230    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
231        when UCP support is not needed, by modifying the Python script that
232        generates it from Unicode data files. This should not matter if the module
233        is correctly used as a library, but I received one complaint about 50K of
234        unwanted data. My guess is that the person linked everything into his
235        program rather than using a library. Anyway, it does no harm.
237    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
238        was a minimum greater than 1 for a wide character in a possessive
239        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
240        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
241        character. Chaos in the form of incorrect output or a compiling loop could
242        result.
244    9.  The restrictions on what a pattern can contain when partial matching is
245        requested for pcre_exec() have been removed. All patterns can now be
246        partially matched by this function. In addition, if there are at least two
247        slots in the offset vector, the offset of the earliest inspected character
248        for the match and the offset of the end of the subject are set in them when
249        PCRE_ERROR_PARTIAL is returned.
251    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
252        synonymous with PCRE_PARTIAL, for backwards compatibility, and
253        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
254        and may be more useful for multi-segment matching.
256    11. Partial matching with pcre_exec() is now more intuitive. A partial match
257        used to be given if ever the end of the subject was reached; now it is
258        given only if matching could not proceed because another character was
259        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
260        string "Z", which now yields "no match" instead of "partial match". In the
261        case of pcre_dfa_exec(), "no match" is given if every matching path for the
262        final character ended with (*FAIL).
264    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
265        if the pattern had a "must contain" character that was already found in the
266        earlier partial match, unless partial matching was again requested. For
267        example, with the pattern /dog.(body)?/, the "must contain" character is
268        "g". If the first part-match was for the string "dog", restarting with
269        "sbody" failed. This bug has been fixed.
271    13. The string returned by pcre_dfa_exec() after a partial match has been
272        changed so that it starts at the first inspected character rather than the
273        first character of the match. This makes a difference only if the pattern
274        starts with a lookbehind assertion or \b or \B (\K is not supported by
275        pcre_dfa_exec()). It's an incompatible change, but it makes the two
276        matching functions compatible, and I think it's the right thing to do.
278    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
279        so that the demonstration program is easily available in environments where
280        PCRE has not been installed from source.
282    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
283        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
284        library.
286    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
287        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
288        is not the first non-POSIX option to be added. Clearly some people find
289        these options useful.
291    17. If a caller to the POSIX matching function regexec() passes a non-zero
292        value for nmatch with a NULL value for pmatch, the value of
293        nmatch is forced to zero.
295    18. RunGrepTest did not have a test for the availability of the -u option of
296        the diff command, as RunTest does. It now checks in the same way as
297        RunTest, and also checks for the -b option.
299    19. If an odd number of negated classes containing just a single character
300        interposed, within parentheses, between a forward reference to a named
301        subpattern and the definition of the subpattern, compilation crashed with
302        an internal error, complaining that it could not find the referenced
303        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
304        [The bug was that it was starting one character too far in when skipping
305        over the character class, thus treating the ] as data rather than
306        terminating the class. This meant it could skip too much.]
308    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
309        /g option in pcretest when the pattern contains \K, which makes it possible
310        to have an empty string match not at the start, even when the pattern is
311        anchored. Updated pcretest and pcredemo to use this option.
313    21. If the maximum number of capturing subpatterns in a recursion was greater
314        than the maximum at the outer level, the higher number was returned, but
315        with unset values at the outer level. The correct (outer level) value is
316        now given.
318    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
319        PCRE did not set those parentheses (unlike Perl). I have now found a way to
320        make it do so. The string so far is captured, making this feature
321        compatible with Perl.
323    23. The tests have been re-organized, adding tests 11 and 12, to make it
324        possible to check the Perl 5.10 features against Perl 5.10.
326    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
327        pattern matches a fixed length string. PCRE did not allow this; now it
328        does. Neither allows recursion.
330    25. I finally figured out how to implement a request to provide the minimum
331        length of subject string that was needed in order to match a given pattern.
332        (It was back references and recursion that I had previously got hung up
333        on.) This code has now been added to pcre_study(); it finds a lower bound
334        to the length of subject needed. It is not necessarily the greatest lower
335        bound, but using it to avoid searching strings that are too short does give
336        some useful speed-ups. The value is available to calling programs via
337        pcre_fullinfo().
339    26. While implementing 25, I discovered to my embarrassment that pcretest had
340        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
341        study optimizations had never been tested with that matching function.
342        Oops. What is worse, even when it was passed study data, there was a bug in
343        pcre_dfa_exec() that meant it never actually used it. Double oops. There
344        were also very few tests of studied patterns with pcre_dfa_exec().
346    27. If (?| is used to create subpatterns with duplicate numbers, they are now
347        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
348        on the other side of the coin, they are no longer allowed to have different
349        names, because these cannot be distinguished in PCRE, and this has caused
350        confusion. (This is a difference from Perl.)
352    28. When duplicate subpattern names are present (necessarily with different
353        numbers, as required by 27 above), and a test is made by name in a
354        conditional pattern, either for a subpattern having been matched, or for
355        recursion in such a pattern, all the associated numbered subpatterns are
356        tested, and the overall condition is true if the condition is true for any
357        one of them. This is the way Perl works, and is also more like the way
358        testing by number works.
361    Version 7.9 11-Apr-09
362    ---------------------
364    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
365        (pcretest), all targets were linked against these libraries. This included
366        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
367        libraries. This caused unwanted dependencies to be created. This problem
368        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
369        pcretest is linked with readline.
371    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
372        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
373        moved outside it again, because FALSE and TRUE are already defined in AIX,
374        but BOOL is not.
376    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
377        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
379    4.  The pcregrep documentation said spaces were inserted as well as colons (or
380        hyphens) following file names and line numbers when outputting matching
381        lines. This is not true; no spaces are inserted. I have also clarified the
382        wording for the --colour (or --color) option.
384    5.  In pcregrep, when --colour was used with -o, the list of matching strings
385        was not coloured; this is different to GNU grep, so I have changed it to be
386        the same.
388    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
389        each matching line was coloured. Now it goes on to look for further matches
390        of any of the test patterns, which is the same behaviour as GNU grep.
392    7.  A pattern that could match an empty string could cause pcregrep to loop; it
393        doesn't make sense to accept an empty string match in pcregrep, so I have
394        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
395        seems to be how GNU grep behaves.
397    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
398        start or after a newline", because the conditional assertion was not being
399        correctly handled. The rule now is that both the assertion and what follows
400        in the first alternative must satisfy the test.
402    9.  If auto-callout was enabled in a pattern with a conditional group whose
403        condition was an assertion, PCRE could crash during matching, both with
404        pcre_exec() and pcre_dfa_exec().
406    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
407        used for matching.
409    11. Unicode property support in character classes was not working for
410        characters (bytes) greater than 127 when not in UTF-8 mode.
412    12. Added the -M command line option to pcretest.
414    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
416    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
418    16. Added comments and documentation about mis-use of no_arg in the C++
419        wrapper.
421    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
422        from Martin Jerabek that uses macro names for all relevant character and
423        string constants.
425    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
426        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
427        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
428        these, but not everybody uses configure.
430    19. A conditional group that had only one branch was not being correctly
431        recognized as an item that could match an empty string. This meant that an
432        enclosing group might also not be so recognized, causing infinite looping
433        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
434        with the subject "ab", where knowledge that the repeated group can match
435        nothing is needed in order to break the loop.
437    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
438        exec(), but without supplying a callout function, matching went wrong.
440    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
441        leak if the size of the offset vector was greater than 30. When the vector
442        is smaller, the saved offsets during recursion go onto a local stack
443        vector, but for larger vectors malloc() is used. It was failing to free
444        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
445        error, in fact).
447    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
448        heapframe that is used only when UTF-8 support is enabled. This caused no
449        problem, but was untidy.
451    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
452        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
453        included within another project.
455    24. Steven Van Ingelgem's patches to add more options to the CMake support,
456        slightly modified by me:
458          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
459              not building pcregrep.
461          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
462              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
464    25. Forward references, both numeric and by name, in patterns that made use of
465        duplicate group numbers, could behave incorrectly or give incorrect errors,
466        because when scanning forward to find the reference group, PCRE was not
467        taking into account the duplicate group numbers. A pattern such as
468        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
470    26. Changed a few more instances of "const unsigned char *" to USPTR, making
471        the feature of a custom pointer more persuasive (as requested by a user).
473    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
474        pcretest.c, inside #ifndefs, because it seems they are sometimes already
475        pre-defined.
477    28. Added support for (*UTF8) at the start of a pattern.
479    29. Arrange for flags added by the "release type" setting in CMake to be shown
480        in the configuration summary.
483    Version 7.8 05-Sep-08
484    ---------------------
486    1.  Replaced UCP searching code with optimized version as implemented for Ad
487        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
488        stage table and inline lookup instead of a function, giving speed ups of 2
489        to 5 times on some simple patterns that I tested. Permission was given to
490        distribute the MultiStage2.py script that generates the tables (it's not in
491        the tarball, but is in the Subversion repository).
493    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
494        scripts.
496    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
497        a group with a zero qualifier. The result of the study could be incorrect,
498        or the function might crash, depending on the pattern.
500    4.  Caseless matching was not working for non-ASCII characters in back
501        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
502        It now works when Unicode Property Support is available.
504    5.  In pcretest, an escape such as \x{de} in the data was always generating
505        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
506        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
507        truncation.
509    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
511    7.  Added two (int) casts to pcregrep when printing the difference of two
512        pointers, in case they are 64-bit values.
514    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
515        test 2 if it fails.
517    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
518        and a #define of that name to empty if it is not externally set. This is to
519        allow users of MSVC to set it if necessary.
521    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
522        the convenience functions in the pcre_get.c source file.
524    11. An option change at the start of a pattern that had top-level alternatives
525        could cause overwriting and/or a crash. This command provoked a crash in
526        some environments:
528          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
530        This potential security problem was recorded as CVE-2008-2371.
532    12. For a pattern where the match had to start at the beginning or immediately
533        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
534        pcre_dfa_exec() could read past the end of the passed subject if there was
535        no match. To help with detecting such bugs (e.g. with valgrind), I modified
536        pcretest so that it places the subject at the end of its malloc-ed buffer.
538    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
539        exec() might read past the end of the data buffer in UTF-8 mode.
541    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
542        the data contained the byte 0x85 as part of a UTF-8 character within its
543        first line. This applied both to normal and DFA matching.
545    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
546        /^[^d]*?$/8 failed to match "abc".
548    16. Added a missing copyright notice to pcrecpp_internal.h.
550    17. Make it more clear in the documentation that values returned from
551        pcre_exec() in ovector are byte offsets, not character counts.
553    18. Tidied a few places to stop certain compilers from issuing warnings.
555    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
556        supplied by Stefan Weber. I made a further small update for 7.8 because
557        there is a change of source arrangements: the pcre_searchfuncs.c module is
558        replaced by pcre_ucd.c.
561    Version 7.7 07-May-08
562    ---------------------
564    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
565        a string to a long long, pretend we don't even have a long long." This is
566        done by checking for the strtoq, strtoll, and _strtoi64 functions.
568    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
569        pre-7.6 versions, which defined a global no_arg variable instead of putting
570        it in the RE class. (See also #8 below.)
572    3.  Remove a line of dead code, identified by coverity and reported by Nuno
573        Lopes.
575    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
577        (1) The include/exclude patterns were being applied to the whole pathnames
578            of files, instead of just to the final components.
580        (2) If there was more than one level of directory, the subdirectories were
581            skipped unless they satisfied the include/exclude conditions. This is
582            inconsistent with GNU grep (and could even be seen as contrary to the
583            pcregrep specification - which I improved to make it absolutely clear).
584            The action now is always to scan all levels of directory, and just
585            apply the include/exclude patterns to regular files.
587    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
588        --exclude_dir in the tests to avoid scanning .svn directories.
590    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
591        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
592        doesn't support NULs in patterns.
594    7.  Added some missing "const"s to declarations of static tables in
595        pcre_compile.c and pcre_dfa_exec.c.
597    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
598        caused by fix #2  above. (Subsequently also a second patch to fix the
599        first patch. And a third patch - this was a messy problem.)
601    9.  Applied Craig's patch to remove the use of push_back().
603    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
604        matching function regexec().
606    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
607        which, however, unlike Perl's \g{...}, are subroutine calls, not back
608        references. PCRE supports relative numbers with this syntax (I don't think
609        Oniguruma does).
611    12. Previously, a group with a zero repeat such as (...){0} was completely
612        omitted from the compiled regex. However, this means that if the group
613        was called as a subroutine from elsewhere in the pattern, things went wrong
614        (an internal error was given). Such groups are now left in the compiled
615        pattern, with a new opcode that causes them to be skipped at execution
616        time.
618    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
619        to the way PCRE behaves:
621        (a) A lone ] character is dis-allowed (Perl treats it as data).
623        (b) A back reference to an unmatched subpattern matches an empty string
624            (Perl fails the current match path).
626        (c) A data ] in a character class must be notated as \] because if the
627            first data character in a class is ], it defines an empty class. (In
628            Perl it is not possible to have an empty class.) The empty class []
629            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
630            The negative empty class [^] matches any one character, independently
631            of the DOTALL setting.
633    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
634        non-existent subpattern following a character class starting with ']' and
635        containing () gave an internal compiling error instead of "reference to
636        non-existent subpattern". Fortunately, when the pattern did exist, the
637        compiled code was correct. (When scanning forwards to check for the
638        existencd of the subpattern, it was treating the data ']' as terminating
639        the class, so got the count wrong. When actually compiling, the reference
640        was subsequently set up correctly.)
642    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
643        it was being rejected as not supported by pcre_dfa_exec(), even though
644        other assertions are supported. I have made pcre_dfa_exec() support
645        (*FAIL).
647    16. The implementation of 13c above involved the invention of a new opcode,
648        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
649        cannot be changed at match time, I realized I could make a small
650        improvement to matching performance by compiling OP_ALLANY instead of
651        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
652        on the OP_ANY path.
654    17. Compiling pcretest on Windows with readline support failed without the
655        following two fixes: (1) Make the unistd.h include conditional on
656        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
658    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
659        ncurses library to be included for pcretest when ReadLine support is
660        requested, but also to allow for it to be overridden. This patch came from
661        Daniel Bergström.
663    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
664        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
665        any errors with the current Unicode tables. Thanks to Peter Kankowski for
666        spotting this.
669    Version 7.6 28-Jan-08
670    ---------------------
672    1.  A character class containing a very large number of characters with
673        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
674        overflow.
676    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
677        HAVE_LONG_LONG is not defined.
679    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
680        bring them up to date and include new features. This patch includes:
682        - Fixed PH's badly added libz and libbz2 support.
683        - Fixed a problem with static linking.
684        - Added pcredemo. [But later removed - see 7 below.]
685        - Fixed dftables problem and added an option.
686        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
687            HAVE_LONG_LONG.
688        - Added readline support for pcretest.
689        - Added an listing of the option settings after cmake has run.
691    4.  A user submitted a patch to Makefile that makes it easy to create
692        "pcre.dll" under mingw when using Configure/Make. I added stuff to
693        Makefile.am that cause it to include this special target, without
694        affecting anything else. Note that the same mingw target plus all
695        the other distribution libraries and programs are now supported
696        when configuring with CMake (see 6 below) instead of with
697        Configure/Make.
699    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
700        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
701        exported in the Windows port". It has not yet been confirmed that the patch
702        solves the problem, but it does no harm.
704    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
705        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
706        with CMake, and also correct the comment about stack recursion.
708    7.  Remove the automatic building of pcredemo from the ./configure system and
709        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
710        of a program that users should build themselves after PCRE is installed, so
711        building it automatically is not really right. What is more, it gave
712        trouble in some build environments.
714    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
717    Version 7.5 10-Jan-08
718    ---------------------
720    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
721        values in parens when parsing an RE using the C++ wrapper."
723    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
724        Characters greater than 255 were excluded from the class instead of being
725        included.
727    3.  The same bug as (2) above applied to negated POSIX classes such as
728        [:^space:].
730    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
731        defined or documented. It seems to have been a typo for PCRE_STATIC, so
732        I have changed it.
734    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
735        first named subpattern) and a construct such as (?&a) would reference the
736        first named subpattern whose name started with "a" (in other words, the
737        length check was missing). Both these problems are fixed. "Subpattern name
738        expected" is now given for (?&) (a zero-length name), and this patch also
739        makes it give the same error for \k'' (previously it complained that that
740        was a reference to a non-existent subpattern).
742    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
743        this is right because (?- can be followed by option settings as well as by
744        digits. I have, however, made the messages clearer.
746    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
747        than the number used in the conditional) now cause a compile-time error.
748        This is actually not compatible with Perl, which accepts such patterns, but
749        treats the conditional as always being FALSE (as PCRE used to), but it
750        seems to me that giving a diagnostic is better.
752    8.  Change "alphameric" to the more common word "alphanumeric" in comments
753        and messages.
755    9.  Fix two occurrences of "backslash" in comments that should have been
756        "backspace".
758    10. Remove two redundant lines of code that can never be obeyed (their function
759        was moved elsewhere).
761    11. The program that makes PCRE's Unicode character property table had a bug
762        which caused it to generate incorrect table entries for sequences of
763        characters that have the same character type, but are in different scripts.
764        It amalgamated them into a single range, with the script of the first of
765        them. In other words, some characters were in the wrong script. There were
766        thirteen such cases, affecting characters in the following ranges:
768          U+002b0 - U+002c1
769          U+0060c - U+0060d
770          U+0061e - U+00612
771          U+0064b - U+0065e
772          U+0074d - U+0076d
773          U+01800 - U+01805
774          U+01d00 - U+01d77
775          U+01d9b - U+01dbf
776          U+0200b - U+0200f
777          U+030fc - U+030fe
778          U+03260 - U+0327f
779          U+0fb46 - U+0fbb1
780          U+10450 - U+1049d
782    12. The -o option (show only the matching part of a line) for pcregrep was not
783        compatible with GNU grep in that, if there was more than one match in a
784        line, it showed only the first of them. It now behaves in the same way as
785        GNU grep.
787    13. If the -o and -v options were combined for pcregrep, it printed a blank
788        line for every non-matching line. GNU grep prints nothing, and pcregrep now
789        does the same. The return code can be used to tell if there were any
790        non-matching lines.
792    14. Added --file-offsets and --line-offsets to pcregrep.
794    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
795        infinitely looping recursion. The bug was that positive lookaheads were not
796        being skipped when checking for a possible empty match (negative lookaheads
797        and both kinds of lookbehind were skipped).
799    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
800        inclusion of <windows.h> to before rather than after the definition of
801        INVALID_FILE_ATTRIBUTES (patch from David Byron).
803    17. Specifying a possessive quantifier with a specific limit for a Unicode
804        character property caused pcre_compile() to compile bad code, which led at
805        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
806        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
807        caused the error; without that there was no problem.
809    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
811    19. Added --enable-pcretest-libreadline.
813    20. In pcrecpp.cc, the variable 'count' was incremented twice in
814        RE::GlobalReplace(). As a result, the number of replacements returned was
815        double what it should be. I removed one of the increments, but Craig sent a
816        later patch that removed the other one (the right fix) and added unit tests
817        that check the return values (which was not done before).
819    21. Several CMake things:
821        (1) Arranged that, when cmake is used on Unix, the libraries end up with
822            the names libpcre and libpcreposix, not just pcre and pcreposix.
824        (2) The above change means that pcretest and pcregrep are now correctly
825            linked with the newly-built libraries, not previously installed ones.
829    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
830        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
831        UTF-8 newline character). The key issue is that the pattern starts .*;
832        this means that the match must be either at the beginning, or after a
833        newline. The bug was in the code for advancing after a failed match and
834        checking that the new position followed a newline. It was not taking
835        account of UTF-8 characters correctly.
837    23. PCRE was behaving differently from Perl in the way it recognized POSIX
838        character classes. PCRE was not treating the sequence [:...:] as a
839        character class unless the ... were all letters. Perl, however, seems to
840        allow any characters between [: and :], though of course it rejects as
841        unknown any "names" that contain non-letters, because all the known class
842        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
843        for example, whereas PCRE did not - it did not recognize a POSIX character
844        class. This seemed a bit dangerous, so the code has been changed to be
845        closer to Perl. The behaviour is not identical to Perl, because PCRE will
846        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
847        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
848        Perl does, and where it didn't before.
850    24. Rewrite so as to remove the single use of %n from pcregrep because in some
851        Windows environments %n is disabled by default.
854    Version 7.4 21-Sep-07
855    ---------------------
857    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
858        means that a class such as [\s] counted as "explicit reference to CR or
859        LF". That isn't really right - the whole point of the change was to try to
860        help when there was an actual mention of one of the two characters. So now
861        the change happens only if \r or \n (or a literal CR or LF) character is
862        encountered.
864    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
865        of both had grown to the point where there were only 3 bits left.
866        Fortunately, there was spare space in the data structure, and so I have
867        moved the internal flags into a new 16-bit field to free up more option
868        bits.
870    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
871        but did not set the internal JCHANGED flag - either of these is enough to
872        control the way the "get" function works - but the PCRE_INFO_JCHANGED
873        facility is supposed to tell if (?J) was ever used, so now (?J) at the
874        start sets both bits.
876    4.  Added options (at build time, compile time, exec time) to change \R from
877        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
879    5.  doc/pcresyntax.html was missing from the distribution.
881    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
882        compatibility, even though it is no longer used.
884    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
885        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
886        windows.h file is present (where different names are used). [This was
887        reversed later after testing - see 16 below.]
889    8.  Changed all #include <config.h> to #include "config.h". There were also
890        some further <pcre.h> cases that I changed to "pcre.h".
892    9.  When pcregrep was used with the --colour option, it missed the line ending
893        sequence off the lines that it output.
895    10. It was pointed out to me that arrays of string pointers cause lots of
896        relocations when a shared library is dynamically loaded. A technique of
897        using a single long string with a table of offsets can drastically reduce
898        these. I have refactored PCRE in four places to do this. The result is
899        dramatic:
901          Originally:                          290
902          After changing UCP table:            187
903          After changing error message table:   43
904          After changing table of "verbs"       36
905          After changing table of Posix names   22
907        Thanks to the folks working on Gregex for glib for this insight.
909    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
910        unicode-properties was also set.
912    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
914    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
915        checked only for CRLF.
917    14. Added casts to pcretest.c to avoid compiler warnings.
919    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
921    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
922        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
923        entirely. This removes changes made in 7 above.
925    17. The CMake files have been updated, and there is now more information about
926        building with CMake in the NON-UNIX-USE document.
929    Version 7.3 28-Aug-07
930  ---------------------  ---------------------
932   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 29  Version 7.3 05-Jul-07 Line 954  Version 7.3 05-Jul-07
954   4. Debugging: adjusted the names of opcodes for different kinds of parentheses   4. Debugging: adjusted the names of opcodes for different kinds of parentheses
955      in debug output.      in debug output.
957   5. Arrange to use "%I64d" instead of "%lld" for long printing in the pcrecpp   5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
958      unittest when running under MinGW.      long printing in the pcrecpp unittest when running under MinGW.
960   6. ESC_K was left out of the EBCDIC table.   6. ESC_K was left out of the EBCDIC table.
# Line 53  Version 7.3 05-Jul-07 Line 978  Version 7.3 05-Jul-07
978      pcreposix and pcrecpp parts of the library. These were overlooked when this      pcreposix and pcrecpp parts of the library. These were overlooked when this
979      problem was solved for the main library.      problem was solved for the main library.
981     9. There were some crude static tests to avoid integer overflow when computing
982        the size of patterns that contain repeated groups with explicit upper
983        limits. As the maximum quantifier is 65535, the maximum group length was
984        set at 30,000 so that the product of these two numbers did not overflow a
985        32-bit integer. However, it turns out that people want to use groups that
986        are longer than 30,000 bytes (though not repeat them that many times).
987        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
988        made it possible to implement the integer overflow checks in a much more
989        dynamic way, which I have now done. The artificial limitation on group
990        length has been removed - we now have only the limit on the total length of
991        the compiled pattern, which depends on the LINK_SIZE setting.
993    10. Fixed a bug in the documentation for get/copy named substring when
994        duplicate names are permitted. If none of the named substrings are set, the
995        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
996        empty string.
998    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
999        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
1000        because the ] is interpreted as the first data character and the
1001        terminating ] is not found. PCRE has been made compatible with Perl in this
1002        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
1003        cause memory overwriting.
1005    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
1006        string has been matched (to stop an infinite loop). It was not recognizing
1007        a conditional subpattern that could match an empty string if that
1008        subpattern was within another subpattern. For example, it looped when
1009        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
1010        condition was not nested. This bug has been fixed.
1012    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
1013        past the start of the subject in the presence of bytes with the top bit
1014        set, for example "\x8aBCD".
1016    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
1017        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
1019    14. Optimized (?!) to (*FAIL).
1021    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1022        This restricts code points to be within the range 0 to 0x10FFFF, excluding
1023        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1024        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1025        does: it's just the validity check that is more restrictive.
1027    16. Inserted checks for integer overflows during escape sequence (backslash)
1028        processing, and also fixed erroneous offset values for syntax errors during
1029        backslash processing.
1031    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1032        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1034    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1035        caused an overrun.
1037    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1038        something other than just ASCII characters) inside a group that had an
1039        unlimited repeat caused a loop at compile time (while checking to see
1040        whether the group could match an empty string).
1042    20. Debugging a pattern containing \p or \P could cause a crash. For example,
1043        [\P{Any}] did so. (Error in the code for printing property names.)
1045    21. An orphan \E inside a character class could cause a crash.
1047    22. A repeated capturing bracket such as (A)? could cause a wild memory
1048        reference during compilation.
1050    23. There are several functions in pcre_compile() that scan along a compiled
1051        expression for various reasons (e.g. to see if it's fixed length for look
1052        behind). There were bugs in these functions when a repeated \p or \P was
1053        present in the pattern. These operators have additional parameters compared
1054        with \d, etc, and these were not being taken into account when moving along
1055        the compiled data. Specifically:
1057        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1058            length.
1060        (b) An item such as \pL+ within a repeated group could cause crashes or
1061            loops.
1063        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1064            "reference to non-existent subpattern" error.
1066        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1068    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1069        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1071    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1073    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1074        character were causing crashes (broken optimization).
1076    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1077        \p or \P) caused a compile-time loop.
1079    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1080        break. For example, the unstudied pattern [\r\n]A does not match the string
1081        "\r\nA" because change 7.0/46 below moves the current point on by two
1082        characters after failing to match at the start. However, the pattern \nA
1083        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1084        the same is true. There doesn't seem any very clean way out of this, but
1085        what I have chosen to do makes the common cases work: PCRE now takes note
1086        of whether there can be an explicit match for \r or \n anywhere in the
1087        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1088        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1089        pattern has explicit CR or LF references.
1091    29. Added (*CR) etc for changing newline setting at start of pattern.
1094  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
1095  ---------------------  ---------------------

Removed from v.200  
changed lines
  Added in v.507

  ViewVC Help
Powered by ViewVC 1.1.5