Fixed in: NetBSD 6 src lib/libc/stdlib/putenv.c 1.13 FreeBSD 7 putenv(3) says so OpenBSD 4.6 src lib/libc/stdlib/setenv.c 1.10 and is correct under current(?) MacOS as well The current wording implies that all of 4.4BSD's descenants also carry this bug (at least it did to me): they did until like 2009 but they're fine now --- man3/putenv.3 | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/man3/putenv.3 b/man3/putenv.3 index 59c2ff1..cb80b29 100644 --- a/man3/putenv.3 +++ b/man3/putenv.3 @@ -83,7 +83,7 @@ .SH ATTRIBUTES .SH STANDARDS POSIX.1-2008. .SH HISTORY -POSIX.1-2001, SVr4, 4.3BSD. +POSIX.1-2001, SVr2, 4.3BSD-Reno. .PP The .BR putenv () @@ -119,7 +119,8 @@ .SH HISTORY On the one hand this causes a memory leak, and on the other hand it violates SUSv2. .PP -The 4.4BSD version, like glibc 2.0, uses a copy. +The 4.3BSD-Reno version, like glibc 2.0, uses a copy; +this is fixed in all modern BSDs. .PP SUSv2 removes the \fIconst\fP from the prototype, and so does glibc 2.1.3. .PP -- 2.30.2
Attachment:
signature.asc
Description: PGP signature
