From: George Foot <mert0407 AT sable DOT ox DOT ac DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Tracking down where GPFs occur .  How? (DJGPP+Allegro)
Date: 4 Nov 1997 04:32:13 GMT
Organization: Oxford University, England
Lines: 24
Message-ID: <63m8gd$eop$1@news.ox.ac.uk>
References: <63m4mh$qjl$1 AT news DOT interlog DOT com>
NNTP-Posting-Host: sable.ox.ac.uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

On Tue, 04 Nov 97 03:36:41 GMT in comp.os.msdos.djgpp Gautam N. Lad
<gautam AT interlog DOT com> wrote:

: Hi,
: Is there any way to determine where a program is causing a GPF?
: I get all the code like General Protection Fault at eip=(whatever).
: and some other (unknown to me) stuff.

: Could this be used to pinpoint where in a program's source (hopefully a .CPP/.C 
: or .HPP/.H) it's happening?

If you compile your source files with the `-g' option, and don't strip
debugging symbols (don't use the `-s' option), you can type `symify
myprog.exe' while the crash dump is still on the screen, replacing
`myprog.exe' with the name of your program.

Incidentally, on this topic, why is it necessary to pass the name of
the executable image? The new stack trace contains the executable's
full path and filename; is this unreliable?

-- 
Regards,

george DOT foot AT merton DOT oxford DOT ac DOT uk