From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: fflush(NULL) clobbers input streams
Date: Tue, 18 Jul 2017 22:41:00 -0000 [thread overview]
Message-ID: <ec913336-7310-7e0c-6f60-3bf3c90313df@cornell.edu> (raw)
In-Reply-To: <87fudtlfen.fsf@Rainer.invalid>
On 7/18/2017 3:21 PM, Achim Gratz wrote:
> Corinna Vinschen writes:
>> Oh, and a plain C testcase, of course...
>
> Call that fflush.c:
>
> --8<---------------cut here---------------start------------->8---
> #include <stdio.h>
> int
> main(int argc, char **argv)
> {
> char buf[1024];
> int i;
> char *bp = buf;
> while (1) {
> while ((i = getc(stdin)) != -1
> && (*bp++ = i) != '\n'
> && bp < &buf[1024])
> /* DO NOTHING */ ;
> *bp = '\0';
> fprintf(stdout, "%s", buf);
> fflush(NULL);
> if (i == -1)
> return 0;
> bp = buf;
> }
> }
> --8<---------------cut here---------------end--------------->8---
>
> Then run:
>
> gcc fflush.c -o fflush
> cat fflush.c | ./fflush 2>/dev/null > fflush.out
> diff fflush.c fflush.out
>
> If things are working, fflush.c and fflush.out should be identical.
> Currently only the first line makes it into fflush.out on Cygwin.
I've checked that the 2017-03-08 snapshot is good and the 2017-03-10
snapshot is bad. I'll bisect further when I get a chance, but maybe
that's already enough to pin down the problem.
Ken
next prev parent reply other threads:[~2017-07-18 22:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 17:53 Achim Gratz
2017-07-18 9:55 ` Corinna Vinschen
2017-07-18 10:51 ` Corinna Vinschen
2017-07-18 19:21 ` Achim Gratz
2017-07-18 22:41 ` Ken Brown [this message]
2017-07-19 2:16 ` Ken Brown
2017-07-19 8:46 ` Corinna Vinschen
2017-07-19 17:03 ` [GOLDSTAR] " Corinna Vinschen
2017-07-19 17:20 ` Ken Brown
2017-07-19 20:40 ` Andrew Schulman
2017-07-19 17:11 ` Achim Gratz
2017-07-19 17:03 ` Achim Gratz
2017-07-18 18:33 ` Achim Gratz
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=ec913336-7310-7e0c-6f60-3bf3c90313df@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.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: 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).