Mail Archives: djgpp-workers/2003/02/02/07:24:13
Richard Dawe wrote:
> Charles Sandmann wrote:
>
> [snip]
>
> > @node edebug32, fsdb, symify, Top
> > @chapter @command{edebug32}
> > @pindex edebug32
> >
> > Usage: @kbd{edebug32 debug-image.exe [args to debug-image]}
> >
> > @command{edebug32} is a simple debugger for DJGPP images. See the internal
> > help for more information on usage. @command{edebug32} is an expert's
> > debugger and does not support newer debugging formats. It is recommended
> > that new users try one of the other more powerful or easy to use debuggers.
>
> I think "easy to use" should be hyphenated: easy-to-use. Also, perhaps you
> could suggest gdb?
>
> ...easy to use debuggers, such as the GNU debugger, gdb (@pxref{gdb}).
>
> >
> > @c -----------------------------------------------------------------------------
> > @node fsdb, , edebug32, Top
> > @chapter @command{fsdb}
> > @pindex fsdb
> >
> > Usage: @kbd{fsdb [-p path] [-d] [-s setup] debug-image.exe [args]}
> >
> > @command{fsdb} is a full screen debugger for DJGPP images. See the internal
> > help for more information on usage. @command{fsdb} is not actively
> > maintained and does not support newer debugging formats. It is recommended
> > that new users try one of the other newer debuggers.
> [snip]
>
> Again, maybe you could suggest gdb here.
I didn't realize fsdb and edebug32 existed before seeing this.
They only appear in passing in the faq AFAICT.
How about specifying specifically what debug formats ARE
supported. fsdb appears particularly handy, since AFAIK DJGPP gdb
doesn't have an equivalent text window interface.
--
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net> USE worldnet address!
- Raw text -