[Bug libc/447] No useful thread safe error to string function

["olaf at cbk dot poznan dot pl" <sourceware-bugzilla at sources dot redhat dot com>]

------- Additional Comments From olaf at cbk dot poznan dot pl  2004-10-14 15:11 -------
1. Man page from Linux:
SVID 3, POSIX, BSD 4.3, ISO/IEC 9899:1990 (C89).
       strerror_r() with prototype as given above is specified by  SUSv3,  and
       was  in  use  under Digital Unix and HP Unix. An incompatible function,
       with prototype
 
       char *strerror_r(int errnum, char *buf, size_t n);
 
       is a GNU extension used by glibc (since 2.0), and must be  regarded  as
       obsolete  in view of SUSv3.  

2. But I never know if I should access the error description from the supplied
buffer or from the pointer the function returns.
It should always put error description in the supplied buffer or always give the
error description as result.

3. OK. It solves my problem. Anyway why it behaves inconsistent as I described
in point 2?

Thank you

-- 


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

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