From owner-freebsd-current  Fri Sep 22 06:51:25 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id GAA01716
          for current-outgoing; Fri, 22 Sep 1995 06:51:25 -0700
Received: from id.slip.bcm.tmc.edu (root@hou08.onramp.net [199.1.137.136])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA01704
          for <freebsd-current@FreeBSD.org>; Fri, 22 Sep 1995 06:51:21 -0700
Received: (from rich@localhost) by id.slip.bcm.tmc.edu (8.6.12/8.6.9) id IAA04468; Fri, 22 Sep 1995 08:48:33 -0500
Date: Fri, 22 Sep 1995 08:48:33 -0500
From: Rich Murphey <rich@lamprey.utmb.edu>
Message-Id: <199509221348.IAA04468@id.slip.bcm.tmc.edu>
To: bde@zeta.org.au
CC: freebsd-current@FreeBSD.org, roberto@keltia.Freenix.FR
In-reply-to: <199509210528.PAA29710@godzilla.zeta.org.au> (message from Bruce Evans on Thu, 21 Sep 1995 15:28:36 +1000)
Subject: Re: XFree86 and the new malloc
Reply-to: rich@lamprey.utmb.edu
Sender: owner-current@FreeBSD.org
Precedence: bulk

|From: Bruce Evans <bde@zeta.org.au>
|
|>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.  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.

Hey, wait a sec.  XFree86 3.1.2 does use -lgnumalloc.  We
had been testing it but only switched when it passed all the
alpha/beta tests, and that happened after 3.0 came out.
Rich