1 |
ChangeLog for PCRE |
ChangeLog for PCRE |
2 |
------------------ |
------------------ |
3 |
|
|
4 |
Version 8.0 02 Jul-08 |
Version 7.9 xx-xxx-09 |
5 |
|
--------------------- |
6 |
|
|
7 |
|
1. When building with support for bzlib/zlib (pcregrep) and/or readline |
8 |
|
(pcretest), all targets were linked against these libraries. This included |
9 |
|
libpcre, libpcreposix, and libpcrecpp, even though they do not use these |
10 |
|
libraries. This caused unwanted dependencies to be created. This problem |
11 |
|
has been fixed, and now only pcregrep is linked with bzlib/zlib and only |
12 |
|
pcretest is linked with readline. |
13 |
|
|
14 |
|
2. The "typedef int BOOL" in pcre_internal.h that was included inside the |
15 |
|
"#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been |
16 |
|
moved outside it again, because FALSE and TRUE are already defined in AIX, |
17 |
|
but BOOL is not. |
18 |
|
|
19 |
|
3. The pcre_config() function was treating the PCRE_MATCH_LIMIT and |
20 |
|
PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints. |
21 |
|
|
22 |
|
4. The pcregrep documentation said spaces were inserted as well as colons (or |
23 |
|
hyphens) following file names and line numbers when outputting matching |
24 |
|
lines. This is not true; no spaces are inserted. I have also clarified the |
25 |
|
wording for the --colour (or --color) option. |
26 |
|
|
27 |
|
5. In pcregrep, when --colour was used with -o, the list of matching strings |
28 |
|
was not coloured; this is different to GNU grep, so I have changed it to be |
29 |
|
the same. |
30 |
|
|
31 |
|
6. When --colo(u)r was used in pcregrep, only the first matching substring in |
32 |
|
each matching line was coloured. Now it goes on to look for further matches |
33 |
|
of any of the test patterns, which is the same behaviour as GNU grep. |
34 |
|
|
35 |
|
7. A pattern that could match an empty string could cause pcregrep to loop; it |
36 |
|
doesn't make sense to accept an empty string match in pcregrep, so I have |
37 |
|
locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this |
38 |
|
seems to be how GNU grep behaves. |
39 |
|
|
40 |
|
8. The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at |
41 |
|
start or after a newline", because the conditional assertion was not being |
42 |
|
correctly handled. The rule now is that both the assertion and what follows |
43 |
|
in the first alternative must satisfy the test. |
44 |
|
|
45 |
|
9. If auto-callout was enabled in a pattern with a conditional group whose |
46 |
|
condition was an assertion, PCRE could crash during matching, both with |
47 |
|
pcre_exec() and pcre_dfa_exec(). |
48 |
|
|
49 |
|
10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was |
50 |
|
used for matching. |
51 |
|
|
52 |
|
11. Unicode property support in character classes was not working for |
53 |
|
characters (bytes) greater than 127 when not in UTF-8 mode. |
54 |
|
|
55 |
|
12. Added the -M command line option to pcretest. |
56 |
|
|
57 |
|
14. Added the non-standard REG_NOTEMPTY option to the POSIX interface. |
58 |
|
|
59 |
|
15. Added the PCRE_NO_START_OPTIMIZE match-time option. |
60 |
|
|
61 |
|
16. Added comments and documentation about mis-use of no_arg in the C++ |
62 |
|
wrapper. |
63 |
|
|
64 |
|
17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch |
65 |
|
from Martin Jerabek that uses macro names for all relevant character and |
66 |
|
string constants. |
67 |
|
|
68 |
|
18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and |
69 |
|
SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without |
70 |
|
SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of |
71 |
|
these, but not everybody uses configure. |
72 |
|
|
73 |
|
19. A conditional group that had only one branch was not being correctly |
74 |
|
recognized as an item that could match an empty string. This meant that an |
75 |
|
enclosing group might also not be so recognized, causing infinite looping |
76 |
|
(and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$ |
77 |
|
with the subject "ab", where knowledge that the repeated group can match |
78 |
|
nothing is needed in order to break the loop. |
79 |
|
|
80 |
|
20. If a pattern that was compiled with callouts was matched using pcre_dfa_ |
81 |
|
exec(), but without supplying a callout function, matching went wrong. |
82 |
|
|
83 |
|
|
84 |
|
Version 7.8 05-Sep-08 |
85 |
--------------------- |
--------------------- |
86 |
|
|
87 |
1. Replaced UCP searching code with optimized version as implemented for Ad |
1. Replaced UCP searching code with optimized version as implemented for Ad |
111 |
|
|
112 |
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 |
113 |
pointers, in case they are 64-bit values. |
pointers, in case they are 64-bit values. |
114 |
|
|
115 |
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 |
116 |
test 2 if it fails. |
test 2 if it fails. |
117 |
|
|
118 |
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, |
119 |
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 |
120 |
allow users of MSVC to set it if necessary. |
allow users of MSVC to set it if necessary. |
121 |
|
|
122 |
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 |
123 |
the convenience functions in the pcre_get.c source file. |
the convenience functions in the pcre_get.c source file. |
124 |
|
|
125 |
|
11. An option change at the start of a pattern that had top-level alternatives |
126 |
|
could cause overwriting and/or a crash. This command provoked a crash in |
127 |
|
some environments: |
128 |
|
|
129 |
|
printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest |
130 |
|
|
131 |
|
This potential security problem was recorded as CVE-2008-2371. |
132 |
|
|
133 |
|
12. For a pattern where the match had to start at the beginning or immediately |
134 |
|
after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and |
135 |
|
pcre_dfa_exec() could read past the end of the passed subject if there was |
136 |
|
no match. To help with detecting such bugs (e.g. with valgrind), I modified |
137 |
|
pcretest so that it places the subject at the end of its malloc-ed buffer. |
138 |
|
|
139 |
|
13. The change to pcretest in 12 above threw up a couple more cases when pcre_ |
140 |
|
exec() might read past the end of the data buffer in UTF-8 mode. |
141 |
|
|
142 |
|
14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and |
143 |
|
the data contained the byte 0x85 as part of a UTF-8 character within its |
144 |
|
first line. This applied both to normal and DFA matching. |
145 |
|
|
146 |
|
15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example, |
147 |
|
/^[^d]*?$/8 failed to match "abc". |
148 |
|
|
149 |
|
16. Added a missing copyright notice to pcrecpp_internal.h. |
150 |
|
|
151 |
|
17. Make it more clear in the documentation that values returned from |
152 |
|
pcre_exec() in ovector are byte offsets, not character counts. |
153 |
|
|
154 |
|
18. Tidied a few places to stop certain compilers from issuing warnings. |
155 |
|
|
156 |
|
19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as |
157 |
|
supplied by Stefan Weber. I made a further small update for 7.8 because |
158 |
|
there is a change of source arrangements: the pcre_searchfuncs.c module is |
159 |
|
replaced by pcre_ucd.c. |
160 |
|
|
161 |
|
|
162 |
Version 7.7 07-May-08 |
Version 7.7 07-May-08 |
163 |
--------------------- |
--------------------- |