Date: Fri, 19 May 2000 10:18:27 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: "Dr. J. Robert Lee" <jrl AT netcom DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: gcc djgpp stopped working
In-Reply-To: <8g26dn$43d$1@slb2.atl.mindspring.net>
Message-ID: <Pine.A41.4.05.10005191014040.29210-100000@ieva06.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


Try using symify on gcc and post results. 

I intentionally left minimal debug info in executables to enable getting
reasonable stack trace on such crashes. Also there were more that one
update of binaries of gcc-2.95.2 for DJGPP, so I don't know
which update You have 

Andris

On 19 May 2000, Dr. J. Robert Lee wrote:

> 
> Until earlier today, I had been happily using the djgpp gcc compiler
> for many months. Around midday, I made the mistake of updating
> windows 98 by responding to the critical update notification message.
> Now that I have the latest security package in place, gcc no longer
> works. It runs for a several minutes then aborts. Here is what I get:
> 
> jrl E:\src\SIGPROC>gcc -dumpversion
> 2.952
> 
> jrl E:\src\SIGPROC>gcc -c anyfile.c
> Abort!
> Exiting due to signal SIGABRT
> Raised at eip=00014ff6
> eax=000a9a44 ebx=00000120 ecx=00000000 edx=0000b460 esi=00000002 edi=000b0956
> ebp=000a9af0 esp=000a9a40 program=E:\COMPILE\DJGPP\BIN\GCC.EXE
> cs: sel=00a7  base=82c0f000  limit=000bffff
> ds: sel=00af  base=82c0f000  limit=000bffff
> es: sel=00af  base=82c0f000  limit=000bffff
> fs: sel=0087  base=0000b460  limit=0000ffff
> gs: sel=00bf  base=00000000  limit=0010ffff
> ss: sel=00af  base=82c0f000  limit=000bffff
> App stack: [000a9f2c..00029f2c]  Exceptn stack: [00029e80..00027f40]
> 
> Call frame traceback EIPs:
>   0x00014f14
>   0x00014ff6
>   0x0001584b
>   0x00010c98
>   0x0000bc56
>   0x0000ccf1
>   0x0000c509
>   0x0000ccf1
>   0x0000c509
>   0x0000ccf1
>   0x0000c509
>   0x0000ccf1
>   0x0000c509
>   0x0000ad44
>   0x0000ea58
>   0x000127f6
> 
> Interestingly, another machine has the same security upgrade, done around the
> same time today, but gcc on it still functions. Both machines are running Win98 
> second edition with all of the critical MS updates. The machine that works is a 
> Pentium II 400; the one that does not work is a Pentium III 733.
> 
> On the bad machine:
> jrl E:\compile\djgpp\bin>go32-v2
> go32/v2 version 2.0 built Dec 24 1999 17:46:57
> DPMI memory available: 94977 Kb
> DPMI swap space available: 32603 Kb
> 
> On the working machine:
> DPMI memory available: 22201 Kb
> DPMI swap space available: 40095 Kb
> 
> Ideas for trouble-shooting?
> --
> J. Robert Lee, Ph.D.
> jrl AT netcom DOT com
>