public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alexcastan at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/37785] New: printf + sleep = problems with output buffer Date: Thu, 09 Oct 2008 18:34:00 -0000 [thread overview] Message-ID: <bug-37785-16813@http.gcc.gnu.org/bugzilla/> (raw) PLATFORM PC i386 + GNU/Linux Ubuntu Hardy 8.04 + GCC 4.2.3 Compiling and Linking options: none. Excuse my poor English. (By the way, what is "Host triplet", "Target triplet", "Build triplet"?) BUG: "printf" really prints at terminal when finds '\n' character. So if I have a simple "printf" iteration without '\n' like this ... int n; for (n=10; n>=0; n--) { printf("%d ", n); sleep(1); }; ... it doesn't works like expected. It just waits 10 seconds without printing anything. After that prints whole line. Another related problem with printf without '\n' and printf buffer using fork, but I don't know if it is problem with printf or fork: int n, pid; for (n=10; n>=0; n--) { printf("%d ", n); sleep(1); }; pid = fork(); if (pid == -1) printf("Error\n"); else if (pid == 0) printf("I'm the child\n"); else printf("I'm the parent\n"); it prints TWO times 10 9 8 7 6 5 4 3 2 1 0 It is not that executes two times, but if the fork send again the buffer to the screen. -- Summary: printf + sleep = problems with output buffer Product: gcc Version: 4.2.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: alexcastan at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37785
next reply other threads:[~2008-10-09 18:34 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-09 18:34 alexcastan at gmail dot com [this message] 2008-10-09 18:37 ` [Bug c/37785] printf without '\n' " paolo dot carlini at oracle dot com 2008-10-09 18:47 ` pinskia at gcc dot gnu dot org 2008-10-09 20:25 ` alexcastan at gmail 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=bug-37785-16813@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).