This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/12204] glibc does has no POSIX compliant strerror_r function
- From: "bruno at clisp dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Thu, 11 Nov 2010 09:36:24 +0000
- Subject: [Bug libc/12204] glibc does has no POSIX compliant strerror_r function
- Auto-submitted: auto-generated
- References: <bug-12204-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12204
Bruno Haible <bruno at clisp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
--- Comment #5 from Bruno Haible <bruno at clisp dot org> 2010-11-11 09:36:21 UTC ---
> What do other OSes do? What's the behavior on Solaris?
Here are the results of the test program:
Solaris 10:
result: failure 22 Unknown error
result: failure 34 Unknown error
FreeBSD 6.4, OpenBSD 4.4:
result: failure 22 Unknown error: -2
result: failure 34 Pe
HP-UX 11.31:
result: failure 22 ______
result: failure 34 ______
AIX 6.1:
result: success Error -2 occurred.
result: success Pe
Tru64 5.1:
result: non-POSIX failure -1 22 Error -2 occurred.
result: success Pe
You can see that the major Unices use the POSIX compliant return value
convention. Tru64 is the only one to use the (-1,errno) return value.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.