From owner-freebsd-current Thu Aug 6 09:35:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02860 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:35:07 -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 JAA02838 for ; Thu, 6 Aug 1998 09:35: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 MAA14269; Thu, 6 Aug 1998 12:34:31 -0400 (EDT) (envelope-from wollman) Date: Thu, 6 Aug 1998 12:34:31 -0400 (EDT) From: Garrett Wollman Message-Id: <199808061634.MAA14269@khavrinen.lcs.mit.edu> To: Bruce Evans Cc: dg@root.com, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-Reply-To: <199808061335.XAA23389@godzilla.zeta.org.au> References: <199808061335.XAA23389@godzilla.zeta.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> Perhaps Bruce is suggesting that a seperate array be allocated to keep >> track of whether or not an env pointer was malloced? This would be very >> costly and, IMO, not worth it considering how rarely memory is lost by >> not freeing previously malloced strings. > Erm, this would be quite cheap, considering how rarely the environment is > updated except by programs that want to demonstrate leaks in it. So you both agree, then, that there is no point in wasting any more time on this? -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