Date: Tue, 25 Jan 2000 10:43:49 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Erik Berglund <erik2 DOT berglund AT telia DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: gcc page fault
In-Reply-To: <Z_0j4.1339$dT4.192511488@newsb.telia.net>
Message-ID: <Pine.A41.4.05.10001251023010.132838-100000@ieva01.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On Mon, 24 Jan 2000, Erik Berglund wrote:

> I was wondering if anyone could help me find
> a mysterious problem in gcc 2.95.2:
> 
> Page fault at eip=0017651f, error=0004
> eax=00e45840 ebx=00392604 ecx=00392604 edx=00fd53330 esi=003935fc
> edi=00391610
> ebp=003303b0 esp=003303a4 program=C:\DJGPP\BIN\CC1.EXE

If it' really CC1.EXE from gcc-2.95.2 You can use symify to get more
usefull stack trace (I intentionally didn't strip binaries for this as
it's difficult to reproduce binaries exactly)

However it should be C:\DJGPP\LIB\GCC-LIB\DJGPP\2.952\CC1.EXE for
GCC-2.95.2. So You either have done something completely wrong with GCC
installation or You You still have outdated binary from GCC-2.7.2.1 in
C:\DJGPP\BIN. You should not have CC1.EXE in C:/DJGPP/BIN.

Andris

> cs: sel=00a7  base=81043000  limit=fffeffff
> ds: sel=00af  base=81043000  limit=fffeffff
> es: sel=00af  base=81043000  limit=fffeffff
> fs: sel=0087  base=0001e3e0  limit=0000ffff
> gs: sel=00bf  base=00000000  limit=0010ffff
> ss: sel=00af  base=81043000  limit=fffeffff
> App stack: [00332000..001b2000]  Exceptn stack: [001a2818..001a08d8]
>  
> Call frame traceback EIPs:
>   0x0017651f   0x17651f  _free+0x77
>   0x00174474   0x174474
>   0x000dc172   0xdc172
>   0x000ce040   0xce040
>   0x0000b182   0xb182
>   0x001627fc   0x1627fc
>   0x0014edf2   0x14edf2
>   0x00009b41   0x9b41
>   0x0000d9cf   0xd9cf
>   0x0017589a   0x17589a
>  

Andris