Date: Tue, 01 Sep 1998 10:17:49 +0200 From: Stefan Eggers <seggers@semyam.dinoco.de> To: joelh@gnu.org Cc: bright@hotjobs.com, matthew@wolfepub.com, hackers@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Environment of a process Message-ID: <199809010817.KAA06341@semyam.dinoco.de> In-Reply-To: Your message of "Mon, 31 Aug 1998 19:08:58 CDT." <199809010008.TAA11460@detlev.UUCP>
next in thread | previous in thread | raw e-mail | index | archive | help
> You can also use setenv, preferably between the fork and exec. (There > was recently a thread about a memory leak if this is done frequently, > tho. I don't know the details.) It was in freebsd-current where you might have seen this lately. The problem is that setenv doesn't free the memory used by the old value. Done between fork and exec it is of no importance as due to the exec the VM of the process where it leaked goes away. It then just leaks in the child process and that only lasts till exec. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809010817.KAA06341>