Date: Tue, 8 Jun 1999 11:34:55 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Johan Venter <jventer AT writeme DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: What about the registers????
In-Reply-To: <zDZ63.6616$PN5.19455@newsfeeds.bigpond.com>
Message-ID: <Pine.SUN.3.91.990608113154.4197E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 7 Jun 1999, Johan Venter wrote:

> > Call frame traceback EIPs:
> >   0x00001016
> 
> Try running:
>     symify <exe name>
> 
> while this information is still on the screen.

This is in general the right thing to do, but in this case it probably 
won't help.  The EIP value (0x1016) is too low to be correct, as I 
explain in my other message in this thread.  So symify won't add anything 
useful to this mystery.

Bad EIP values are usually caused by some code that corrupts the stack, 
so that when a function tries to return, it pops garbage from the stack 
instead of the return address, and then GPFaults.