Date: Sun, 28 Jun 1998 15:23:26 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Joshua Hab <joshuahab AT aol DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: GCC itself crashes, is this some sort of bug?
In-Reply-To: <1998062707164600.DAA14687@ladder03.news.aol.com>
Message-ID: <Pine.SUN.3.91.980628151837.9146D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On 27 Jun 1998, Joshua Hab wrote:

> 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 usual reason for this is an insufficient stack available to the 
compiler.  The crash traceback shows which program (cc1.exe in your case)
crashes; you should stubedit that program and enlarge its stack size.  
The DJGPP FAQ list has the details in section 6.4.

> [snip limits, etc.]

You should NEVER remove anything from the crash traceback you post.  It 
includes crucial information about the cause(s) of the problem, and 
since you don't know why does it crash, you cannot possibly know what 
parts of the info are relevant.  Chances are, you will remove the most 
important parts.