From 8dc7206187ef9e9486fb5f102b85400ae9795dd1 Mon Sep 17 00:00:00 2001 From: ph10 Date: Mon, 19 Feb 2018 16:35:05 +0000 Subject: Fix POSIX API bug when REG_STARTEND is used with a non-zero starting offset and there are unset groups within the matching group list. git-svn-id: svn://vcs.exim.org/pcre/code/trunk@1724 2f5784b3-3f2a-0410-8824-cb99058d5e15 --- ChangeLog | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'ChangeLog') diff --git a/ChangeLog b/ChangeLog index dca7743..108d739 100644 --- a/ChangeLog +++ b/ChangeLog @@ -4,7 +4,7 @@ ChangeLog for PCRE Note that the PCRE 8.xx series (PCRE1) is now in a bugfix-only state. All development is happening in the PCRE2 10.xx series. -Version 8.42 xx-xxx-2017 +Version 8.42 xx-xxx-2018 ------------------------ 1. Fixed a MIPS issue in the JIT compiler reported by Joshua Kinard. @@ -39,6 +39,11 @@ as the first character of a match. 8. Fix out-of-bounds read for partial matching of /./ against an empty string when the newline type is CRLF. +9. When matching using the the REG_STARTEND feature of the POSIX API with a +non-zero starting offset, unset capturing groups with lower numbers than a +group that did capture something were not being correctly returned as "unset" +(that is, with offset values of -1). + Version 8.41 05-July-2017 ------------------------- -- cgit v1.2.1