From owner-freebsd-stable Thu Sep 11 22:50:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA05957 for stable-outgoing; Thu, 11 Sep 1997 22:50:07 -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 WAA05937 for ; Thu, 11 Sep 1997 22:50:01 -0700 (PDT) Received: (qmail 8745 invoked by uid 982); 12 Sep 1997 05:47:41 -0000 Message-ID: <19970912064740.36419@webcrawler.com> Date: Fri, 12 Sep 1997 06:47:40 +0100 From: Martijn Koster To: freebsd-stable@freebsd.org Subject: [mak@webcrawler.com: malloc.c problems in 2.2 stable?] Mime-Version: 1.0 Content-Type: message/rfc822 Content-Description: Forwarded message from Martijn Koster X-Mailer: Mutt 0.76 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, [got no replies on freebsd-questions, hoping for more luck here] [apologies if this has come up before] 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 '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