Message-ID:	<007501bf9b3f$35f8b580$b4e406d5@akaja.01019freenet.de>
From:	"D&V" <akaja AT 01019freenet DOT de>
To:	"Andris Pavenis" <pavenis AT lanet DOT lv>
Cc:	<djgpp AT Delorie DOT com>
Subject:	Re: Compiler crash??
Date:	Fri, 31 Mar 2000 20:28:50 +0200
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 4.72.3110.5
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3110.3
Reply-To:	djgpp AT delorie DOT com

You were right, the overclocking caused the compiler to crash. Now
everything seems to be fine.

-----Original Message-----
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Artur Butryn <akaja AT MailAndNews DOT com>
Cc: djgpp AT delorie DOT com <djgpp AT delorie DOT com>
Date: Friday, March 31, 2000 9:57 AM
Subject: Re: Compiler crash??


>
>
>I intentionally didn't strip executables in binary archives of DJGPP port
>of gcc-2.95.2. Information included in binaries is enough for symify to
>provide stack trace but not enough for debuggers. So use it to get
>more info. Read DJGPP FAQ if needed. There were more than one update of
>port of gcc-2.95.2, so I don't know which one You have.
>
>Also STOP OVERCLOCKING Your CPU and look whether problem goes away.
>     =================
>
>Andris
>
>
>On Thu, 30 Mar 2000, Artur Butryn wrote:
>
>> I have following problem. Very often when I try to compile something a
>> following errror message is displayed.
>>
>>
>>  Compiling: test.cpp
>>  Exiting due to signal SIGILL
>>  Invalid Opcode at eip=00007201
>>  eax=00000020 ebx=00000120 ecx=50f4c483 edx=00000149 esi=001b7314
>> edi=001bd84
>>  ebp=001a9f78 esp=001a9f10
program=C:\DJGPP\LIB\GCC-LIB\DJGPP\2.952\CPP.EXE
>>  sel=0457  base=82fb3000  limit=001cffff
>>  sel=045f  base=82fb3000  limit=001cffff
>>  sel=045f  base=82fb3000  limit=001cffff
>>  sel=0437  base=00016180  limit=0000ffff
>>  sel=046f  base=00000000  limit=0010ffff
>>  sel=045f  base=82fb3000  limit=001cffff
>>  App stack: [001aa718..00033718]  Exceptn stack: [00033624..000316e4]
>>  Call frame traceback EIPs:
>>    0x00007201
>>    0x0000a48e
>>    0x00009975
>>    0x00008639
>>    0x000067fb
>>    0x0000a48e
>>    0x00009975
>>    0x00008639
>>    0x000067fb
>>    0x0000a48e
>>    0x00009975
>>    0x00008639
>>    0x000067fb
>>    0x00005940
>>    0x00017bfe
>>  There were some errors
>>
>>
>> I'm using:
>> Cyrix P166+ (overclocked  to 200Mhz)
>> 32Mb RAM
>> WIN 95
>> lotsa disk space
>>
>> The same thing happens when I quit to DOS and run DJPP with CWSDPMI.EXE
>> I check in FAQ but there was no inf on this sort of behaviour.
>> Is it some sort of compiler bug?
>>
>> Akaja
>>
>>
>
>

- Raw text -