Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ucla-cs!zen!ucbvax!jade!saturn!ucscc.UCSC.EDU!haynes
From: haynes@ucscc.UCSC.EDU.ucsc.edu (99700000)
Newsgroups: comp.unix.wizards
Subject: Re: Bizzare, non repeatable, 4.3 C compiler behavior
Message-ID: <555@saturn.ucsc.edu>
Date: Mon, 20-Jul-87 16:38:27 EDT
Article-I.D.: saturn.555
Posted: Mon Jul 20 16:38:27 1987
Date-Received: Fri, 24-Jul-87 02:37:31 EDT
References: <328@rocksanne.UUCP> <962@argus.UUCP>
Sender: usenet@saturn.ucsc.edu
Reply-To: haynes@ucscc.UCSC.EDU (Jim Haynes)
Organization: California State Home for the Weird
Lines: 19

What all this suggests is that there might be a non-repeatable hardware
problem that doesn't show up except when the system is running normally.
We had a case a while back which happened to be a bad Ethernet controller.
It was apparently writing to addresses other than those of Ethernet buffers.
So a question is, is the system doing anything else strange besides the
c compiler problem?  If so, you probably have a hardware problem.  Diagnostics
probably won't show it, because they don't get all the peripherals moving
at once.  In our case the bad Ethernet controller worked fine when installed
in a diskless workstation, but would trash a multi-user system badly.

Then there was a problem back about Versin 6 where the C compiler had only
a very limited set of temp file names, so you could only do one compilation
at a time, but I guess that was fixed long before 4.3



haynes@ucscc.ucsc.edu
haynes@ucscc.bitnet
..ucbvax!ucscc!haynes