Date: Wed, 17 Dec 1997 11:49:11 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Chris Frolik <frolikcc AT indy DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: Getting useful information from the traceback
In-Reply-To: <3495F8E1.1C87@indy.net>
Message-ID: <Pine.SUN.3.91.971217114709.28294G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 15 Dec 1997, Chris Frolik wrote:

> However, now that I know *where* the problem occurs, I am still not
> sure *why*.  Is there any useful information I can get out of the
> traceback to tell me what's happening?  For example, am I dividing by
> zero, writing beyond the bounds of an array, etc?  Is there any way to
> determine this?  Here is the traceback:
> 
> Shutting down Allegro
> Exiting due to signal SIGSEGV
> Page fault at eip=0000e5c7, error=0006
> eax=fff607b8 ebx=00000000 ecx=c6047600 edx=00000000 esi=7fc7c0bb
> edi=00000000
> ebp=fff608dc esp=fff607b8 program=C:\CHRIS\CPP\SPACEWAR\MAPED.EXE

Error 0006 means that you are trying to write to an address that isn't 
present.  For example, garbled or NULL pointer.