Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
X-Authentication-Warning:	smtp2.ihug.co.nz: Host animal.ihug.co.nz [203.109.255.132] claimed to be ihug.co.nz
Message-ID:	<3BAE5413.16D5DEC8@ihug.co.nz>
Date:	Mon, 24 Sep 2001 09:28:51 +1200
From:	Ross Smith <ross DOT s AT ihug DOT co DOT nz>
Organization:	Ihug
X-Mailer:	Mozilla 4.77 [en] (X11; U; Linux 2.2.18 i686)
X-Accept-Language:	en
MIME-Version:	1.0
To:	Drew <sk DOT ml AT btinternet DOT com>
CC:	cygwin <cygwin AT cygwin DOT com>
Subject:	Re: possible GCC bug
References:	<000701c14454$661a8440$0149a8c0 AT sknet01>

Drew wrote:
> 
> gcc: Internal compiler error: program cc1 got fatal signal 11

Signal 11 from GCC nearly always means that you have faulty hardware
(probably RAM). GCC is an excellent stress test for the hardware it's
running on, and will often show up small hardware faults that don't
trouble many other programs.

-- 
Ross Smith .......................................... ross DOT s AT ihug DOT co DOT nz
Ihug (Auckland, New Zealand) ................... http://www.ihug.co.nz/

           Vs lbh pna ernq guvf, lbh'er ivbyngvat gur QZPN

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -