From:	broeker AT physik DOT rwth-aachen DOT de
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Compiler crash??
Date:	31 Mar 2000 15:51:33 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	24
Message-ID:	<8c2hi5$omu$1@nets3.rz.RWTH-Aachen.DE>
References:	<38E4796F AT MailAndNews DOT com>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 954517893 25310 137.226.32.75 (31 Mar 2000 15:51:33 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	31 Mar 2000 15:51:33 GMT
Originator:	broeker@
To:	djgpp AT Delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Artur Butryn <akaja AT mailandnews DOT com> wrote:
> I have following problem. Very often when I try to compile something a 
> following errror message is displayed.

'Very often' means what? If you repeatedly try the same compile, of
the same source file, does the error appear every time?  If not,
you've probably tuned your hardware beyond its limits. Software
doesn't usually behave differently, in repeated runs. If it does: does
it depend on the source file? Could you check the same source file on
another machine with GCC installed (or post it here, if its small)?

>  Compiling: test.cpp
>  Exiting due to signal SIGILL
>  Invalid Opcode at eip=00007201

This is a very strange type of error. About the only way I think you
could get it is

1) your memory loses single bits (bad or overly stressed RAM chips)
2) you caught a virus (improbable, it wouldn't normally have got past
   the COFF selfcheck.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -