public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crrodriguez at opensuse dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/28099] New: fcloseall doesn't close anything
Date: Sun, 18 Jul 2021 16:10:37 +0000	[thread overview]
Message-ID: <bug-28099-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=28099

            Bug ID: 28099
           Summary: fcloseall doesn't close anything
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: stdio
          Assignee: unassigned at sourceware dot org
          Reporter: crrodriguez at opensuse dot org
  Target Milestone: ---

Example to demonstrate de bug.

#define _GNU_SOURCE
#include <stdio.h>
#include <assert.h>

int main(void)
{
    FILE *fp, *fp1;
    fp = tmpfile();
    fp1 =tmpfile();
    assert ( fcloseall() == 0 );
    assert ( fputs("doh", fp) < 0 );
    assert ( fputs("bla", fp1) < 0 );
    return 0;
}

after the fcloseall() call all writes to the stream must fail..it really does
not appear to be doing anything.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-07-18 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 16:10 crrodriguez at opensuse dot org [this message]
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
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@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).