public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug regex/17356] New: regex assertion violation with triple backreferences Date: Sun, 07 Sep 2014 23:47:00 -0000 [thread overview] Message-ID: <bug-17356-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17356 Bug ID: 17356 Summary: regex assertion violation with triple backreferences Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: regex Assignee: unassigned at sourceware dot org Reporter: eggert at gnu dot org CC: drepper.fsp at gmail dot com Flags: security+ Created attachment 7772 --> https://sourceware.org/bugzilla/attachment.cgi?id=7772&action=edit Test for triple backreference regex bug The attached program, which is a strictly conforming use of the POSIX regular expression matcher, has undefined behavior with glibc. On Fedora 20 x86-64 it simply dumps core; on Ubuntu 14.04 x86-64 it outputs "regexec.c:1386: pop_fail_stack: Assertion `num >= 0' failed" and then dumps core. It works fine on Solaris and AIX. I expect that this bug has been in all glibc versions since Isamu Hasegawa's circa-2002 rewrite of the regex code, and that the bug is in glibc 2.20 too, though I haven't tested this. Fixing this bug will not be trivial, I'm afraid. I have not succeeded in tracking down Mr. Hasegawa. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-09-07 23:47 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-07 23:47 eggert at gnu dot org [this message] 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 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@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: 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).