public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pasky at suse dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/11230] memchr overshoots on ia64 Date: Thu, 04 Feb 2010 00:21:00 -0000 [thread overview] Message-ID: <20100204002142.19322.qmail@sourceware.org> (raw) In-Reply-To: <20100128025427.11230.jrnieder@gmail.com> ------- Additional Comments From pasky at suse dot cz 2010-02-04 00:21 ------- I can confirm that I can _also_ reproduce the original issue at our SUSE machines and the issue persists even with the patch applied. I use this test file as an argument of the testcase program in bug description: 100644 346d4e61f111336a1443ef6b2e834aa5b1a7f91a 0 bozbar 100644 8e4020bb5a8d8c873b25de15933e75cc0fc275df 0 frotz 100644 dca6b92303befc93086aa025d90a5facd7eb2812 0 nitfol hjl, are you sure you haven't overlooked something when testing your patch? -- What |Removed |Added ---------------------------------------------------------------------------- CC| |pasky at suse dot cz Status|WAITING |NEW http://sourceware.org/bugzilla/show_bug.cgi?id=11230 ------- 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:[~2010-02-04 0:21 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-28 2:54 [Bug libc/11230] New: " jrnieder at gmail dot com 2010-01-28 3:52 ` [Bug libc/11230] " hjl dot tools at gmail dot com 2010-01-28 4:44 ` aurelien at aurel32 dot net 2010-01-28 6:37 ` hjl dot tools at gmail dot com 2010-01-28 6:37 ` hjl dot tools at gmail dot com 2010-01-28 8:32 ` aurelien at aurel32 dot net 2010-01-28 14:02 ` hjl dot tools at gmail dot com 2010-02-01 14:55 ` aurelien at aurel32 dot net 2010-02-01 16:50 ` hjl dot tools at gmail dot com 2010-02-01 17:08 ` aurelien at aurel32 dot net 2010-02-01 17:25 ` hjl dot tools at gmail dot com 2010-02-04 0:21 ` pasky at suse dot cz [this message] 2010-02-04 1:04 ` hjl dot tools at gmail dot com 2010-02-04 1:22 ` pasky at suse dot cz 2010-02-04 1:33 ` jrnieder at gmail dot com 2010-02-05 14:44 ` hjl dot tools at gmail dot com 2010-02-05 15:09 ` hjl dot tools at gmail dot com 2010-02-05 17:45 ` aurelien at aurel32 dot net 2010-02-05 20:27 ` pasky at suse dot cz 2010-02-06 10:21 ` drepper at redhat dot com 2010-02-08 19:48 ` jrnieder at gmail dot com [not found] <bug-11230-131@http.sourceware.org/bugzilla/> 2014-06-30 20:12 ` 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=20100204002142.19322.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).