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
Reply-To: <Alec AT Mihailovs DOT com>
From: "Alec Mihailovs" <mihailovs AT email DOT msn DOT com>
To: "Cygwin" <cygwin AT cygwin DOT com>, "Ross Smith" <ross DOT s AT ihug DOT co DOT nz>
Subject: RE: possible GCC bug
Date: Sun, 23 Sep 2001 19:37:39 -0400
Message-ID: <NCBBKFBLELHDDEGCEHPIEEMKEPAA.mihailovs@email.msn.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <3BAE5413.16D5DEC8@ihug.co.nz>
Importance: Normal
X-OriginalArrivalTime: 23 Sep 2001 23:37:05.0265 (UTC) FILETIME=[A7175610:01C14488]

>> gcc: Internal compiler error: program cc1 got fatal signal 11
Ross Smith wrote:
> 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.

I also get fatal signal 11, make error 139 and a stack dump on 3 different
computers running
cygwin with Windows 98, Windows 2000 and Windows XP trying to compile
lie.exe which compiles without any problems on the same computers running
Linux.
That doesn't look like a hardware fault for me. Here is one of the stack
dumps
(for Windows 98):

Exception: STATUS_ACCESS_VIOLATION at eip=61082C9E
eax=00401145 ebx=00401145 ecx=FFFFFE79 edx=00000000 esi=00000000
edi=614E474C
ebp=007CFC8C esp=007CFC88 program=C:\CYGWIN\LIE\LIE.EXE
cs=0167 ds=016F es=016F fs=6BD7 gs=0000 ss=016F
Stack trace:
Frame     Function  Args
007CFC8C  61082C9E  (00000000, 00401145, 007CFCCC, 61082BE3)
007CFCBC  0040123F  (00401145, 00000000, 007CFCEC, 004013FF)
007CFCEC  00401432  (00000000, 00000000, 007CFD2C, 00409175)
007CFD0C  0040842D  (00000004, 61095368, 00000001, 00000001)
007CFD2C  00409205  (00000001, 614E474C, 00A00008, 00000000)
007CFD88  6100401E  (00000000, 00000000, 00000000, 00000002)
007CFDB8  6100421D  (00409150, 00000000, 81748244, 00000000)
007CFDD8  6100425C  (00000000, 00000000, FFFFFFFF, 00000004)
007CFE08  00429A0B  (00409150, 007CFC8C, BFFC9490, 007CFF68)
007CFE38  0040103D  (00000000, 81747FA4, 00000000, 0065694C)
007CFF78  BFF8B560  (81748200, 00000008, 81747FA4, 00000000)
  83558 [main] Lie 1878673 handle_exceptions: Error while dumping state
(probably corrupted stack)

$ uname -a
CYGWIN_98-4.10 ALEC 1.3.3(0.46.3.2) 2001-09-12 23:54 i686 unknown

Alec Mihailovs
http://webpages.shepherd.edu/amihailo/




--
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/