summaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2007-03-30 15:46:27 +0000
committerph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2007-03-30 15:46:27 +0000
commit28ed4f58e289c711ec3494e9f512da278506ece9 (patch)
tree06a6f1e644a86f80dd401ba66951259bc112c1b7 /ChangeLog
parent44b15daf3a13326a8e41a73b882fb3cbad686c66 (diff)
downloadpcre-28ed4f58e289c711ec3494e9f512da278506ece9.tar.gz
Fixed obscure bug when matching a null string in multiline mode with
newline=any. git-svn-id: svn://vcs.exim.org/pcre/code/trunk@141 2f5784b3-3f2a-0410-8824-cb99058d5e15
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog8
1 files changed, 8 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 639dba5..da3397e 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -126,6 +126,14 @@ Version 7.1 12-Mar-07
16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
in an attempt to make files that differ only in their line terminators
compare equal. This works on Linux.
+
+17. Under certain error circumstances pcregrep might try to free random memory
+ as it exited. This is now fixed, thanks to valgrind.
+
+19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
+ "abc\r\n\r\n", it found an unwanted second match after the second \r. This
+ was because its rules for how to advance for /g after matching an empty
+ string did not allow for this case. They now check for it specially.
Version 7.0 19-Dec-06