From owner-freebsd-hackers  Fri Jun 26 07:17:53 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA12745
          for freebsd-hackers-outgoing; Fri, 26 Jun 1998 07:17:53 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from main.fiscodata.com.br (main.fiscodata.com.br [200.250.227.210])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12718
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 26 Jun 1998 07:17:27 -0700 (PDT)
          (envelope-from paulo@main.fiscodata.com.br)
Received: (from paulo@localhost)
	by main.fiscodata.com.br (8.8.8/8.8.5) id LAA15525;
	Fri, 26 Jun 1998 11:21:46 -0300 (EST)
Date: Fri, 26 Jun 1998 11:21:46 -0300 (EST)
Message-Id: <199806261421.LAA15525@main.fiscodata.com.br>
From: Paulo Cesar Pereira de Andrade <paulo@main.fiscodata.com.br>
To: rssh@grad.kiev.ua
CC: J.Hogeveen@twiddle.com, freebsd-hackers@FreeBSD.ORG
In-reply-to: <3592BA54.9A3CA8EF@Shevchenko.Kiev.UA>
	(Ruslan@Shevchenko.Kiev.UA)
Subject: Re: Signal-11
References: <Pine.BSF.3.96.980625214302.12963A-100000@Dot.Twiddle.COM> <3592BA54.9A3CA8EF@Shevchenko.Kiev.UA>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

|> Date: Fri, 26 Jun 1998 00:00:05 +0300
|> From: Ruslan Shevchenko <Ruslan@Shevchenko.Kiev.UA>
|> 
|> Jeroen Hogeveen wrote:
|> 
|> > hi, just one quick question. sorry to ask it here, but response on
|> > -questions is 0,0.
|> >
|> > Has anyone had experiences regarding sig11's like these?
|> >   .map\" -O -pipe -I/usr/local/include  log-server.c
|> >   gcc: Internal compiler error: program as got fatal signal 11
|> >   *** Error code 1
|> >
|> > Sig-11 indicates a SIGSEV - segmentation violation as far as I know.
|> > Does this mean my memory (configuration) is bad or that my CPU is
|> > overheated?
|> >
|> 
|>  You can check this, by doing make (or compiling) again and again.
|> 
|> If this error is reprodusable, than it is gcc error
|> (gcc is very buggy), otherwise --- memory error.
|> 

  I have a 486 machine that frequently trashes files. Sometimes,
while doing a large compile, gcc will not understand the C language
anymore ;), doing the *same* error always. A simple reboot and recompile
works fine.

  The most common problems is the gcc executable file image being loaded
incorrectly from disk or the file it is compiling. I think the real problem
with this machine may be the hard disk, but the cause of the repeteable
failures is the file cache with wrong data.

Paulo


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