public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "vprodan dot hosting at artstyle dot ru" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/558] New: regcomp and regexec bug
Date: Thu, 18 Nov 2004 02:06:00 -0000	[thread overview]
Message-ID: <20041118020600.558.vprodan.hosting@artstyle.ru> (raw)

Some regular expressions make regcomp to eat CPU and memory.
Try run date |egrep '.{1,2048}' and enjoy the result if you're patient enough.

Test case:
#include <stdio.h>
#include <regex.h>

int main(void) {
    char s[] = "/.{1,2048}.{1,2048}.{1,2048}.{1,2048}.{1,2048}/";
    regex_t reg;                      
    int res;    
    fprintf(stderr, "starting\n");
    res = regcomp(&reg, s, REG_EXTENDED);
    fprintf(stderr, "regcomp(&reg, '%s', REG_EXTENDED) = %d\n", s, res);
}

This bug appeared in between 2.2.5 and 2.3:

> date: 2002/02/27 19:00:56;  author: drepper;  state: Exp;  lines: +7 -8399
> Check in complete rewrite.

-- 
           Summary: regcomp and regexec bug
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: regex
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: vprodan dot hosting at artstyle dot ru
                CC: glibc-bugs-regex at sources dot redhat dot com,glibc-
                    bugs at sources dot redhat dot com,vprodan dot hosting
                    at artstyle dot ru
 GCC build triplet: i686-pc-linux-gnu


http://sources.redhat.com/bugzilla/show_bug.cgi?id=558

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


             reply	other threads:[~2004-11-18  2:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18  2:06 vprodan dot hosting at artstyle dot ru [this message]
2004-11-22  9:15 ` [Bug regex/558] " bonzini at gnu dot org
2004-11-23 12:31 ` bonzini at gnu dot org
2004-11-23 12:32 ` bonzini at gnu dot org
2004-12-10 16:56 ` bonzini at gnu dot org
2005-01-27 19:08 ` drepper at redhat dot com

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=20041118020600.558.vprodan.hosting@artstyle.ru \
    --to=sourceware-bugzilla@sources.redhat.com \
    --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).