Date: Thu, 6 Aug 1998 21:10:20 +1000 From: Bruce Evans <bde@zeta.org.au> To: dg@root.com, freebsd@xaa.iae.nl Cc: freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc Message-ID: <199808061110.VAA13616@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
> The problem with fixing setenv() is that you don't know if a pointer was >malloced, allocated from the env area above the stack, points to read-only >text, points to a static data buffer, etc. There really is no way to know >for sure, so you can't free the memory. Yo can know if you malloced it in a previous call to putenv() or setenv(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808061110.VAA13616>