From owner-freebsd-current Tue May 8 9:13:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 8875C37B422 for ; Tue, 8 May 2001 09:13:41 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0302.cvx21-bradley.dialup.earthlink.net [209.179.193.47]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id MAA18898; Tue, 8 May 2001 12:12:49 -0400 (EDT) Message-ID: <3AF81B16.7EC1F3DE@mindspring.com> Date: Tue, 08 May 2001 09:13:10 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Dennis Glatting , Kris Kennaway , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm References: <20010507074503.Y24943-100000@btw.plaintalk.bellevue.wa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > Plus, your program doesn't even do what you think it does (because a) > it has at least one significant bug and b) malloc() doesn't behave the > way you think it does). And even if it did, the /dev/random stuff is > pointless, you can achieve the same effect by setting every byte you > allocate (possibly even just the first byte of every chunk) to 0. So now the question becomes "what is he testing that is resulting in 4.3 locking up?". Your suggested replacement test might be fun to run, but I think it wouldn't lock up 4.3... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message