public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/13762] re_search etc. should return -2 on memory exhaustion
Date: Thu, 26 Jun 2014 14:22:00 -0000 [thread overview]
Message-ID: <bug-13762-132-Svp9H3dnAI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13762-132@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13762
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
CC| |fweimer at redhat dot com
Flags| |security-
--- Comment #2 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Ondrej Bilka from comment #1)
> Could you send this to libc-alpha?
Seconded.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2014-06-26 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 7:07 [Bug regex/13762] New: " eggert at gnu dot org
2013-10-12 20:53 ` [Bug regex/13762] " neleai at seznam dot cz
2014-06-26 14:22 ` fweimer at redhat dot com [this message]
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-Svp9H3dnAI@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: link
Be 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).