public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/13762] New: re_search etc. should return -2 on memory exhaustion Date: Mon, 27 Feb 2012 07:07:00 -0000 [thread overview] Message-ID: <bug-13762-132@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13762 Bug #: 13762 Summary: re_search etc. should return -2 on memory exhaustion Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: regex AssignedTo: unassigned@sourceware.org ReportedBy: eggert@gnu.org CC: drepper.fsp@gmail.com Classification: Unclassified Created attachment 6249 --> http://sourceware.org/bugzilla/attachment.cgi?id=6249 Fix re_search to return -2 on memory exhaustion. I ran into this problem when testing GNU grep, which uses the re_search function. re_search is supposed to return -2 on internal error, but it returns -1 in some cases when memory is exhausted. -1 simply means "no match", so this causes grep to falsely claim "no match" when it should have reported an error due to memory exhaustion. I'm attaching a patch against the current git master. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-02-27 7:07 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-27 7:07 eggert at gnu dot org [this message] 2013-10-12 20:53 ` [Bug regex/13762] " neleai at seznam dot cz 2014-06-26 14:22 ` fweimer 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=bug-13762-132@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --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).