Mail Archives: djgpp/1996/11/13/11:07:06
Martin..... <beable AT magna DOT com DOT au> wrote:
: G'day,
: I am in the middle of writing a couple of test programs using
: DJGPP(a dam fine compiler I might add) and was wondering if there
: was any way of having a post portem debugging environment. I'm
: talking about something like what the old modula-2 compilers used to
: have, where if an unexpected crash occured, the compiled program
: would write out a dump file which could later be analized with a
: debug version of the code.
: I was reading thru the notes that came with Quake, (since id
: used DJGPP to write it I was looking for clues). I found mention of
: the that the bug reports required the eight-digit number which comes
: after the eip=. I take it that this comes from Charles Sandman's
: DPMI.
: Of what value is the 'eip=' number and is this a pointer or
: clue as to what could have gone wrong in the program?? Is there any
: other method of debugging a DJGPP executable after the fact??
The register values and the stack trace give some indication on where
the error happened (address) and how the function was called that the
error caused. There is a tool included in the djgpp that converts
these addresses to function names based on the symbols stored in the
executable (symify). Core dumps like on unix are currently not support
AFAIK, but you should be able to run your programs inside gdb and then
analyse the location of the crash (that is, if the error is
reproducable :-).
bye, Alexander
--
Alexander Lehmann, | "On the Internet,
alex AT hal DOT rhein-main DOT de (MIME, NeXT) | nobody knows
lehmann AT mathematik DOT th-darmstadt DOT de (MIME) | you're a dog."
<URL:http://home.pages.de/~lehmann/>
- Raw text -