public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tee at sgi dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/2013] memccpy() gives inconsistent results on mmapped files Date: Thu, 23 Feb 2006 19:51:00 -0000 [thread overview] Message-ID: <20060223195112.16263.qmail@sourceware.org> (raw) In-Reply-To: <20051209165212.2013.tee@sgi.com> ------- Additional Comments From tee at sgi dot com 2006-02-23 19:51 ------- The patch from Comment #3 does fix the problem for us. -- http://sourceware.org/bugzilla/show_bug.cgi?id=2013 ------- 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:[~2006-02-23 19:51 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-12-09 16:52 [Bug libc/2013] New: " tee at sgi dot com 2005-12-29 16:51 ` [Bug libc/2013] " hjl at lucon dot org 2005-12-29 16:51 ` hjl at lucon dot org 2006-01-02 21:31 ` tee at sgi dot com 2006-01-05 22:55 ` hjl at lucon dot org 2006-02-23 19:51 ` tee at sgi dot com [this message] 2006-03-02 4:49 ` cvs-commit at gcc dot gnu dot org 2006-03-02 4:50 ` roland at gnu dot org 2006-03-02 4:50 ` roland at gnu dot org 2007-02-18 4:47 ` drepper 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=20060223195112.16263.qmail@sourceware.org \ --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).