From:	"Johan Venter" <jventer AT writeme DOT com>
Newsgroups:	comp.os.msdos.djgpp
References:	<7jg9v2$l6l$1 AT nnrp1 DOT deja DOT com>
Subject:	Re: What about the registers????
Lines:	25
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2014.211
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2014.211
Message-ID:	<zDZ63.6616$PN5.19455@newsfeeds.bigpond.com>
Date:	Mon, 7 Jun 1999 22:42:43 +1000
NNTP-Posting-Host:	203.40.83.5
X-Trace:	newsfeeds.bigpond.com 928802399 203.40.83.5 (Tue, 08 Jun 1999 10:39:59 EST)
NNTP-Posting-Date:	Tue, 08 Jun 1999 10:39:59 EST
Organization:	Telstra BigPond Internet Services (http://www.bigpond.com)
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Call frame traceback EIPs:
>   0x00001016

Try running:
    symify <exe name>

while this information is still on the screen. Post the result.
Also, try compiling with the -g option and run through a debugger.

Almost always, a GPF is caused by the use of un initialised memory
(ie pointers that haven't been malloc'd). symify might help return the
name of the function being called at the time of the crash.

Also, are you running under Windows? The Windows DPMI server
doesn't catch NULL pointer exceptions, but rather lets them linger on
until such time as they corrupt memory in use by Windows.

--
Johan Venter
ICQ 3643877
Visit "The TPU DJGPP Interest Group":
http://surf.to/djgppig

- Raw text -