🚀 go-pugleaf

admin@intergrafix.net writes:

> I've figured out HOW the problem occurs, i just dont know WHY it occurs, or
> WHY it should occur. Possibly a bug in the c libs or gcc??
> The HOW is: when you putenv() an array, and then modify the array afterwards,
> the environment automatically gets changed without executing another
> putenv()! This, to me, sounds ludicrous. Even setting the array below to
> static char doesn't help.

Believe it or not, this is correct behavior.  According to the Single
Unix Spec
(http://www.opengroup.org/onlinepubs/7908799/xsh/putenv.html):

# The putenv() function makes the value of the environment variable
# name equal to value by altering an existing variable or creating a
# new one. In either case, the string pointed to by string becomes
# part of the environment, so altering the string will change the
# environment. The space used by string is no longer used once a new
# string-defining name is passed to putenv().

If you want it to be independent, use strdup or something of the sort.

A note to this effect appears to have been added to the glibc
documentation recently; it may not be in your version.

-- 

Nate Eldredge
neldredge@hmc.edu