From owner-freebsd-current Sun Apr 14 10:55:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA03727 for current-outgoing; Sun, 14 Apr 1996 10:55:30 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA03712 for ; Sun, 14 Apr 1996 10:55:22 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id KAA23202; Sun, 14 Apr 1996 10:55:10 -0700 From: "Rodney W. Grimes" Message-Id: <199604141755.KAA23202@GndRsh.aac.dev.com> Subject: Re: Can someone explain why... To: scrappy@ki.net (Marc G. Fournier) Date: Sun, 14 Apr 1996 10:55:10 -0700 (PDT) Cc: davidg@Root.COM, current@freebsd.org In-Reply-To: from "Marc G. Fournier" at "Apr 14, 96 01:18:24 am" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Sat, 13 Apr 1996, David Greenman wrote: > > > Simple - you have a memory problem and the part of memory that is caching > > gcc is wrong. It just happens that the code involved is only exercised when > > you use -O. It's easy to test this: just reboot your computer and see if the > > problem goes away. If it persists, then you might have a corrupt gcc binary. > > > Okay, that works for me...is there anything I can do to a SIMM to > test it *before* I change it? Or to test the new one before I even put it > in? Trial and Error doesn't seem to be an effective way of fixing this > problem :( Find a memory supplier that has a SIMM tester, that is the only true and accurate way to rule a SIMM good or bad, sans replacing it. I know these folks are not easy to find, but check with your local PC distributors (not retailers), they sometimes have one around. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD