From: joshuahab AT aol DOT com (Joshua Hab)
Newsgroups: comp.os.msdos.djgpp
Subject: GCC itself crashes, is this some sort of bug?
Lines: 29
Message-ID: <1998062707164600.DAA14687@ladder03.news.aol.com>
NNTP-Posting-Host: ladder03.news.aol.com
Date: 27 Jun 1998 07:16:46 GMT
Organization: AOL http://www.aol.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

I have a program that when compiled using

gcc -c cube.c -o cube.o

crashes on two different computers some of the time. I have no problems
compiling anything else.

The program makes use of Allegro, but I'm sure this isn't the problem because
it crashes on the compiling stage.

Error output is this:

Exiting due to signal SIGSEGV
Page fault at EIP=0001d074, error 0004
eax=00000000 ebx=58158b1e ecx=ffdce680 edx=ffdce500 esi=002d688c edi=002d6c6c
ebp=ffdcc9f0 esp=ffdcc9e4 program=C:\DJGPP\BIN\CC1.EXE
[snip limits, etc.]
Call frame traceback EIPs:
0x0001d074
0x0001d206
0x0001ef01
0x0001f716
0x000085ed
0x00026d32
0x000290e2
0x000efd9a

This is bizarre. I can post code if it is deemed relevant, it is a simple
program that rotates and displays cubes on the screen.