luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-01-13 07:56:17 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add thread-safety warnings to the g_setenv() and g_unsetenv() docs

Browse Source 
https://bugzilla.gnome.org/show_bug.cgi?id=659326
This commit is contained in:
Dan Winship 2011-09-26 14:17:43 -04:00
parent 104ea17125
commit 51166d0127
1 changed files with 20 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
glib/gutils.c
View File

@ -1331,6 +1331,16 @@ _g_getenv_nomalloc (const gchar *variable,
* Note that on some systems, when variables are overwritten, the memory
* used for the previous variables and its value isn't reclaimed.
*
* <warning><para>
* Environment variable handling in UNIX is not thread-safe, and your
* program may crash if one thread calls g_setenv() while another
* thread is calling getenv(). (And note that many functions, such as
* gettext(), call getenv() internally.) This function is only safe to
* use at the very start of your program, before creating any other
* threads (or creating objects that create worker threads of their
* own).
* </para></warning>
*
* Returns: %FALSE if the environment variable couldn't be set.
*
* Since: 2.4
@ -1430,8 +1440,16 @@ extern char **environ;
*
* Note that on some systems, when variables are overwritten, the memory
* used for the previous variables and its value isn't reclaimed.
* Furthermore, this function can't be guaranteed to operate in a
* threadsafe way.
*
* <warning><para>
* Environment variable handling in UNIX is not thread-safe, and your
* program may crash if one thread calls g_unsetenv() while another
* thread is calling getenv(). (And note that many functions, such as
* gettext(), call getenv() internally.) This function is only safe to
* use at the very start of your program, before creating any other
* threads (or creating objects that create worker threads of their
* own).
* </para></warning>
*
* Since: 2.4
**/