public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/1291] size-overflow bugs in the regex code Date: Fri, 02 Sep 2005 22:52:00 -0000 [thread overview] Message-ID: <20050902225216.12712.qmail@sourceware.org> (raw) In-Reply-To: <20050902225143.1291.eggert@gnu.org> ------- Additional Comments From eggert at gnu dot org 2005-09-02 22:52 ------- Created an attachment (id=645) --> (http://sources.redhat.com/bugzilla/attachment.cgi?id=645&action=view) add some size-overflow checks to regex code -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=1291 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-09-02 22:52 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-09-02 22:51 [Bug regex/1291] New: " eggert at gnu dot org 2005-09-02 22:52 ` eggert at gnu dot org [this message] 2006-04-25 18:21 ` [Bug regex/1291] " drepper at redhat dot com 2006-04-26 7:16 ` bonzini at gnu dot org [not found] <bug-1291-132@http.sourceware.org/bugzilla/> 2012-02-06 14:09 ` aj at suse dot de 2012-12-01 16:47 ` aj at suse dot de
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=20050902225216.12712.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --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).