public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug regex/17356] regex assertion violation with triple backreferences
Date: Thu, 08 Sep 2022 12:36:00 +0000 [thread overview]
Message-ID: <bug-17356-131-rFUtHQtUeR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17356-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17356
Vincent Lefèvre <vincent-srcware at vinc17 dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vincent-srcware at vinc17 dot net
--- Comment #4 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> ---
(In reply to eggert from comment #3)
> Apparently I was incorrect when I wrote that this was a duplicate of
> Bug#11053 as that other bug is fixed but this one is not.
More precisely, the assertion violation was Bug#11053, which is fixed in glibc
2.35, but the test now fails: it gives no matches, while there should be a
match, since the regexp matches the empty string.
Test with grep:
vinc17@gcc92:~$ echo 'a' | grep -E '(.{0,1})(.{0,1})\2\1'
a
vinc17@gcc92:~$ echo 'a' | grep -E '(.{0,1})(.{0,1})(.{0,1})\3\2\1'
vinc17@gcc92:~$
(with only 2 backreferences, this is OK, but not with 3).
The bug could be retitled.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-08 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 23:47 [Bug regex/17356] New: " eggert at gnu dot org
2014-09-23 0:11 ` [Bug regex/17356] " eggert at gnu dot org
2014-09-23 7:55 ` fweimer at redhat dot com
2022-09-07 4:30 ` eggert at cs dot ucla.edu
2022-09-08 12:36 ` vincent-srcware at vinc17 dot net [this message]
2022-09-08 17:03 ` [Bug regex/17356] regex misbehavior " eggert at cs dot ucla.edu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-17356-131-rFUtHQtUeR@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).