This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


------- Additional Comments From t-nishiie at soft dot fujitsu dot com  2007-09-26 00:41 -------
(In reply to comment #8)
I propose a following patch.

  *putenv()/setenv()/clearenv()/unsetenv() are not thread safe.

diff -ruN manual.orig/startup.texi manual/startup.texi
--- manual.orig/startup.texi	2006-11-11 06:10:22.000000000 +0900
+++ manual/startup.texi	2007-09-25 16:26:36.500000000 +0900
@@ -309,9 +309,9 @@
 
 The value of an environment variable can be accessed with the
 @code{getenv} function.  This is declared in the header file
-@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.
+@file{stdlib.h}. Modifications of enviroment variables are not
+allowed in Multi-threaded programs. The @code{getenv} function
+can be safely used in multi-threaded programs.
 @pindex stdlib.h
 
 @comment stdlib.h


-- 


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]