public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/611] New: regex with a long character sequence requires huge stack space Date: Fri, 17 Dec 2004 08:34:00 -0000 [thread overview] Message-ID: <20041217083412.611.bonzini@gnu.org> (raw) The parse tree produced by concat nodes is extremely unbalanced. With an 8 MB stack, perl -e "print 's/' . ('a' x 300000) . '//'" > huge sed -f huge segfaults in calc_first. Of course with a lower stack size it takes much shorter regexes to trigger the bug, and anyway this is not nice behavior (ok, regex is a memory hog but at least it usually gives REG_ESPACE). With a 512 KB stack, even compiling a{32767} segfaults. -- Summary: regex with a long character sequence requires huge stack space Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: regex AssignedTo: bonzini at gnu dot org ReportedBy: bonzini at gnu dot org CC: glibc-bugs-regex at sources dot redhat dot com,glibc- bugs at sources dot redhat dot com http://sources.redhat.com/bugzilla/show_bug.cgi?id=611 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2004-12-17 8:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-17 8:34 bonzini at gnu dot org [this message] 2004-12-17 8:38 ` [Bug regex/611] " bonzini at gnu dot org 2004-12-20 10:22 ` bonzini at gnu dot org 2004-12-27 9:57 ` bonzini at gnu dot org 2004-12-27 15:11 ` bonzini at gnu dot org 2004-12-27 16:43 ` drepper at redhat dot com 2004-12-28 16:34 ` bonzini at gnu dot org 2005-01-26 22:28 ` drepper at redhat dot com 2005-01-26 22:43 ` 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=20041217083412.611.bonzini@gnu.org \ --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: linkBe 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).