From:	Damian Frank <damianf AT WPI DOT EDU>
Subject:	Re: Debuggers
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Date:	Fri, 19 May 1995 12:34:21 -0400 (EDT)

> If you're looking for a source level debugging environment like CV or 
> Borland C, you'll be dissapointed.  GDB provides source code information
> i.e it will give you the line that a particular section of the assembler
> corresponds to (this is implicit in the symbol table of the code), but any
> form of stepping at source level is not available.  The GDB does not
> present itself very well, everything being command line driven (i.e no
> menus etc..).  

What ARE you talking about?  It's quite possible to step through code at the
source level with GDB - even with DJGPP.  All you have to do is compile your
code with -g, and then you can set breakpoints with the break command, and
then step or trace through with next or trace.  GDB is quite versatile. 
While it's not as easy to use as Borland's Turbo Debugger (or the IDE
versions in Turbo Pascal and Borland C, which are the same as Turbo Debugger
in most respects), and doesn't have pull-down menus, or different data
windows and such, in general, it doesn't lack any of their functionality.

-- 
  ________________   ________________________________________________
 /  Damian Frank  \ /   "The dead have risen, and they're voting     \
|  damianf AT wpi DOT edu |     Republican!"                                |
|    WPI CS '97    |                          Bart Simpson           |
 \________________/ \_______________________________________________/

- Raw text -