From owner-freebsd-current  Fri Aug  7 13:31:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA15681
          for freebsd-current-outgoing; Fri, 7 Aug 1998 13:31:12 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15641
          for <freebsd-current@FreeBSD.org>; Fri, 7 Aug 1998 13:31:03 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA24590;
	Fri, 7 Aug 1998 13:22:12 -0700 (PDT)
Message-Id: <199808072022.NAA24590@implode.root.com>
To: Archie Cobbs <archie@whistle.com>
cc: phk@critter.freebsd.dk (Poul-Henning Kamp), wollman@khavrinen.lcs.mit.edu,
        freebsd-current@FreeBSD.ORG, bde@zeta.org.au
Subject: Re: memory leaks in libc 
In-reply-to: Your message of "Fri, 07 Aug 1998 12:51:04 PDT."
             <199808071951.MAA04454@bubba.whistle.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 07 Aug 1998 13:22:11 -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>The attitude reflected in this statement is the exact opposite of mine,
>which is: Yes, there is a memoryleak associated with use of this API,
>let's fix the stupid bug and get on with it! Am I crazy for thinking
>that?

   I wouldn't say you're crazy by thinking that, but I'm still concerned
about programs that do a mix of setenv and private frobbing of the env.
It seems to me that by "fixing" this memory leak, you're quite likely adding
new bugs to existing programs.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message