ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 368 by ph10, Sun Aug 24 16:25:20 2008 UTC revision 511 by ph10, Mon Mar 29 09:25:38 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.8 25-Aug-08  Version 8.03 26-Mar-2010
5    ------------------------
7    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
8        THEN.
10    2.  (*ACCEPT) was not working when inside an atomic group.
13    Version 8.02 19-Mar-2010
14    ------------------------
16    1.  The Unicode data tables have been updated to Unicode 5.2.0.
18    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
19        configured.
21    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
22        original author of that file, following a query about its status.
24    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
25        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
27    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
28        quantifier applied to a forward-referencing subroutine call, could compile
29        incorrect code or give the error "internal error: previously-checked
30        referenced subpattern not found".
32    6.  Both MS Visual Studio and Symbian OS have problems with initializing
33        variables to point to external functions. For these systems, therefore,
34        pcre_malloc etc. are now initialized to local functions that call the
35        relevant global functions.
37    7.  There were two entries missing in the vectors called coptable and poptable
38        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
39        I've fixed the data, and added a kludgy way of testing at compile time that
40        the lengths are correct (equal to the number of opcodes).
42    8.  Following on from 7, I added a similar kludge to check the length of the
43        eint vector in pcreposix.c.
45    9.  Error texts for pcre_compile() are held as one long string to avoid too
46        much relocation at load time. To find a text, the string is searched,
47        counting zeros. There was no check for running off the end of the string,
48        which could happen if a new error number was added without updating the
49        string.
51    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
53    11. \K was not working if it appeared in an atomic group or in a group that
54        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
55        \K is "not well defined" if used in an assertion. PCRE now accepts it if
56        the assertion is positive, but not if it is negative.
58    12. Change 11 fortuitously reduced the size of the stack frame used in the
59        "match()" function of pcre_exec.c by one pointer. Forthcoming
60        implementation of support for (*MARK) will need an extra pointer on the
61        stack; I have reserved it now, so that the stack frame size does not
62        decrease.
64    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
65        item in branch that calls a recursion is a subroutine call - as in the
66        second branch in the above example - was incorrectly given the compile-
67        time error "recursive call could loop indefinitely" because pcre_compile()
68        was not correctly checking the subroutine for matching a non-empty string.
70    14. The checks for overrunning compiling workspace could trigger after an
71        overrun had occurred. This is a "should never occur" error, but it can be
72        triggered by pathological patterns such as hundreds of nested parentheses.
73        The checks now trigger 100 bytes before the end of the workspace.
75    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
78    Version 8.01 19-Jan-2010
79    ------------------------
81    1.  If a pattern contained a conditional subpattern with only one branch (in
82        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
83        computed the wrong minimum data length (which is of course zero for such
84        subpatterns). This could cause incorrect "no match" results.
86    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
87        the pattern is reset in the first branch, pcre_compile() failed with
88        "internal error: code overflow at offset...". This happened only when
89        the reset was to the original external option setting. (An optimization
90        abstracts leading options settings into an external setting, which was the
91        cause of this.)
93    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
94        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
95        assertion pattern did not match (meaning that the assertion was true), it
96        was incorrectly treated as false if the SKIP had been reached during the
97        matching. This also applied to assertions used as conditions.
99    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
100        assertion subpattern, including such a pattern used as a condition,
101        unpredictable results occurred, instead of the error return
104    5.  The C++ GlobalReplace function was not working like Perl for the special
105        situation when an empty string is matched. It now does the fancy magic
106        stuff that is necessary.
108    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
109        removed. (These were left over from very, very early versions of PCRE.)
111    7.  Some cosmetic changes to the code to make life easier when compiling it
112        as part of something else:
114        (a) Change DEBUG to PCRE_DEBUG.
116        (b) In pcre_compile(), rename the member of the "branch_chain" structure
117            called "current" as "current_branch", to prevent a collision with the
118            Linux macro when compiled as a kernel module.
120        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
121            prevent a collision with the Linux macro when compiled as a kernel
122            module.
124    8.  In pcre_compile() there are some checks for integer overflows that used to
125        cast potentially large values to (double). This has been changed to that
126        when building, a check for int64_t is made, and if it is found, it is used
127        instead, thus avoiding the use of floating point arithmetic. (There is no
128        other use of FP in PCRE.) If int64_t is not found, the fallback is to
129        double.
131    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
132        2005 (difference between two addresses compared to an unsigned value).
134    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
135        custom one, because of the following reported problem in Windows:
137          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
138              under Win32.
139          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
140              therefore missing the function definition.
141          - The compiler thus generates a "C" signature for the test function.
142          - The linker fails to find the "C" function.
143          - PCRE fails to configure if asked to do so against libbz2.
145    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
146        messages were output:
148          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
149          rerunning libtoolize, to keep the correct libtool macros in-tree.
150          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
152        I have done both of these things.
154    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
155        most of the time, it *can* run out if it is given a pattern that contains a
156        runaway infinite recursion. I updated the discussion in the pcrestack man
157        page.
159    13. Now that we have gone to the x.xx style of version numbers, the minor
160        version may start with zero. Using 08 or 09 is a bad idea because users
161        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
162        interpreted as invalid octal numbers. I've updated the previous comment in
163        configure.ac, and also added a check that gives an error if 08 or 09 are
164        used.
166    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
167        causing partial matching to fail when the end of the subject matched \W
168        in a UTF-8 pattern where \W was quantified with a minimum of 3.
170    15. There were some discrepancies between the declarations in pcre_internal.h
171        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
172        their definitions. The declarations used "const uschar *" and the
173        definitions used USPTR. Even though USPTR is normally defined as "const
174        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
175        reported that: "This difference in casting confuses some C++ compilers, for
176        example, SunCC recognizes above declarations as different functions and
177        generates broken code for hbpcre." I have changed the declarations to use
178        USPTR.
180    16. GNU libtool is named differently on some systems. The autogen.sh script now
181        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
182        (FreeBSD).
184    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
185        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
186        comment: "Figure out how to create a longlong from a string: strtoll and
187        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
188        instance, but it only takes 2 args instead of 3!"
190    18. A subtle bug concerned with back references has been fixed by a change of
191        specification, with a corresponding code fix. A pattern such as
192        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
193        refers, was giving matches when it shouldn't. For example, xa=xaaa would
194        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
195        same bug. Such groups have to be quantified to be useful, or contained
196        inside another quantified group. (If there's no repetition, the reference
197        can never match.) The problem arises because, having left the group and
198        moved on to the rest of the pattern, a later failure that backtracks into
199        the group uses the captured value from the final iteration of the group
200        rather than the correct earlier one. I have fixed this in PCRE by forcing
201        any group that contains a reference to itself to be an atomic group; that
202        is, there cannot be any backtracking into it once it has completed. This is
203        similar to recursive and subroutine calls.
206    Version 8.00 19-Oct-09
207    ----------------------
209    1.  The table for translating pcre_compile() error codes into POSIX error codes
210        was out-of-date, and there was no check on the pcre_compile() error code
211        being within the table. This could lead to an OK return being given in
212        error.
214    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
215        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
216        in a Windows environment.
218    3.  The pcregrep --count option prints the count for each file even when it is
219        zero, as does GNU grep. However, pcregrep was also printing all files when
220        --files-with-matches was added. Now, when both options are given, it prints
221        counts only for those files that have at least one match. (GNU grep just
222        prints the file name in this circumstance, but including the count seems
223        more useful - otherwise, why use --count?) Also ensured that the
224        combination -clh just lists non-zero counts, with no names.
226    4.  The long form of the pcregrep -F option was incorrectly implemented as
227        --fixed_strings instead of --fixed-strings. This is an incompatible change,
228        but it seems right to fix it, and I didn't think it was worth preserving
229        the old behaviour.
231    5.  The command line items --regex=pattern and --regexp=pattern were not
232        recognized by pcregrep, which required --regex pattern or --regexp pattern
233        (with a space rather than an '='). The man page documented the '=' forms,
234        which are compatible with GNU grep; these now work.
236    6.  No libpcreposix.pc file was created for pkg-config; there was just
237        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
239    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
240        when UCP support is not needed, by modifying the Python script that
241        generates it from Unicode data files. This should not matter if the module
242        is correctly used as a library, but I received one complaint about 50K of
243        unwanted data. My guess is that the person linked everything into his
244        program rather than using a library. Anyway, it does no harm.
246    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
247        was a minimum greater than 1 for a wide character in a possessive
248        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
249        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
250        character. Chaos in the form of incorrect output or a compiling loop could
251        result.
253    9.  The restrictions on what a pattern can contain when partial matching is
254        requested for pcre_exec() have been removed. All patterns can now be
255        partially matched by this function. In addition, if there are at least two
256        slots in the offset vector, the offset of the earliest inspected character
257        for the match and the offset of the end of the subject are set in them when
258        PCRE_ERROR_PARTIAL is returned.
260    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
261        synonymous with PCRE_PARTIAL, for backwards compatibility, and
262        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
263        and may be more useful for multi-segment matching.
265    11. Partial matching with pcre_exec() is now more intuitive. A partial match
266        used to be given if ever the end of the subject was reached; now it is
267        given only if matching could not proceed because another character was
268        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
269        string "Z", which now yields "no match" instead of "partial match". In the
270        case of pcre_dfa_exec(), "no match" is given if every matching path for the
271        final character ended with (*FAIL).
273    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
274        if the pattern had a "must contain" character that was already found in the
275        earlier partial match, unless partial matching was again requested. For
276        example, with the pattern /dog.(body)?/, the "must contain" character is
277        "g". If the first part-match was for the string "dog", restarting with
278        "sbody" failed. This bug has been fixed.
280    13. The string returned by pcre_dfa_exec() after a partial match has been
281        changed so that it starts at the first inspected character rather than the
282        first character of the match. This makes a difference only if the pattern
283        starts with a lookbehind assertion or \b or \B (\K is not supported by
284        pcre_dfa_exec()). It's an incompatible change, but it makes the two
285        matching functions compatible, and I think it's the right thing to do.
287    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
288        so that the demonstration program is easily available in environments where
289        PCRE has not been installed from source.
291    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
292        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
293        library.
295    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
296        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
297        is not the first non-POSIX option to be added. Clearly some people find
298        these options useful.
300    17. If a caller to the POSIX matching function regexec() passes a non-zero
301        value for nmatch with a NULL value for pmatch, the value of
302        nmatch is forced to zero.
304    18. RunGrepTest did not have a test for the availability of the -u option of
305        the diff command, as RunTest does. It now checks in the same way as
306        RunTest, and also checks for the -b option.
308    19. If an odd number of negated classes containing just a single character
309        interposed, within parentheses, between a forward reference to a named
310        subpattern and the definition of the subpattern, compilation crashed with
311        an internal error, complaining that it could not find the referenced
312        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
313        [The bug was that it was starting one character too far in when skipping
314        over the character class, thus treating the ] as data rather than
315        terminating the class. This meant it could skip too much.]
317    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
318        /g option in pcretest when the pattern contains \K, which makes it possible
319        to have an empty string match not at the start, even when the pattern is
320        anchored. Updated pcretest and pcredemo to use this option.
322    21. If the maximum number of capturing subpatterns in a recursion was greater
323        than the maximum at the outer level, the higher number was returned, but
324        with unset values at the outer level. The correct (outer level) value is
325        now given.
327    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
328        PCRE did not set those parentheses (unlike Perl). I have now found a way to
329        make it do so. The string so far is captured, making this feature
330        compatible with Perl.
332    23. The tests have been re-organized, adding tests 11 and 12, to make it
333        possible to check the Perl 5.10 features against Perl 5.10.
335    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
336        pattern matches a fixed length string. PCRE did not allow this; now it
337        does. Neither allows recursion.
339    25. I finally figured out how to implement a request to provide the minimum
340        length of subject string that was needed in order to match a given pattern.
341        (It was back references and recursion that I had previously got hung up
342        on.) This code has now been added to pcre_study(); it finds a lower bound
343        to the length of subject needed. It is not necessarily the greatest lower
344        bound, but using it to avoid searching strings that are too short does give
345        some useful speed-ups. The value is available to calling programs via
346        pcre_fullinfo().
348    26. While implementing 25, I discovered to my embarrassment that pcretest had
349        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
350        study optimizations had never been tested with that matching function.
351        Oops. What is worse, even when it was passed study data, there was a bug in
352        pcre_dfa_exec() that meant it never actually used it. Double oops. There
353        were also very few tests of studied patterns with pcre_dfa_exec().
355    27. If (?| is used to create subpatterns with duplicate numbers, they are now
356        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
357        on the other side of the coin, they are no longer allowed to have different
358        names, because these cannot be distinguished in PCRE, and this has caused
359        confusion. (This is a difference from Perl.)
361    28. When duplicate subpattern names are present (necessarily with different
362        numbers, as required by 27 above), and a test is made by name in a
363        conditional pattern, either for a subpattern having been matched, or for
364        recursion in such a pattern, all the associated numbered subpatterns are
365        tested, and the overall condition is true if the condition is true for any
366        one of them. This is the way Perl works, and is also more like the way
367        testing by number works.
370    Version 7.9 11-Apr-09
371    ---------------------
373    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
374        (pcretest), all targets were linked against these libraries. This included
375        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
376        libraries. This caused unwanted dependencies to be created. This problem
377        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
378        pcretest is linked with readline.
380    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
381        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
382        moved outside it again, because FALSE and TRUE are already defined in AIX,
383        but BOOL is not.
385    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
386        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
388    4.  The pcregrep documentation said spaces were inserted as well as colons (or
389        hyphens) following file names and line numbers when outputting matching
390        lines. This is not true; no spaces are inserted. I have also clarified the
391        wording for the --colour (or --color) option.
393    5.  In pcregrep, when --colour was used with -o, the list of matching strings
394        was not coloured; this is different to GNU grep, so I have changed it to be
395        the same.
397    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
398        each matching line was coloured. Now it goes on to look for further matches
399        of any of the test patterns, which is the same behaviour as GNU grep.
401    7.  A pattern that could match an empty string could cause pcregrep to loop; it
402        doesn't make sense to accept an empty string match in pcregrep, so I have
403        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
404        seems to be how GNU grep behaves.
406    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
407        start or after a newline", because the conditional assertion was not being
408        correctly handled. The rule now is that both the assertion and what follows
409        in the first alternative must satisfy the test.
411    9.  If auto-callout was enabled in a pattern with a conditional group whose
412        condition was an assertion, PCRE could crash during matching, both with
413        pcre_exec() and pcre_dfa_exec().
415    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
416        used for matching.
418    11. Unicode property support in character classes was not working for
419        characters (bytes) greater than 127 when not in UTF-8 mode.
421    12. Added the -M command line option to pcretest.
423    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
425    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
427    16. Added comments and documentation about mis-use of no_arg in the C++
428        wrapper.
430    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
431        from Martin Jerabek that uses macro names for all relevant character and
432        string constants.
434    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
435        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
436        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
437        these, but not everybody uses configure.
439    19. A conditional group that had only one branch was not being correctly
440        recognized as an item that could match an empty string. This meant that an
441        enclosing group might also not be so recognized, causing infinite looping
442        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
443        with the subject "ab", where knowledge that the repeated group can match
444        nothing is needed in order to break the loop.
446    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
447        exec(), but without supplying a callout function, matching went wrong.
449    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
450        leak if the size of the offset vector was greater than 30. When the vector
451        is smaller, the saved offsets during recursion go onto a local stack
452        vector, but for larger vectors malloc() is used. It was failing to free
453        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
454        error, in fact).
456    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
457        heapframe that is used only when UTF-8 support is enabled. This caused no
458        problem, but was untidy.
460    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
461        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
462        included within another project.
464    24. Steven Van Ingelgem's patches to add more options to the CMake support,
465        slightly modified by me:
467          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
468              not building pcregrep.
470          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
471              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
473    25. Forward references, both numeric and by name, in patterns that made use of
474        duplicate group numbers, could behave incorrectly or give incorrect errors,
475        because when scanning forward to find the reference group, PCRE was not
476        taking into account the duplicate group numbers. A pattern such as
477        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
479    26. Changed a few more instances of "const unsigned char *" to USPTR, making
480        the feature of a custom pointer more persuasive (as requested by a user).
482    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
483        pcretest.c, inside #ifndefs, because it seems they are sometimes already
484        pre-defined.
486    28. Added support for (*UTF8) at the start of a pattern.
488    29. Arrange for flags added by the "release type" setting in CMake to be shown
489        in the configuration summary.
492    Version 7.8 05-Sep-08
493  ---------------------  ---------------------
495  1.  Replaced UCP searching code with optimized version as implemented for Ad  1.  Replaced UCP searching code with optimized version as implemented for Ad
# Line 31  Version 7.8 25-Aug-08 Line 519  Version 7.8 25-Aug-08
520  7.  Added two (int) casts to pcregrep when printing the difference of two  7.  Added two (int) casts to pcregrep when printing the difference of two
521      pointers, in case they are 64-bit values.      pointers, in case they are 64-bit values.
523  8.  Added comments about Mac OS X stack usage to the pcrestack man page and to  8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
524      test 2 if it fails.      test 2 if it fails.
526  9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,  9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
527      and a #define of that name to empty if it is not externally set. This is to      and a #define of that name to empty if it is not externally set. This is to
528      allow users of MSVC to set it if necessary.      allow users of MSVC to set it if necessary.
530  10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from  10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
531      the convenience functions in the pcre_get.c source file.      the convenience functions in the pcre_get.c source file.
533  11. An option change at the start of a pattern that had top-level alternatives  11. An option change at the start of a pattern that had top-level alternatives
534      could cause overwriting and/or a crash. This command provoked a crash in      could cause overwriting and/or a crash. This command provoked a crash in
535      some environments:      some environments:
537        printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest        printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
539      This potential security problem was recorded as CVE-2008-2371.      This potential security problem was recorded as CVE-2008-2371.
541  12. For a pattern where the match had to start at the beginning or immediately  12. For a pattern where the match had to start at the beginning or immediately
542      after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and      after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
543      pcre_dfa_exec() could read past the end of the passed subject if there was      pcre_dfa_exec() could read past the end of the passed subject if there was
544      no match. To help with detecting such bugs (e.g. with valgrind), I modified      no match. To help with detecting such bugs (e.g. with valgrind), I modified
545      pcretest so that it places the subject at the end of its malloc-ed buffer.      pcretest so that it places the subject at the end of its malloc-ed buffer.
547  13. The change to pcretest in 12 above threw up a couple more cases when pcre_  13. The change to pcretest in 12 above threw up a couple more cases when pcre_
548      exec() might read past the end of the data buffer in UTF-8 mode.      exec() might read past the end of the data buffer in UTF-8 mode.
550  14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and  14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
551      the data contained the byte 0x85 as part of a UTF-8 character within its      the data contained the byte 0x85 as part of a UTF-8 character within its
552      first line. This applied both to normal and DFA matching.      first line. This applied both to normal and DFA matching.
554  15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,  15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
555      /^[^d]*?$/8 failed to match "abc".      /^[^d]*?$/8 failed to match "abc".
 16. Added a missing copyright notice to pcrecpp_internal.h.  
557  17. Make it more clear in the documentation that values returned from  16. Added a missing copyright notice to pcrecpp_internal.h.
559    17. Make it more clear in the documentation that values returned from
560      pcre_exec() in ovector are byte offsets, not character counts.      pcre_exec() in ovector are byte offsets, not character counts.
562    18. Tidied a few places to stop certain compilers from issuing warnings.
564    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
565        supplied by Stefan Weber. I made a further small update for 7.8 because
566        there is a change of source arrangements: the pcre_searchfuncs.c module is
567        replaced by pcre_ucd.c.
570  Version 7.7 07-May-08  Version 7.7 07-May-08
571  ---------------------  ---------------------

Removed from v.368  
changed lines
  Added in v.511

  ViewVC Help
Powered by ViewVC 1.1.5