| 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, |
| 39 |
|
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. |
| 41 |
|
|
| 42 |
|
10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from |
| 43 |
|
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 |
| 46 |
|
could cause overwriting and/or a crash. This command provoked a crash in |
| 47 |
|
some environments: |
| 48 |
|
|
| 49 |
|
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. |
| 52 |
|
|
| 53 |
|
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 |
| 55 |
|
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 |
| 57 |
|
pcretest so that it places the subject at the end of its malloc-ed buffer. |
| 58 |
|
|
| 59 |
|
|
| 60 |
Version 7.7 07-May-08 |
Version 7.7 07-May-08 |
Parent Directory
| 
Revision Log
| 
Patch