public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/10325] destructor of FILE handles created by fopencookie() not called on exit.
Date: Fri, 30 Oct 2009 07:19:00 -0000	[thread overview]
Message-ID: <20091030071849.11879.qmail@sourceware.org> (raw)
In-Reply-To: <20090624124605.10325.rixed@happyleptic.org>


------- Additional Comments From drepper at redhat dot com  2009-10-30 07:18 -------
This wasn't in the design.  The system doesn't know anything about the actual
implementation.  Perhaps some of the resources needed for the cookie functions
is already gone.  It's not safe to try to close the FILE.  Aside, there might be
code out there which depends on the current behavior.  It'd different if from
day one this requirement would have existed.

And whatever ISO C says doesn't apply here because cookie streams are not in ISO C.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX


http://sourceware.org/bugzilla/show_bug.cgi?id=10325

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2009-10-30  7:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 12:46 [Bug libc/10325] New: " rixed at happyleptic dot org
2009-10-30  7:19 ` drepper at redhat dot com [this message]
     [not found] <bug-10325-131@http.sourceware.org/bugzilla/>
2012-08-21 21:52 ` [Bug libc/10325] " mvr at google dot com
2014-06-17  5:56 ` fweimer at redhat 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=20091030071849.11879.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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).