From owner-freebsd-questions  Wed Sep 10 02:35:51 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id CAA19894
          for questions-outgoing; Wed, 10 Sep 1997 02:35:51 -0700 (PDT)
Received: from mailgate.greenhills.co.uk (mailgate.greenhills.co.uk [195.11.194.180])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA19889
          for <freebsd-questions@freebsd.org>; Wed, 10 Sep 1997 02:35:47 -0700 (PDT)
Received: (qmail 6723 invoked by uid 982); 10 Sep 1997 09:33:28 -0000
Message-ID: <19970910103328.56275@webcrawler.com>
Date: Wed, 10 Sep 1997 10:33:28 +0100
From: Martijn Koster <mak@webcrawler.com>
To: freebsd-questions@freebsd.org
Subject: malloc.c problems in 2.2 stable?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.76
Sender: owner-freebsd-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi all,

[apologies if this has come up before; I've only just (re)subscribed.]

I've justed finished tracking down swap filling on one of my
2.2-stable production machines to procmail (delivering an only 8M
message), then to realloc.

A search of the mailing lists turned up John Fieber
<jfieber@indiana.edu>'s suggestions in June of moving to 3.0-current
malloc.c, and that indeed fixed things. Cool!


Anyway, what suprises me is that I cvsup with tag=RELENG_2_2, yet saw
this fairly major (to me) problem.  Is this fix not in 2.2-stable for
a reason? Is it there, but am I tracking it wrong? Should I use
some another malloc.c? Is just changing malloc.c safe?

The malloc.c I had was:

 * $Id: malloc.c,v 1.18.2.3 1997/07/24 08:25:25 phk Exp $

the one I use now is:

 * $Id: malloc.c,v 1.32 1997/08/31 05:59:39 phk Exp $

and:

  ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/lib/libc/stdlib/malloc.c

is a different one alltogether. Huh?

Any suggestions appreciated.

-- Martijn Koster, m.koster@pobox.com