Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.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.s@ihug.co.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.ml@btinternet.com>
CC: cygwin <cygwin@cygwin.com>
Subject: Re: possible GCC bug
References: <000701c14454$661a8440$0149a8c0@sknet01>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.s@ihug.co.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/