This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug libc/814] perror(3) generates an error
- From: "jakub at redhat dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 2 Apr 2005 17:07:00 -0000
- Subject: [Bug libc/814] perror(3) generates an error
- References: <20050401163034.814.steelman@post.pl>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- 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.