From owner-freebsd-current Sat Apr 13 22:18:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA25987 for current-outgoing; Sat, 13 Apr 1996 22:18:36 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA25982 for ; Sat, 13 Apr 1996 22:18:32 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id BAA09710; Sun, 14 Apr 1996 01:18:31 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id BAA08831; Sun, 14 Apr 1996 01:18:27 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Sun, 14 Apr 1996 01:18:24 -0400 (EDT) From: "Marc G. Fournier" To: David Greenman cc: current@freebsd.org Subject: Re: Can someone explain why... In-Reply-To: <199604140450.VAA03095@Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org