Date: 11 Aug 1999 09:53:14 +0200 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/5604: setenv(3) function has memory leak, other bugs Message-ID: <xzpwvv2vjmd.fsf@flood.ping.uio.no> In-Reply-To: Peter Jeremy's message of "Tue, 10 Aug 1999 15:00:02 -0700 (PDT)" References: <199908102200.PAA25697@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Jeremy <jeremyp@gsmx07.alcatel.com.au> writes: > The approach used in Solaris and OSF/1 (I'm not sure what POSIX > mandates) is not to have a setenv(3) at all. Instead putenv(3) > directly manipulates the environment and requires that the string > pointed to by its argument remain valid (ie not be an automatic > variable). This pushes the memory management issue onto the > application. We have putenv() too, but it's just a wrapper for setenv(). I think we should rewrite our putenv() to conform to the SUSV2 (as described above) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpwvv2vjmd.fsf>