public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/14716] memmem crash Date: Sun, 14 Oct 2012 06:22:00 -0000 [thread overview] Message-ID: <bug-14716-131-sBNTa1ujdg@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14716-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14716 Jan Kratochvil <jan.kratochvil at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #6683|0 |1 is obsolete| | Attachment #6684|0 |1 is obsolete| | --- Comment #5 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2012-10-14 06:21:54 UTC --- Created attachment 6685 --> http://sourceware.org/bugzilla/attachment.cgi?id=6685 .c crash reproducer. -- 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 prev parent reply other threads:[~2012-10-14 6:22 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-13 18:47 [Bug libc/14716] New: " jan.kratochvil at redhat dot com 2012-10-13 18:58 ` [Bug libc/14716] " jan.kratochvil at redhat dot com 2012-10-13 19:06 ` jan.kratochvil at redhat dot com 2012-10-13 21:08 ` hjl.tools at gmail dot com 2012-10-13 21:47 ` hjl.tools at gmail dot com 2012-10-14 6:22 ` jan.kratochvil at redhat dot com 2012-10-14 6:22 ` jan.kratochvil at redhat dot com [this message] 2012-10-14 7:14 ` maxim.kuvyrkov at gmail dot com 2012-10-14 23:36 ` hjl.tools at gmail dot com 2012-10-16 0:25 ` maxim.kuvyrkov at gmail dot com 2014-06-14 12:55 ` 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-14716-131-sBNTa1ujdg@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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).