public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "infor at rudhar dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug stdio/28099] fcloseall doesn't close anything Date: Wed, 01 Sep 2021 08:02:21 +0000 [thread overview] Message-ID: <bug-28099-131-kgnb8dOjdG@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28099-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28099 Ruud Harmsen <infor at rudhar dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |infor at rudhar dot com --- Comment #3 from Ruud Harmsen <infor at rudhar dot com> --- Or perhaps the streams and file descriptors ARE closed, but fputs error checking isn't working properly? Cf. https://sourceware.org/bugzilla/show_bug.cgi?id=20632, where I found the first fputws to a closed stderr (that is, a close(2) was done) does return -1, as it should, but subsequent calls of fputws return 1 as if they are OK. But they aren't, no text appears. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-01 8:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-18 16:10 [Bug stdio/28099] New: " crrodriguez at opensuse dot org 2021-07-18 16:25 ` [Bug stdio/28099] " schwab@linux-m68k.org 2021-07-18 16:54 ` crrodriguez at opensuse dot org 2021-09-01 8:02 ` infor at rudhar dot com [this message] 2021-09-01 14:27 ` crrodriguez at opensuse dot org 2021-09-01 15:27 ` crrodriguez at opensuse 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-28099-131-kgnb8dOjdG@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: 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).