From owner-freebsd-bugs Wed Jan 26 14: 0:17 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3755E156AE for ; Wed, 26 Jan 2000 14:00:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id OAA56617; Wed, 26 Jan 2000 14:00:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Wed, 26 Jan 2000 14:00:03 -0800 (PST) Message-Id: <200001262200.OAA56617@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Archie Cobbs Subject: Re: bin/5604: setenv(3) function has memory leak, other bugs Reply-To: Archie Cobbs Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/5604; it has been noted by GNATS. From: Archie Cobbs To: peter.jeremy@alcatel.com.au (Peter Jeremy) Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: bin/5604: setenv(3) function has memory leak, other bugs Date: Wed, 26 Jan 2000 13:54:08 -0800 (PST) Peter Jeremy writes: > In view of the upcoming 4.0-RELEASE freeze, together with the apparent > impossibility to implement a setenv(3) that doesn't have memory leaks, > could you please consider committing the following patch which at > least documents the problem. I would be satisfied with this as a `fix' > for PR bin/10341 (though it doesn't address the second part of bin/5604). Thanks, I'll do it. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message