Date: Wed, 21 Dec 2022 03:31:11 +0000 From: bugzilla-noreply@freebsd.org To: standards@FreeBSD.org Subject: [Bug 268479] lib/libc/stdlib/getenv.c may have a problem with putenv() Message-ID: <bug-268479-99-fqZEi5LgfR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268479-99@https.bugs.freebsd.org/bugzilla/> References: <bug-268479-99@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268479 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #2 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Dennis Clarke from comment #1) The way I read that material it indicates: A) '\0' is available as a potential internal(!) string terminator because the content of the string being represented is disallowed from including a '\0'. B) Nothing in the wording indicates an empty string is disallowed from being represented. Such an empty string could be followed by a string terminator ('\0') in the internal representation. > However putenv and setenv both allow the value to be just a NUL byte '\0' I suspect that this is '\0' used as an internal-string-terminator, not as content of the represented string. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268479-99-fqZEi5LgfR>