public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/11053] Wrong results with backreferences
Date: Fri, 09 Apr 2010 17:46:00 -0000	[thread overview]
Message-ID: <20100409174604.25786.qmail@sourceware.org> (raw)
In-Reply-To: <20091204193539.11053.bonzini@gnu.org>


------- Additional Comments From bonzini at gnu dot org  2010-04-09 17:46 -------
Minimized testcases (same regex):

$ echo 8 | grep -E -e "$regex"
8          # >>> okay
$ echo 87 | grep -E -e "$regex"
Segmentation fault

$ echo 88 | grep -E -e "$regex"
88         # >>> okay
$ echo 887 | grep -E -e "$regex"
Segmentation fault

Also, everything I tried to feed that is of length 9 or higher and should not
match, gives either a false positive or a segfault:

$ echo 987654321 | grep -E -e "$regex"
887654321
$ echo 484635532 | grep -E -e "$regex"
484635532
$ echo 0123454321 | grep -E -e "$regex"
Segmentation fault
$ echo 0000123454321 | grep -E -e "$regex"
Segmentation fault


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Segfault on invalid         |Wrong results with
                   |backreference               |backreferences


http://sourceware.org/bugzilla/show_bug.cgi?id=11053

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2010-04-09 17:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 19:36 [Bug regex/11053] New: Segfault on invalid backreference bonzini at gnu dot org
2010-04-05 19:39 ` [Bug regex/11053] " drepper at redhat dot com
2010-04-09 17:46 ` bonzini at gnu dot org [this message]
     [not found] <bug-11053-132@http.sourceware.org/bugzilla/>
2014-06-30 20:34 ` [Bug regex/11053] Wrong results with backreferences fweimer at redhat dot com
2014-06-30 20:34 ` fweimer at redhat dot com
2014-09-23  2:28 ` eggert at gnu dot org
2014-09-23  7:55 ` fweimer at redhat dot com
2017-01-17 21:24 ` eggert at gnu dot org
2021-02-06  7:37 ` eggert at cs dot ucla.edu
2021-03-04  7:33 ` mliska at suse dot cz
2021-08-16  0:55 ` sam at gentoo dot org
2021-08-16  7:08 ` simon_a_taylor at yahoo dot com
2021-08-25  5:10 ` michael.hudson at canonical dot com
2021-08-25 18:09 ` eggert at cs dot ucla.edu
2021-09-21 15:00 ` cvs-commit at gcc dot gnu.org
2022-09-05 23:06 ` vincent-srcware at vinc17 dot net
2022-09-06  0:37 ` eggert at cs dot ucla.edu
2022-09-06  2:47 ` vincent-srcware at vinc17 dot net
2022-09-06  2:59 ` vincent-srcware at vinc17 dot net
2022-09-06 18:47 ` eggert at cs dot ucla.edu
2022-09-06 22:56 ` vincent-srcware at vinc17 dot net
2022-09-06 23:41 ` eggert at cs dot ucla.edu
2022-09-07  0:17 ` vincent-srcware at vinc17 dot net
2022-09-07  4:31 ` eggert at cs dot ucla.edu
2022-09-07 10:31 ` vincent-srcware at vinc17 dot net
2022-09-07 20:57 ` eggert at cs dot ucla.edu
2022-09-08 11:44 ` vincent-srcware at vinc17 dot net
2022-11-11 16:29 ` cvs-commit at gcc dot gnu.org

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=20100409174604.25786.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs-regex@sources.redhat.com \
    /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).