Date: Sun, 8 Aug 1999 14:17:01 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Michel de Ruiter <Michel AT smr DOT nl>
cc: "'DJGPP workers'" <djgpp-workers AT delorie DOT com>
Subject: Re: Gcc crash
In-Reply-To: <B0FEA00E82A7D1118BFB00A0CC99027821336A@ARGON>
Message-ID: <Pine.SUN.3.91.990808141643.23423Z-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Fri, 6 Aug 1999, Michel de Ruiter wrote:

> If anyone has a vague guess or idea of what might be going on, please
> help.

After trying the release version, like Andris suggested, if the crash
persists, post the traceback.  Then someone with sources might be able
to see where in the source code does it crash, which might give enough
hints to unlock the problem. 

In the meantime, you could disassemble inside a debugger near EIP
0x0c0ba2, and see what instruction is that.  Then at least you will
know what register seems to have the garbled value.  I'm guessing that
EAX is the culprit, but I might be wrong.

Btw, did you try stubediting cc1.exe to enlarge its stack?  If not, I
suggest to bump it to at least 1MB and try again.  The crash traceback
shows a very shallow stack, but some previous code might have
overflowed the stack and overwrote some data in the .bss or .data
sections.