Date: Sat, 24 Jun 1995 16:56:12 +1000 (EST) From: David Dawes <dawes@physics.usyd.edu.au> To: freebsd-hackers@freebsd.org Subject: Re: Memory leak somewhere? Message-ID: <199506240656.AA02226@physics.su.oz.au> In-Reply-To: <199506240634.IAA02830@uriah.heep.sax.de> from "J Wunsch" at Jun 24, 95 08:34:08 am
next in thread | previous in thread | raw e-mail | index | archive | help
>As David Dawes wrote: >> >> I've noticed it growing fairly large too. I've tried linking it with >> -lgnumalloc (Linux uses GNU malloc by default), and that seems to help >> (you can do this using the XFree86 LinkKit) > >Perhaps i should rather direct this to xfree86-beta: > >XFree86 used to link the binaries against -lgnumalloc by default in >earlier versions. NetBSD still does. Is there any reason why it has >been dropped for FreeBSD? (I think gnumalloc falls under LGPL, so the >Copyright issues aren't so hard here.) > >At least for the server, it seems to be a big deal. I used to link >mine against the GNU version, and now that i didn't do it for the >first time, i'm seeing it growing rather large, too. It was dropped because someone reported problems with it. I've been using it for the last few weeks without problems though, and I'm planning to link with gnumalloc by default for FreeBSD in XFree86 3.1.2. Regarding LGPL, there is no problem for the Xserver because we have the LinkKit. I don't know about clients, etc, or how LGPL fits in with dynamically loaded libraries (I'd have expected dynamic linking to fulfill the requirements of LGPL). Anyway, this is an issue for those distributing binaries. We (XFree86) provide full source, so there isn't any problem for us. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506240656.AA02226>