From owner-freebsd-questions Tue May 23 09:44:18 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA07329 for questions-outgoing; Tue, 23 May 1995 09:44:18 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA07321 for ; Tue, 23 May 1995 09:44:15 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id KAA08194; Tue, 23 May 1995 10:43:54 -0600 Date: Tue, 23 May 1995 10:43:54 -0600 From: Nate Williams Message-Id: <199505231643.KAA08194@trout.sri.MT.net> In-Reply-To: Erik Manders "A better malloc for freebsd" (May 23, 5:34pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Erik Manders , questions@FreeBSD.org Subject: Re: A better malloc for freebsd Sender: questions-owner@FreeBSD.org Precedence: bulk > if (or when) the malloc in 950412-SNAP will > be replaced by 2.0.5 or 2.1. I'm getting tired of compiling all big > user programs (xv, tin, etc...) with gnumalloc. I doubt very highly that the malloc in 2.0.5 or 2.1 will *not* be the one in the tree now. However, I spent a little bit of time cleaning up Doug Lea's version and will integrate it into my local test tree after the 2.0.5 release and run with it in a production environment at that time as a replacement for the stock malloc. Hopefully I'll be able to wring out any problems that might still be in programs that depend on the current BSD malloc implementation. (Another one was fixed last week) by doing this, and also get some performance improvements at the same time. 2.1 is supposed to be a very stable release, and changing the system malloc routine is something that could cause too many potential problems. Nate