From owner-freebsd-bugs  Thu Jul 23 00:37:02 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA29320
          for freebsd-bugs-outgoing; Thu, 23 Jul 1998 00:37:02 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29308;
          Thu, 23 Jul 1998 00:36:57 -0700 (PDT)
          (envelope-from hoek@FreeBSD.org)
From: Tim Vanderhoek <hoek@FreeBSD.ORG>
Received: (from hoek@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id AAA08185;
	Thu, 23 Jul 1998 00:36:32 -0700 (PDT)
Date: Thu, 23 Jul 1998 00:36:32 -0700 (PDT)
Message-Id: <199807230736.AAA08185@freefall.freebsd.org>
To: scottm@cs.ucla.edu, hoek@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/5974
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: -current VM oddities

State-Changed-From-To: open-closed
State-Changed-By: hoek
State-Changed-When: Thu Jul 23 00:31:35 PDT 1998
State-Changed-Why: 
Random coredumps and inexplicable compile errors are a prime indicator
of bad memory.


PRs of this type should be sent to -current, anyways.  Besides, the fact
that you were the only person complaining about ld.so being broken
should have made you at least suspect a less generic bug.  :)

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message