Date: Fri, 07 Aug 1998 21:01:52 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Archie Cobbs <archie@whistle.com> 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 Message-ID: <3224.902516512@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 07 Aug 1998 10:12:48 PDT." <199808071712.KAA29716@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199808071712.KAA29716@bubba.whistle.com>, Archie Cobbs writes: >Garrett Wollman writes: >> >> malloc() is simple enough. It would solve the problem for programs >> >> than need it (a real world example of which exists at Whistle). >> >> > OK, just to prove I'm not lazy... try this. >> >> Now having gone to that effort, you can just add it to your program >> that needs it, and we don't have to bear the kluge in the C library. > >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. Summary: Yes, there is a memoryleak associated with use of this API, if that is unacceptable for your application then don't use this API. Would this thread please DROP DEAD preferably RIGHT NOW! THANKYOU! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3224.902516512>