public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mtk.manpages at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug stdio/13151] fmemopen streams fail to read eof Date: Fri, 27 Apr 2012 20:31:00 -0000 [thread overview] Message-ID: <bug-13151-131-2NKnl3NkAC@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13151-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13151 --- Comment #2 from Michael Kerrisk <mtk.manpages at gmail dot com> 2012-04-27 20:31:07 UTC --- Rich, I spoke a little soon. I see that that the fmemopen() POSIX spec has a definition of "a+" that is more consistent with your explanation. Anyway, we both agree there's a problem here ;-). -- 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-04-27 20:31 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-05 2:24 [Bug libc/13151] New: " bugdal at aerifal dot cx 2012-02-21 2:30 ` [Bug stdio/13151] " jsm28 at gcc dot gnu.org 2012-04-27 20:16 ` mtk.manpages at gmail dot com 2012-04-27 20:31 ` mtk.manpages at gmail dot com [this message] 2012-04-28 2:21 ` mtk.manpages at gmail dot com 2012-04-28 3:28 ` mtk.manpages at gmail dot com 2012-04-28 4:26 ` mtk.manpages at gmail dot com 2012-12-19 10:39 ` schwab@linux-m68k.org 2013-05-20 15:24 ` ondra at iuuk dot mff.cuni.cz 2014-02-16 18:29 ` jackie.rosen at hushmail dot com 2014-05-28 19:40 ` schwab at sourceware dot org 2014-06-27 12:10 ` fweimer at redhat dot com 2015-07-08 15:16 ` adhemerval.zanella at linaro dot org
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-13151-131-2NKnl3NkAC@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).