From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id DF24E3851A87; Tue,  6 Sep 2022 00:37:24 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DF24E3851A87
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1662424644;
	bh=PJ8n7T+SccfyrqwEKBre6knX8PzlwJLGJd0ur9Vo5+g=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=cDLR7AbEi/r3mVL/jekIpkuApPMyiedN1yyVInSQoEz6iIRsu99iG9CmqhY6Em7N/
	 +p8h/w4Ei/PAW32j/Nz1lZXoSFox6LKNwK08OBbJBr+8ksWtZUubwcrzpU6CNpdy4n
	 UqiuBfiwBwuMkdYhTO7F+hF/Mr0yXORI3mn3xPOY=
From: "eggert at cs dot ucla.edu" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/11053] Wrong results with backreferences
Date: Tue, 06 Sep 2022 00:37:24 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: regex
X-Bugzilla-Version: 2.11
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eggert at cs dot ucla.edu
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: eggert at cs dot ucla.edu
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security+
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-11053-132-OQ5TGGR2OW@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-11053-132@http.sourceware.org/bugzilla/>
References: <bug-11053-132@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <glibc-bugs-regex.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D11053

--- Comment #15 from eggert at cs dot ucla.edu ---
On 9/5/22 18:06, vincent-srcware at vinc17 dot net wrote:
>
> What is the status of this bug? The comment says that it is fixed, and I =
could
> check on an Ubuntu 22.04.1 LTS machine with libc6 2.35-0ubuntu3.1 that re=
gbug.c
> and rebug2.c no longer fail, but the result is still incorrect with the g=
rep
> example from Debian bug 884075:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D884075
>
> vinc17@gcc92:~$ echo 11111111111 | grep -E '^(11+)\1+$|^1?$' ; echo $?
> 11111111111
> 0
>
It looks like my comment=20
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D884075#27> was=20
incorrect, in that the two bugs are different bugs. glibc bug 11053 is=20
fixed, but Debian bug 884075 is not fixed. Perhaps a better match for=20
Debian bug 884075 is glibc bug 10844.

It's not an important bug. However, if you have time to fix it please=20
feel free to send in a fix.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=