public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: benko@sztaki.hu To: gcc-gnats@gcc.gnu.org Subject: libstdc++/5799: streams reading from fifo Date: Fri, 01 Mar 2002 02:56:00 -0000 [thread overview] Message-ID: <20020301105010.23585.qmail@sources.redhat.com> (raw) >Number: 5799 >Category: libstdc++ >Synopsis: streams reading from fifo >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Mar 01 02:56:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Benko Pal >Release: 3.0.4 >Organization: >Environment: SuSE linux 7.3 i686 libc 2.2.4 >Description: Perhaps this is not a bug. if an ifstream reads from a named pipe, it sees the data only when the buffer is full or the pipe is closed, but not when the process writing to the pipe flushes. Using <stdio.h> there is no such problem. e.g. compiling and running #include <fstream> #include <iostream> int main() { std::ifstream in("/tmp/pipe"); char c; while (in >> c) std::cout << c; return 0; } while in an other shell I $ mkfifo /tmp/pipe $ cat > /tmp/pipe hello world ^D $ In the shell running the c++ program helloworld only appears after ^D. But compiling and running #include <stdio.h> int main() { FILE *in = fopen("/tmp/pipe", "r"); char c; while ((c = fgetc(in)) != EOF) putchar(c); return 0; } After entering hello and pushing enter, hello appears on the output of the program. Is a special initialisation of the ifstream needed perhaps? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-03-01 10:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-01 2:56 benko [this message] 2002-03-02 19:37 rodrigc 2002-03-03 23:16 Pal Benko 2002-04-05 11:54 bkoz
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=20020301105010.23585.qmail@sources.redhat.com \ --to=benko@sztaki.hu \ --cc=gcc-gnats@gcc.gnu.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: 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).