From owner-freebsd-hackers Tue Oct 21 01:46:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA00416 for hackers-outgoing; Tue, 21 Oct 1997 01:46:07 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA00408 for ; Tue, 21 Oct 1997 01:46:02 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id KAA26850 for ; Tue, 21 Oct 1997 10:56:05 +0200 (SAT) Received: by citadel via recvmail id 26817; Tue Oct 21 10:55:42 1997 by gram.cdsec.com (8.8.5/8.8.5) id KAA12807 for hackers@freebsd.org; Tue, 21 Oct 1997 10:22:20 +0200 (SAT) From: Graham Wheeler Message-Id: <199710210822.KAA12807@cdsec.com> Subject: Re: Bug in 2.2.2 To: hackers@freebsd.org Date: Tue, 21 Oct 1997 10:22:19 +0200 (SAT) X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I wrote a small program to exercise the heap and ran it for about ten million > > iterations without a problem. Then I decided to add a periodic call to fork(), > > as both Midnight Commander and the firewall gateway program both do plenty > > of these. When I ran this the O/S panicked almost immediately. > > > Graham, > i have run your test program, both with and without fork(), > against phkmalloc from 2.2 upgraded to CTM 470 for over 10 > million iterations. the upgrade replaces > /home/src/lib/libc/stdlib/malloc.c version 1.18.2.2 with > version 1.18.2.3. there are changes in the way that > phkmalloc deals with changing sizes fo allocated memory > and more. ;) > > can you upgrade from 2.2.2 to 2.2.5 and run your code again? > 2.2.5 will be out very soon. the source tree will be > tagged within the hour (Oct 20th 6pm PDT). We have a subscription, which means I will be able to do this, but only in a few weeks time. I upgraded my HDD at home last night, and, not having a 2.2.2 CD there, installed 2.2.1. If I remember I will run the program there tonight, and see what happens, just for interest. Would it be possible to use the newer malloc.c with 2.2.2, without changing anything else? That would be a test I could do in the short term. -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)-253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/