From owner-freebsd-current Wed Sep 20 23:21:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA26786 for current-outgoing; Wed, 20 Sep 1995 23:21:24 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA26777 for ; Wed, 20 Sep 1995 23:21:20 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id AAA01482; Thu, 21 Sep 1995 00:23:00 -0600 Date: Thu, 21 Sep 1995 00:23:00 -0600 From: Nate Williams Message-Id: <199509210623.AAA01482@rocky.sri.MT.net> To: Bruce Evans Cc: freebsd-current@FreeBSD.org, roberto@keltia.Freenix.FR Subject: Re: XFree86 and the new malloc In-Reply-To: <199509210528.PAA29710@godzilla.zeta.org.au> References: <199509210528.PAA29710@godzilla.zeta.org.au> Sender: owner-current@FreeBSD.org Precedence: bulk > >Has anyone tried to link the X server with the new libc's malloc from > >Poul-Henning ? > > It's already linked to libc's malloc unless you have a version that is > linked to a nonstandard libmalloc. Actually, version XFree 3.1.2 links against GNU malloc on BSD systems to minimize real memory use as far as I know. > This is one of the main advantages (?) of not putting phkmalloc in a > special library that almost no one will use. It also shows why third > party programs should not use nonstandard libraries to avoid problems > in standard libaries. Except when the 'standard' library has so many problems that the program is much more useful with these non-standard libraries. :( Nate