| 95 |
\w+ when the character tables indicated that \x{c4} was a word character. |
\w+ when the character tables indicated that \x{c4} was a word character. |
| 96 |
There were several related cases, all because the tests for doing a table |
There were several related cases, all because the tests for doing a table |
| 97 |
lookup were testing for characters less than 127 instead of 255. |
lookup were testing for characters less than 127 instead of 255. |
| 98 |
|
|
| 99 |
|
27. If a pattern contains capturing parentheses that are not used in a match, |
| 100 |
|
their slots in the ovector are set to -1. For those that are higher than |
| 101 |
|
any matched groups, this happens at the end of processing. In the case when |
| 102 |
|
there were back references that the ovector was too small to contain |
| 103 |
|
(causing temporary malloc'd memory to be used during matching), and the |
| 104 |
|
highest capturing number was not used, memory off the end of the ovector |
| 105 |
|
was incorrectly being set to -1. (It was using the size of the temporary |
| 106 |
|
memory instead of the true size.) |
| 107 |
|
|
| 108 |
|
28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an |
| 109 |
|
ovector size, it uses memory at the end of the block that it has got. |
| 110 |
|
|
| 111 |
|
|
| 112 |
Version 8.30 04-February-2012 |
Version 8.30 04-February-2012 |
Parent Directory
| 
Revision Log
| 
Patch