31 |
|
|
32 |
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 |
33 |
pointers, in case they are 64-bit values. |
pointers, in case they are 64-bit values. |
34 |
|
|
35 |
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 |
36 |
test 2 if it fails. |
test 2 if it fails. |
37 |
|
|
38 |
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, |
39 |
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 |
40 |
allow users of MSVC to set it if necessary. |
allow users of MSVC to set it if necessary. |
41 |
|
|
42 |
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 |
43 |
the convenience functions in the pcre_get.c source file. |
the convenience functions in the pcre_get.c source file. |
44 |
|
|
45 |
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 |
46 |
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 |
47 |
some environments: |
some environments: |
48 |
|
|
49 |
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 |
50 |
|
|
51 |
This potential security problem was recorded as CVE-2008-2371. |
This potential security problem was recorded as CVE-2008-2371. |
52 |
|
|
53 |
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 |
54 |
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 |
55 |
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 |
56 |
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 |
57 |
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. |
58 |
|
|
59 |
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_ |
60 |
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. |
61 |
|
|
62 |
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 |
63 |
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 |
64 |
first line. This applied both to normal and DFA matching. |
first line. This applied both to normal and DFA matching. |
65 |
|
|
66 |
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, |
67 |
/^[^d]*?$/8 failed to match "abc". |
/^[^d]*?$/8 failed to match "abc". |
68 |
|
|
69 |
16. Added a missing copyright notice to pcrecpp_internal.h. |
16. Added a missing copyright notice to pcrecpp_internal.h. |
70 |
|
|
71 |
17. Make it more clear in the documentation that values returned from |
17. Make it more clear in the documentation that values returned from |
72 |
pcre_exec() in ovector are byte offsets, not character counts. |
pcre_exec() in ovector are byte offsets, not character counts. |
73 |
|
|
74 |
18. Tidied a few places to stop certain compilers from issuing warnings. |
18. Tidied a few places to stop certain compilers from issuing warnings. |
75 |
|
|
76 |
|
|
77 |
Version 7.7 07-May-08 |
Version 7.7 07-May-08 |