Date: Fri, 12 Sep 1997 06:47:40 +0100 From: Martijn Koster <mak@webcrawler.com> To: freebsd-stable@freebsd.org Subject: [mak@webcrawler.com: malloc.c problems in 2.2 stable?] Message-ID: <19970912064740.36419@webcrawler.com>
next in thread | raw e-mail | index | archive | help
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 <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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970912064740.36419>