From owner-freebsd-current Fri Aug 7 10:22:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12224 for freebsd-current-outgoing; Fri, 7 Aug 1998 10:22:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12056 for ; Fri, 7 Aug 1998 10:22:00 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id NAA20680; Fri, 7 Aug 1998 13:21:21 -0400 (EDT) (envelope-from wollman) Date: Fri, 7 Aug 1998 13:21:21 -0400 (EDT) From: Garrett Wollman Message-Id: <199808071721.NAA20680@khavrinen.lcs.mit.edu> To: Archie Cobbs Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), freebsd-current@FreeBSD.ORG, bde@zeta.org.au, dg@root.com Subject: Re: memory leaks in libc In-Reply-To: <199808071712.KAA29716@bubba.whistle.com> References: <199808070332.XAA17093@khavrinen.lcs.mit.edu> <199808071712.KAA29716@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> I believe that any program which suffers serious harm from the memory >> leak probably needs to use a different environment-access model. > Yes, until we fix the bug. Then they don't anymore, that's the whole point. No, you've missed the point entirely. *Any program which does enough playing around with the environment to be harmed by this memory leak is using a totally inappropriate interface.* -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message