From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3198 invoked by alias); 17 Dec 2004 08:34:38 -0000 Mailing-List: contact glibc-bugs-regex-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-regex-owner@sources.redhat.com Received: (qmail 2972 invoked by uid 48); 17 Dec 2004 08:34:16 -0000 Date: Fri, 17 Dec 2004 08:34:00 -0000 From: "bonzini at gnu dot org" To: glibc-bugs-regex@sources.redhat.com Message-ID: <20041217083412.611.bonzini@gnu.org> Reply-To: sourceware-bugzilla@sources.redhat.com Subject: [Bug regex/611] New: regex with a long character sequence requires huge stack space X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg00006.txt.bz2 List-Id: 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.