Sender:	rich AT phekda DOT freeserve DOT co DOT uk
Message-ID:	<3E3CF19E.21CAB8F3@phekda.freeserve.co.uk>
Date:	Sun, 02 Feb 2003 10:23:26 +0000
From:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer:	Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language:	de,fr
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: symify docs
References:	<10302012320 DOT AA22101 AT clio DOT rice DOT edu>
Reply-To:	djgpp-workers AT delorie DOT com

Hello.

Charles Sandmann wrote:
> Plan to commit soon

It looks good to me, but:

[snip]
> @node symify, edebug32, , Top
> @chapter @command{symify}
> @pindex symify
> 
> Usage: @kbd{symify [-o output.dmp] [-i input.dmp] progname.exe}
> 
> @command{symify} is a utility that adds procedure names and source line
> numbers to the call frame traceback displayed on the screen when a program
> aborts.  The default behavior is to add the extra information to the
> screen, but input or output from files can be specified with the
> @code{-o} and @code{-i} switches.  If @command{bfdsymify} is installed
> @command{symify} will pass the arguments to @command{bfdsymify}.

Perhaps you could mention that bfdsymify works the same way as symify. Also
why would you want to use bfdsymify? And where do you get it? How about
splitting the text about bfdsymify into a separate paragraph like this:

    If @command{bfdsymify} is installed @command{symify} will pass the
    arguments to @command{bfdsymify}.  @command{bfdsymify} can cope with
    more debugging formats than @command{symify}.  It takes the same
    arguments as @command{bfdsymify}.  To get @command{bfdsymify},
    please install the GNU debugger, gdb (@pxref{gdb}).

[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.

Thanks, bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

- Raw text -