Date: Mon, 15 Oct 2001 21:53:24 -0600 From: Warner Losh <imp@harmony.village.org> To: Heath Nielson <heath@cs.byu.edu> Cc: David Marker <marker_d@yahoo.com>, freebsd-stable@FreeBSD.ORG Subject: Re: setenv() cores with NULL value [was Re: Gdm proplem on 4.4] Message-ID: <200110160353.f9G3rO728525@harmony.village.org> In-Reply-To: Your message of "Mon, 15 Oct 2001 18:37:25 MDT." <Pine.LNX.4.33.0110151727300.6035-100000@organ.cs.byu.edu> References: <Pine.LNX.4.33.0110151727300.6035-100000@organ.cs.byu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.LNX.4.33.0110151727300.6035-100000@organ.cs.byu.edu> Heath Nielson writes: : FreeBSD doesn't like a NULL value. There was no mention of NULL input : values in the man page. It seems that a NULL value is valid. I can type : export TEST= at the prompt without any errors, but I'm no shell expert. : Maybe the TEST env. variable's value isn't really NULL. Does anyone else : have anything to add to this? NULL isn't allowed to be passed to getenv. That is a programming error. You get unpredictable results. We nicely give you a core file so you can debug your error. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110160353.f9G3rO728525>