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

Diff of /code/trunk/ChangeLog

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

revision 295 by ph10, Mon Dec 31 17:00:24 2007 UTC revision 500 by ph10, Sat Mar 6 19:00:29 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 31-Dec-07  Version 8.02 01-Mar-2010
5    ------------------------
6    
7    1.  The Unicode data tables have been updated to Unicode 5.2.0.
8    
9    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
10        configured.
11    
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.
14    
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.
17    
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".
22    
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.
27    
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).
32    
33    8.  Following on from 7, I added a similar kludge to check the length of the
34        eint vector in pcreposix.c.
35    
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.
41    
42    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
43    
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.
48    
49    
50    Version 8.01 19-Jan-2010
51    ------------------------
52    
53    1.  If a pattern contained a conditional subpattern with only one branch (in
54        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
55        computed the wrong minimum data length (which is of course zero for such
56        subpatterns). This could cause incorrect "no match" results.
57    
58    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
59        the pattern is reset in the first branch, pcre_compile() failed with
60        "internal error: code overflow at offset...". This happened only when
61        the reset was to the original external option setting. (An optimization
62        abstracts leading options settings into an external setting, which was the
63        cause of this.)
64    
65    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
66        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
67        assertion pattern did not match (meaning that the assertion was true), it
68        was incorrectly treated as false if the SKIP had been reached during the
69        matching. This also applied to assertions used as conditions.
70    
71    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
72        assertion subpattern, including such a pattern used as a condition,
73        unpredictable results occurred, instead of the error return
74        PCRE_ERROR_DFA_UITEM.
75    
76    5.  The C++ GlobalReplace function was not working like Perl for the special
77        situation when an empty string is matched. It now does the fancy magic
78        stuff that is necessary.
79    
80    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
81        removed. (These were left over from very, very early versions of PCRE.)
82    
83    7.  Some cosmetic changes to the code to make life easier when compiling it
84        as part of something else:
85    
86        (a) Change DEBUG to PCRE_DEBUG.
87    
88        (b) In pcre_compile(), rename the member of the "branch_chain" structure
89            called "current" as "current_branch", to prevent a collision with the
90            Linux macro when compiled as a kernel module.
91    
92        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
93            prevent a collision with the Linux macro when compiled as a kernel
94            module.
95    
96    8.  In pcre_compile() there are some checks for integer overflows that used to
97        cast potentially large values to (double). This has been changed to that
98        when building, a check for int64_t is made, and if it is found, it is used
99        instead, thus avoiding the use of floating point arithmetic. (There is no
100        other use of FP in PCRE.) If int64_t is not found, the fallback is to
101        double.
102    
103    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
104        2005 (difference between two addresses compared to an unsigned value).
105    
106    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
107        custom one, because of the following reported problem in Windows:
108    
109          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
110              under Win32.
111          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
112              therefore missing the function definition.
113          - The compiler thus generates a "C" signature for the test function.
114          - The linker fails to find the "C" function.
115          - PCRE fails to configure if asked to do so against libbz2.
116    
117    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
118        messages were output:
119    
120          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
121          rerunning libtoolize, to keep the correct libtool macros in-tree.
122          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
123    
124        I have done both of these things.
125    
126    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
127        most of the time, it *can* run out if it is given a pattern that contains a
128        runaway infinite recursion. I updated the discussion in the pcrestack man
129        page.
130    
131    13. Now that we have gone to the x.xx style of version numbers, the minor
132        version may start with zero. Using 08 or 09 is a bad idea because users
133        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
134        interpreted as invalid octal numbers. I've updated the previous comment in
135        configure.ac, and also added a check that gives an error if 08 or 09 are
136        used.
137    
138    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
139        causing partial matching to fail when the end of the subject matched \W
140        in a UTF-8 pattern where \W was quantified with a minimum of 3.
141    
142    15. There were some discrepancies between the declarations in pcre_internal.h
143        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
144        their definitions. The declarations used "const uschar *" and the
145        definitions used USPTR. Even though USPTR is normally defined as "const
146        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
147        reported that: "This difference in casting confuses some C++ compilers, for
148        example, SunCC recognizes above declarations as different functions and
149        generates broken code for hbpcre." I have changed the declarations to use
150        USPTR.
151    
152    16. GNU libtool is named differently on some systems. The autogen.sh script now
153        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
154        (FreeBSD).
155    
156    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
157        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
158        comment: "Figure out how to create a longlong from a string: strtoll and
159        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
160        instance, but it only takes 2 args instead of 3!"
161    
162    18. A subtle bug concerned with back references has been fixed by a change of
163        specification, with a corresponding code fix. A pattern such as
164        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
165        refers, was giving matches when it shouldn't. For example, xa=xaaa would
166        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
167        same bug. Such groups have to be quantified to be useful, or contained
168        inside another quantified group. (If there's no repetition, the reference
169        can never match.) The problem arises because, having left the group and
170        moved on to the rest of the pattern, a later failure that backtracks into
171        the group uses the captured value from the final iteration of the group
172        rather than the correct earlier one. I have fixed this in PCRE by forcing
173        any group that contains a reference to itself to be an atomic group; that
174        is, there cannot be any backtracking into it once it has completed. This is
175        similar to recursive and subroutine calls.
176    
177    
178    Version 8.00 19-Oct-09
179    ----------------------
180    
181    1.  The table for translating pcre_compile() error codes into POSIX error codes
182        was out-of-date, and there was no check on the pcre_compile() error code
183        being within the table. This could lead to an OK return being given in
184        error.
185    
186    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
187        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
188        in a Windows environment.
189    
190    3.  The pcregrep --count option prints the count for each file even when it is
191        zero, as does GNU grep. However, pcregrep was also printing all files when
192        --files-with-matches was added. Now, when both options are given, it prints
193        counts only for those files that have at least one match. (GNU grep just
194        prints the file name in this circumstance, but including the count seems
195        more useful - otherwise, why use --count?) Also ensured that the
196        combination -clh just lists non-zero counts, with no names.
197    
198    4.  The long form of the pcregrep -F option was incorrectly implemented as
199        --fixed_strings instead of --fixed-strings. This is an incompatible change,
200        but it seems right to fix it, and I didn't think it was worth preserving
201        the old behaviour.
202    
203    5.  The command line items --regex=pattern and --regexp=pattern were not
204        recognized by pcregrep, which required --regex pattern or --regexp pattern
205        (with a space rather than an '='). The man page documented the '=' forms,
206        which are compatible with GNU grep; these now work.
207    
208    6.  No libpcreposix.pc file was created for pkg-config; there was just
209        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
210    
211    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
212        when UCP support is not needed, by modifying the Python script that
213        generates it from Unicode data files. This should not matter if the module
214        is correctly used as a library, but I received one complaint about 50K of
215        unwanted data. My guess is that the person linked everything into his
216        program rather than using a library. Anyway, it does no harm.
217    
218    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
219        was a minimum greater than 1 for a wide character in a possessive
220        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
221        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
222        character. Chaos in the form of incorrect output or a compiling loop could
223        result.
224    
225    9.  The restrictions on what a pattern can contain when partial matching is
226        requested for pcre_exec() have been removed. All patterns can now be
227        partially matched by this function. In addition, if there are at least two
228        slots in the offset vector, the offset of the earliest inspected character
229        for the match and the offset of the end of the subject are set in them when
230        PCRE_ERROR_PARTIAL is returned.
231    
232    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
233        synonymous with PCRE_PARTIAL, for backwards compatibility, and
234        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
235        and may be more useful for multi-segment matching.
236    
237    11. Partial matching with pcre_exec() is now more intuitive. A partial match
238        used to be given if ever the end of the subject was reached; now it is
239        given only if matching could not proceed because another character was
240        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
241        string "Z", which now yields "no match" instead of "partial match". In the
242        case of pcre_dfa_exec(), "no match" is given if every matching path for the
243        final character ended with (*FAIL).
244    
245    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
246        if the pattern had a "must contain" character that was already found in the
247        earlier partial match, unless partial matching was again requested. For
248        example, with the pattern /dog.(body)?/, the "must contain" character is
249        "g". If the first part-match was for the string "dog", restarting with
250        "sbody" failed. This bug has been fixed.
251    
252    13. The string returned by pcre_dfa_exec() after a partial match has been
253        changed so that it starts at the first inspected character rather than the
254        first character of the match. This makes a difference only if the pattern
255        starts with a lookbehind assertion or \b or \B (\K is not supported by
256        pcre_dfa_exec()). It's an incompatible change, but it makes the two
257        matching functions compatible, and I think it's the right thing to do.
258    
259    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
260        so that the demonstration program is easily available in environments where
261        PCRE has not been installed from source.
262    
263    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
264        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
265        library.
266    
267    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
268        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
269        is not the first non-POSIX option to be added. Clearly some people find
270        these options useful.
271    
272    17. If a caller to the POSIX matching function regexec() passes a non-zero
273        value for nmatch with a NULL value for pmatch, the value of
274        nmatch is forced to zero.
275    
276    18. RunGrepTest did not have a test for the availability of the -u option of
277        the diff command, as RunTest does. It now checks in the same way as
278        RunTest, and also checks for the -b option.
279    
280    19. If an odd number of negated classes containing just a single character
281        interposed, within parentheses, between a forward reference to a named
282        subpattern and the definition of the subpattern, compilation crashed with
283        an internal error, complaining that it could not find the referenced
284        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
285        [The bug was that it was starting one character too far in when skipping
286        over the character class, thus treating the ] as data rather than
287        terminating the class. This meant it could skip too much.]
288    
289    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
290        /g option in pcretest when the pattern contains \K, which makes it possible
291        to have an empty string match not at the start, even when the pattern is
292        anchored. Updated pcretest and pcredemo to use this option.
293    
294    21. If the maximum number of capturing subpatterns in a recursion was greater
295        than the maximum at the outer level, the higher number was returned, but
296        with unset values at the outer level. The correct (outer level) value is
297        now given.
298    
299    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
300        PCRE did not set those parentheses (unlike Perl). I have now found a way to
301        make it do so. The string so far is captured, making this feature
302        compatible with Perl.
303    
304    23. The tests have been re-organized, adding tests 11 and 12, to make it
305        possible to check the Perl 5.10 features against Perl 5.10.
306    
307    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
308        pattern matches a fixed length string. PCRE did not allow this; now it
309        does. Neither allows recursion.
310    
311    25. I finally figured out how to implement a request to provide the minimum
312        length of subject string that was needed in order to match a given pattern.
313        (It was back references and recursion that I had previously got hung up
314        on.) This code has now been added to pcre_study(); it finds a lower bound
315        to the length of subject needed. It is not necessarily the greatest lower
316        bound, but using it to avoid searching strings that are too short does give
317        some useful speed-ups. The value is available to calling programs via
318        pcre_fullinfo().
319    
320    26. While implementing 25, I discovered to my embarrassment that pcretest had
321        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
322        study optimizations had never been tested with that matching function.
323        Oops. What is worse, even when it was passed study data, there was a bug in
324        pcre_dfa_exec() that meant it never actually used it. Double oops. There
325        were also very few tests of studied patterns with pcre_dfa_exec().
326    
327    27. If (?| is used to create subpatterns with duplicate numbers, they are now
328        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
329        on the other side of the coin, they are no longer allowed to have different
330        names, because these cannot be distinguished in PCRE, and this has caused
331        confusion. (This is a difference from Perl.)
332    
333    28. When duplicate subpattern names are present (necessarily with different
334        numbers, as required by 27 above), and a test is made by name in a
335        conditional pattern, either for a subpattern having been matched, or for
336        recursion in such a pattern, all the associated numbered subpatterns are
337        tested, and the overall condition is true if the condition is true for any
338        one of them. This is the way Perl works, and is also more like the way
339        testing by number works.
340    
341    
342    Version 7.9 11-Apr-09
343    ---------------------
344    
345    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
346        (pcretest), all targets were linked against these libraries. This included
347        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
348        libraries. This caused unwanted dependencies to be created. This problem
349        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
350        pcretest is linked with readline.
351    
352    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
353        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
354        moved outside it again, because FALSE and TRUE are already defined in AIX,
355        but BOOL is not.
356    
357    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
358        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
359    
360    4.  The pcregrep documentation said spaces were inserted as well as colons (or
361        hyphens) following file names and line numbers when outputting matching
362        lines. This is not true; no spaces are inserted. I have also clarified the
363        wording for the --colour (or --color) option.
364    
365    5.  In pcregrep, when --colour was used with -o, the list of matching strings
366        was not coloured; this is different to GNU grep, so I have changed it to be
367        the same.
368    
369    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
370        each matching line was coloured. Now it goes on to look for further matches
371        of any of the test patterns, which is the same behaviour as GNU grep.
372    
373    7.  A pattern that could match an empty string could cause pcregrep to loop; it
374        doesn't make sense to accept an empty string match in pcregrep, so I have
375        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
376        seems to be how GNU grep behaves.
377    
378    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
379        start or after a newline", because the conditional assertion was not being
380        correctly handled. The rule now is that both the assertion and what follows
381        in the first alternative must satisfy the test.
382    
383    9.  If auto-callout was enabled in a pattern with a conditional group whose
384        condition was an assertion, PCRE could crash during matching, both with
385        pcre_exec() and pcre_dfa_exec().
386    
387    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
388        used for matching.
389    
390    11. Unicode property support in character classes was not working for
391        characters (bytes) greater than 127 when not in UTF-8 mode.
392    
393    12. Added the -M command line option to pcretest.
394    
395    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
396    
397    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
398    
399    16. Added comments and documentation about mis-use of no_arg in the C++
400        wrapper.
401    
402    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
403        from Martin Jerabek that uses macro names for all relevant character and
404        string constants.
405    
406    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
407        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
408        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
409        these, but not everybody uses configure.
410    
411    19. A conditional group that had only one branch was not being correctly
412        recognized as an item that could match an empty string. This meant that an
413        enclosing group might also not be so recognized, causing infinite looping
414        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
415        with the subject "ab", where knowledge that the repeated group can match
416        nothing is needed in order to break the loop.
417    
418    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
419        exec(), but without supplying a callout function, matching went wrong.
420    
421    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
422        leak if the size of the offset vector was greater than 30. When the vector
423        is smaller, the saved offsets during recursion go onto a local stack
424        vector, but for larger vectors malloc() is used. It was failing to free
425        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
426        error, in fact).
427    
428    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
429        heapframe that is used only when UTF-8 support is enabled. This caused no
430        problem, but was untidy.
431    
432    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
433        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
434        included within another project.
435    
436    24. Steven Van Ingelgem's patches to add more options to the CMake support,
437        slightly modified by me:
438    
439          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
440              not building pcregrep.
441    
442          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
443              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
444    
445    25. Forward references, both numeric and by name, in patterns that made use of
446        duplicate group numbers, could behave incorrectly or give incorrect errors,
447        because when scanning forward to find the reference group, PCRE was not
448        taking into account the duplicate group numbers. A pattern such as
449        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
450    
451    26. Changed a few more instances of "const unsigned char *" to USPTR, making
452        the feature of a custom pointer more persuasive (as requested by a user).
453    
454    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
455        pcretest.c, inside #ifndefs, because it seems they are sometimes already
456        pre-defined.
457    
458    28. Added support for (*UTF8) at the start of a pattern.
459    
460    29. Arrange for flags added by the "release type" setting in CMake to be shown
461        in the configuration summary.
462    
463    
464    Version 7.8 05-Sep-08
465    ---------------------
466    
467    1.  Replaced UCP searching code with optimized version as implemented for Ad
468        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
469        stage table and inline lookup instead of a function, giving speed ups of 2
470        to 5 times on some simple patterns that I tested. Permission was given to
471        distribute the MultiStage2.py script that generates the tables (it's not in
472        the tarball, but is in the Subversion repository).
473    
474    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
475        scripts.
476    
477    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
478        a group with a zero qualifier. The result of the study could be incorrect,
479        or the function might crash, depending on the pattern.
480    
481    4.  Caseless matching was not working for non-ASCII characters in back
482        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
483        It now works when Unicode Property Support is available.
484    
485    5.  In pcretest, an escape such as \x{de} in the data was always generating
486        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
487        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
488        truncation.
489    
490    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
491    
492    7.  Added two (int) casts to pcregrep when printing the difference of two
493        pointers, in case they are 64-bit values.
494    
495    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
496        test 2 if it fails.
497    
498    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
499        and a #define of that name to empty if it is not externally set. This is to
500        allow users of MSVC to set it if necessary.
501    
502    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
503        the convenience functions in the pcre_get.c source file.
504    
505    11. An option change at the start of a pattern that had top-level alternatives
506        could cause overwriting and/or a crash. This command provoked a crash in
507        some environments:
508    
509          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
510    
511        This potential security problem was recorded as CVE-2008-2371.
512    
513    12. For a pattern where the match had to start at the beginning or immediately
514        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
515        pcre_dfa_exec() could read past the end of the passed subject if there was
516        no match. To help with detecting such bugs (e.g. with valgrind), I modified
517        pcretest so that it places the subject at the end of its malloc-ed buffer.
518    
519    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
520        exec() might read past the end of the data buffer in UTF-8 mode.
521    
522    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
523        the data contained the byte 0x85 as part of a UTF-8 character within its
524        first line. This applied both to normal and DFA matching.
525    
526    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
527        /^[^d]*?$/8 failed to match "abc".
528    
529    16. Added a missing copyright notice to pcrecpp_internal.h.
530    
531    17. Make it more clear in the documentation that values returned from
532        pcre_exec() in ovector are byte offsets, not character counts.
533    
534    18. Tidied a few places to stop certain compilers from issuing warnings.
535    
536    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
537        supplied by Stefan Weber. I made a further small update for 7.8 because
538        there is a change of source arrangements: the pcre_searchfuncs.c module is
539        replaced by pcre_ucd.c.
540    
541    
542    Version 7.7 07-May-08
543    ---------------------
544    
545    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
546        a string to a long long, pretend we don't even have a long long." This is
547        done by checking for the strtoq, strtoll, and _strtoi64 functions.
548    
549    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
550        pre-7.6 versions, which defined a global no_arg variable instead of putting
551        it in the RE class. (See also #8 below.)
552    
553    3.  Remove a line of dead code, identified by coverity and reported by Nuno
554        Lopes.
555    
556    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
557    
558        (1) The include/exclude patterns were being applied to the whole pathnames
559            of files, instead of just to the final components.
560    
561        (2) If there was more than one level of directory, the subdirectories were
562            skipped unless they satisfied the include/exclude conditions. This is
563            inconsistent with GNU grep (and could even be seen as contrary to the
564            pcregrep specification - which I improved to make it absolutely clear).
565            The action now is always to scan all levels of directory, and just
566            apply the include/exclude patterns to regular files.
567    
568    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
569        --exclude_dir in the tests to avoid scanning .svn directories.
570    
571    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
572        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
573        doesn't support NULs in patterns.
574    
575    7.  Added some missing "const"s to declarations of static tables in
576        pcre_compile.c and pcre_dfa_exec.c.
577    
578    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
579        caused by fix #2  above. (Subsequently also a second patch to fix the
580        first patch. And a third patch - this was a messy problem.)
581    
582    9.  Applied Craig's patch to remove the use of push_back().
583    
584    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
585        matching function regexec().
586    
587    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
588        which, however, unlike Perl's \g{...}, are subroutine calls, not back
589        references. PCRE supports relative numbers with this syntax (I don't think
590        Oniguruma does).
591    
592    12. Previously, a group with a zero repeat such as (...){0} was completely
593        omitted from the compiled regex. However, this means that if the group
594        was called as a subroutine from elsewhere in the pattern, things went wrong
595        (an internal error was given). Such groups are now left in the compiled
596        pattern, with a new opcode that causes them to be skipped at execution
597        time.
598    
599    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
600        to the way PCRE behaves:
601    
602        (a) A lone ] character is dis-allowed (Perl treats it as data).
603    
604        (b) A back reference to an unmatched subpattern matches an empty string
605            (Perl fails the current match path).
606    
607        (c) A data ] in a character class must be notated as \] because if the
608            first data character in a class is ], it defines an empty class. (In
609            Perl it is not possible to have an empty class.) The empty class []
610            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
611            The negative empty class [^] matches any one character, independently
612            of the DOTALL setting.
613    
614    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
615        non-existent subpattern following a character class starting with ']' and
616        containing () gave an internal compiling error instead of "reference to
617        non-existent subpattern". Fortunately, when the pattern did exist, the
618        compiled code was correct. (When scanning forwards to check for the
619        existencd of the subpattern, it was treating the data ']' as terminating
620        the class, so got the count wrong. When actually compiling, the reference
621        was subsequently set up correctly.)
622    
623    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
624        it was being rejected as not supported by pcre_dfa_exec(), even though
625        other assertions are supported. I have made pcre_dfa_exec() support
626        (*FAIL).
627    
628    16. The implementation of 13c above involved the invention of a new opcode,
629        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
630        cannot be changed at match time, I realized I could make a small
631        improvement to matching performance by compiling OP_ALLANY instead of
632        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
633        on the OP_ANY path.
634    
635    17. Compiling pcretest on Windows with readline support failed without the
636        following two fixes: (1) Make the unistd.h include conditional on
637        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
638    
639    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
640        ncurses library to be included for pcretest when ReadLine support is
641        requested, but also to allow for it to be overridden. This patch came from
642        Daniel Bergström.
643    
644    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
645        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
646        any errors with the current Unicode tables. Thanks to Peter Kankowski for
647        spotting this.
648    
649    
650    Version 7.6 28-Jan-08
651    ---------------------
652    
653    1.  A character class containing a very large number of characters with
654        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
655        overflow.
656    
657    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
658        HAVE_LONG_LONG is not defined.
659    
660    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
661        bring them up to date and include new features. This patch includes:
662    
663        - Fixed PH's badly added libz and libbz2 support.
664        - Fixed a problem with static linking.
665        - Added pcredemo. [But later removed - see 7 below.]
666        - Fixed dftables problem and added an option.
667        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
668            HAVE_LONG_LONG.
669        - Added readline support for pcretest.
670        - Added an listing of the option settings after cmake has run.
671    
672    4.  A user submitted a patch to Makefile that makes it easy to create
673        "pcre.dll" under mingw when using Configure/Make. I added stuff to
674        Makefile.am that cause it to include this special target, without
675        affecting anything else. Note that the same mingw target plus all
676        the other distribution libraries and programs are now supported
677        when configuring with CMake (see 6 below) instead of with
678        Configure/Make.
679    
680    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
681        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
682        exported in the Windows port". It has not yet been confirmed that the patch
683        solves the problem, but it does no harm.
684    
685    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
686        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
687        with CMake, and also correct the comment about stack recursion.
688    
689    7.  Remove the automatic building of pcredemo from the ./configure system and
690        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
691        of a program that users should build themselves after PCRE is installed, so
692        building it automatically is not really right. What is more, it gave
693        trouble in some build environments.
694    
695    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
696    
697    
698    Version 7.5 10-Jan-08
699  ---------------------  ---------------------
700    
701  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
# Line 99  Version 7.5 31-Dec-07 Line 793  Version 7.5 31-Dec-07
793    
794  20. In pcrecpp.cc, the variable 'count' was incremented twice in  20. In pcrecpp.cc, the variable 'count' was incremented twice in
795      RE::GlobalReplace(). As a result, the number of replacements returned was      RE::GlobalReplace(). As a result, the number of replacements returned was
796      double what it should be. I have removed one of the increments.      double what it should be. I removed one of the increments, but Craig sent a
797        later patch that removed the other one (the right fix) and added unit tests
798        that check the return values (which was not done before).
799    
800  21. Several CMake things:  21. Several CMake things:
801    
# Line 110  Version 7.5 31-Dec-07 Line 806  Version 7.5 31-Dec-07
806          linked with the newly-built libraries, not previously installed ones.          linked with the newly-built libraries, not previously installed ones.
807    
808      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
809    
810  22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*  22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
811      crashed when matching a string such as a\x{2029}b (note that \x{2029} is a      crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
812      UTF-8 newline character). The key issue is that the pattern starts .*;      UTF-8 newline character). The key issue is that the pattern starts .*;
813      this means that the match must be either at the beginning, or after a      this means that the match must be either at the beginning, or after a
814      newline. The bug was in the code for advancing after a failed match and      newline. The bug was in the code for advancing after a failed match and
815      checking that the new position followed a newline. It was not taking      checking that the new position followed a newline. It was not taking
816      account of UTF-8 characters correctly.      account of UTF-8 characters correctly.
817    
818  23. PCRE was behaving differently from Perl in the way it recognized POSIX  23. PCRE was behaving differently from Perl in the way it recognized POSIX
819      character classes. PCRE was not treating the sequence [:...:] as a      character classes. PCRE was not treating the sequence [:...:] as a
820      character class unless the ... were all letters. Perl, however, seems to      character class unless the ... were all letters. Perl, however, seems to
821      allow any characters between [: and :], though of course it rejects as      allow any characters between [: and :], though of course it rejects as
822      unknown any "names" that contain non-letters, because all the known class      unknown any "names" that contain non-letters, because all the known class
823      names consist only of letters. Thus, Perl gives an error for [[:1234:]],      names consist only of letters. Thus, Perl gives an error for [[:1234:]],
824      for example, whereas PCRE did not - it did not recognize a POSIX character      for example, whereas PCRE did not - it did not recognize a POSIX character
825      class. This seemed a bit dangerous, so the code has been changed to be      class. This seemed a bit dangerous, so the code has been changed to be
826      closer to Perl. The behaviour is not identical to Perl, because PCRE will      closer to Perl. The behaviour is not identical to Perl, because PCRE will
827      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
828      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
829      Perl does, and where it didn't before.      Perl does, and where it didn't before.
830    
831    24. Rewrite so as to remove the single use of %n from pcregrep because in some
832        Windows environments %n is disabled by default.
833    
834    
835  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Legend:
Removed from v.295  
changed lines
  Added in v.500

  ViewVC Help
Powered by ViewVC 1.1.5