Mail Archives: djgpp/1994/03/09/14:02:26
>You have probably been asked this question a thousand times so I apologize
>for having to ask it 1001 times. I recently installed DJGPP but according to
>the FAQ that was included, GDB has not been ported. I have alot of
>experience writing C programs for UNIX systems and have been using the
>symbolic debuggers provided in that environment. Are there any debuggers for
>DJGPP? If not, what are you using to debug programs written for DJGPP? I
>noticed some debugging capabilities in go32, but I don't know how to take
>advantage of it. Can you provide any help here, or know of a FAQ that I can
>get that would help?
Well, there is a full screen version of 'edebug' by Morten Welinder,
fsdb090.zip, available from omnigate.clarkson.edu:/pub/msdos/djgpp.
You'll need the sources for the old debugger, which are in 'djsrc111.zip'
to compile it.
I have to admit that the lack of a GDB-comparable debugger is one of the
biggest strikes against the DJGPP package. I have been known to transfer my
programs over to my Linux partition just to run GDB on them! Several
friends of mine have given up on DJGPP because of the lack of a symbolic
debugger.
BTW: To anyone who might want to port GDB -- I (for one) would consider
making a (modest) monetary donation to support someone to do this.
EMX, the other GNU C for MSDOS, apparently has GDB. I haven't tried it
though.
What might help in the interim though, for the non-experts here (like me),
are some tips on using the 'edebug' debugger. For example, how to translate
the symbolic ('mangled'?) names into real names from the code, what kind of
things to look for when your program bombs, etc. Obviously 'symify' is a
start. Anything to help those of us who don't know AT&T assembler that well yet.
Anyone willing to make a debugger tutorial?
Gordon
- Raw text -