[Bug libc/4887] Wordexp() should be thread safe.

["t-nishiie at soft dot fujitsu dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From t-nishiie at soft dot fujitsu dot com  2007-08-29 06:45 -------
  There is a mistake in the manual of libc.
  Ulrich Drepper said:
---
setenv, putenv, clearenve, etc are not allowed in  threaded
 code without killing the rest.
---

  The manual of GNU libc has the following description.
---
http://www.gnu.org/software/libc/manual/html_mono/libc.html#Environment-Access
25.4.1 Environment Access
The value of an environment variable can be accessed with
the getenv function. This is declared in the header file
stdlib.h. All of the following functions can be safely used
 in multi-threaded programs. It is made sure that concurrent
 modifications to the environment do not lead to errors.

char * getenv (const char *name)
...
int putenv (char *string)
...
int setenv (const char *name, const char *value, int replace)
...
int unsetenv (const char *name)
---

  If description of a manual is right, you should make 
functions like setenv(), putenv(), and clearenv() into thread-safe.
  You should correct description of the manual, if that is not right.


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


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

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