public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/814] perror(3) generates an error
Date: Sat, 02 Apr 2005 17:07:00 -0000	[thread overview]
Message-ID: <20050402170700.15365.qmail@sourceware.org> (raw)
In-Reply-To: <20050401163034.814.steelman@post.pl>


------- Additional Comments From jakub at redhat dot com  2005-04-02 17:06 -------
Hm, why?  It will only make glibc slower and bigger.
errno value is undefined after most calls, it has defined value only when certain
functions signal an error (usually returning -1 or NULL) and only very few
functions have errno defined in all cases or unmodified.
perror is not one of them.  Even if perror preserved errno value, errno is
still undefined after write or close that don't return -1.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |INVALID


http://sources.redhat.com/bugzilla/show_bug.cgi?id=814

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


  parent reply	other threads:[~2005-04-02 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01 16:31 [Bug libc/814] New: " steelman at post dot pl
2005-04-01 17:38 ` [Bug libc/814] " schwab at suse dot de
2005-04-01 19:42 ` schwab at suse dot de
2005-04-01 19:43 ` schwab at suse dot de
2005-04-02 13:11 ` gotom at debian dot or dot jp
2005-04-02 13:12 ` gotom at debian dot or dot jp
2005-04-02 17:07 ` jakub at redhat dot com [this message]
     [not found] <bug-814-131@http.sourceware.org/bugzilla/>
2014-12-11 19:02 ` wjmelements 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=20050402170700.15365.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --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).