From owner-freebsd-questions  Sat Jul  5 15:47:52 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA23449
          for questions-outgoing; Sat, 5 Jul 1997 15:47:52 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23444
          for <freebsd-questions@FreeBSD.ORG>; Sat, 5 Jul 1997 15:47:48 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id PAA04788;
	Sat, 5 Jul 1997 15:49:24 -0700 (PDT)
Message-Id: <199707052249.PAA04788@implode.root.com>
To: dburr@POBoxes.com
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: what is wrong with my machine??! 
In-reply-to: Your message of "Sat, 05 Jul 1997 14:41:57 GMT."
             <33c05876.34863358@mail.inreach.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sat, 05 Jul 1997 15:49:24 -0700
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Anyway, here is the problem:  When compiling large programs, the
>compile sometimes stops with an error.  usually the error is something
>like "parse error before '}'" but I remember one time when it was
>something else (can't remember what the error was at that time,
>though).  The weird thing is, there IS no error (when I read the file,
>it looks like perfectly good C syntax to me), and, if I run 'make' and
>recompile that file WITHOUT CHANGING IT, it works fine!

   This usually indicates a cache, CPU, or other hardware problem.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project