public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eblake at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/12799] fflush violates POSIX on seekable input streams
Date: Tue, 14 Apr 2020 00:24:27 +0000 [thread overview]
Message-ID: <bug-12799-131-g50STus7ZR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12799-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=12799
--- Comment #2 from Eric Blake <eblake at redhat dot com> ---
(In reply to Eric Blake from comment #1)
> The removal of libio.h is making this bug all the more important to fix, so
> that gnulib can quit mucking around in glibc internals:
> https://lists.gnu.org/archive/html/bug-gnulib/2018-03/msg00002.html
>
> Is there a chance that it can be fixed for 2.28?
Still broken in 2020. Similarly, fflush(NULL) should have this effect on all
seekable input streams.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-04-14 0:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 17:14 [Bug libc/12799] New: " eblake at redhat dot com
2012-02-21 2:23 ` [Bug stdio/12799] " jsm28 at gcc dot gnu.org
2012-10-29 14:00 ` siddhesh at redhat dot com
2012-12-11 11:48 ` hannes at stressinduktion dot org
2012-12-19 10:48 ` schwab@linux-m68k.org
2014-06-27 13:17 ` fweimer at redhat dot com
2020-04-14 0:18 ` eblake at redhat dot com
2020-04-14 0:24 ` eblake at redhat dot com [this message]
2020-04-14 15:59 ` rjones at redhat dot com
2020-08-02 23:05 ` chimpatheist at gmail dot com
2020-08-03 18:34 ` chimpatheist at gmail dot com
2020-08-03 20:03 ` chimpatheist at gmail dot com
2021-01-22 2:47 ` dancol at dancol 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-12799-131-g50STus7ZR@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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: link
Be 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).