From owner-freebsd-current Fri Aug 7 12:52:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07267 for freebsd-current-outgoing; Fri, 7 Aug 1998 12:52:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07262 for ; Fri, 7 Aug 1998 12:52:26 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA07644; Fri, 7 Aug 1998 12:51:23 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma007642; Fri Aug 7 12:51:04 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA04454; Fri, 7 Aug 1998 12:51:04 -0700 (PDT) From: Archie Cobbs Message-Id: <199808071951.MAA04454@bubba.whistle.com> Subject: Re: memory leaks in libc In-Reply-To: <3224.902516512@critter.freebsd.dk> from Poul-Henning Kamp at "Aug 7, 98 09:01:52 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Fri, 7 Aug 1998 12:51:04 -0700 (PDT) Cc: wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG, bde@zeta.org.au, dg@root.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > >I just don't understand where you're coming from. There is a clear > >bug in the standard library, we agree on this right? You are saying > >that it's not worth fixing, because... > > I think there is agreement that a bogus API was defined long time ago, > and since getting rid of that API not worth even discussing, this > entire thread is a waste of time. ? Who's talking about changing the API? I think you're misunderstanding the issue. The issue is simply: there's a memory leak in libc, should we or should we not fix it? It's a standard bug-fix cost/benefit question. > Yes, there is a memoryleak associated with use of this API, > if that is unacceptable for your application then don't use this API. 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? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message