Date: Thu, 6 Aug 1998 23:32:21 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Archie Cobbs <archie@whistle.com> Cc: freebsd-current@FreeBSD.ORG, bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu, dg@root.com Subject: Re: memory leaks in libc Message-ID: <199808070332.XAA17093@khavrinen.lcs.mit.edu> In-Reply-To: <199808070208.TAA26936@bubba.whistle.com> References: <199808070123.SAA26723@bubba.whistle.com> <199808070208.TAA26936@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Thu, 6 Aug 1998 19:08:48 -0700 (PDT), Archie Cobbs <archie@whistle.com> said: >> 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 believe that any program which suffers serious harm from the memory leak probably needs to use a different environment-access model. -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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808070332.XAA17093>