From:	north AT iname DOT com
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: What about the registers????
Date:	Mon, 14 Jun 1999 07:37:29 GMT
Organization:	Deja.com - Share what you know. Learn what you don't.
Lines:	44
Message-ID:	<7k2bfp$j7d$1@nnrp1.deja.com>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 990608113154 DOT 4197E-100000 AT is>
NNTP-Posting-Host:	193.13.200.10
X-Article-Creation-Date:	Mon Jun 14 07:37:29 1999 GMT
X-Http-User-Agent:	Mozilla/4.08 [en] (WinNT; I ;Nav)
X-Http-Proxy:	1.0 x32.deja.com:80 (Squid/1.1.22) for client 193.13.200.10
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <Pine DOT SUN DOT 3 DOT 91 DOT 990608113154 DOT 4197E-100000 AT is>,
  djgpp AT delorie DOT com wrote:
>
> 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.
>

Can You explain this for me then:
While taking your advice and debugged whith a couple of printf's and
using the stack window in Rhide I found that the GPF was caused by
a cfree(*pointer)-function.

'call frame traceback
 in function free+275
 in function cfree+12
 in function '

This program was linked with the libc-library ditrubuted in djdev202.
So i blew the dust of from the old libc-library found in djdev201 and
linked it with the program, and now it works without any GPF's
???


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

- Raw text -