public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "jwakely.gcc at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sourceware.org Subject: [Bug regex/20095] parse_dup_op duplicates the tree exponentially when using repeated + Date: Thu, 24 Aug 2023 15:14:35 +0000 [thread overview] Message-ID: <bug-20095-132-x5U0QQEZX0@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-20095-132@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=20095 Jonathan Wakely <jwakely.gcc at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwakely.gcc at gmail dot com --- Comment #3 from Jonathan Wakely <jwakely.gcc at gmail dot com> --- This behaviour can rapidly exhaust memory (Bug 25814, Bug 28864, Bug 20095 , Bug 29642), which seems unhelpful when ".++" is not even a valid regex. POSIX says it's undefined: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_04_06 Why doesn't regcomp just fail to compile it with REG_BADRPT? Similarly for ".**" etc. GNU grep seems to have tests for these that expect BADRPT: https://git.savannah.gnu.org/cgit/grep.git/tree/tests/tests?h=v3.11#n234 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-24 15:14 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-05-14 1:08 [Bug regex/20095] New: " dualbus at gmail dot com 2020-04-15 15:53 ` [Bug regex/20095] " dpmendenhall at gmail dot com 2023-08-24 15:14 ` jwakely.gcc at gmail dot com [this message] 2023-08-24 20:21 ` adhemerval.zanella at linaro dot org 2023-08-24 20:28 ` jwakely.gcc at gmail dot com 2023-08-24 22:43 ` sh200105 at mail dot ru
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-20095-132-x5U0QQEZX0@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs-regex@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).