public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lizhijian at cn dot fujitsu.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15589] New: freopen would close oldfd even though oldfd is same as newfd
Date: Thu, 06 Jun 2013 05:50:00 -0000	[thread overview]
Message-ID: <bug-15589-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 15589
           Summary: freopen would close oldfd even though oldfd is same as
                    newfd
           Product: glibc
           Version: 2.16
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: lizhijian at cn dot fujitsu.com
                CC: drepper.fsp at gmail dot com

after glibc commit:
http://repo.or.cz/w/glibc.git/commit/94b7cc3711b0b74c1d3ae18b9a2e019e51a8e0bf

It look like cause some problems,
freopen would close oldfd even though oldfd is same as newfd.

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


             reply	other threads:[~2013-06-06  5:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  5:50 lizhijian at cn dot fujitsu.com [this message]
2013-06-06  5:53 ` [Bug libc/15589] " lizhijian at cn dot fujitsu.com
2013-06-06  5:56 ` lizhijian at cn dot fujitsu.com
2013-06-14  4:03 ` lizhijian at cn dot fujitsu.com
2014-06-13 15:10 ` fweimer at redhat dot com
2015-08-22 20:36 ` [Bug stdio/15589] " jsm28 at gcc dot gnu.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-15589-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).