Date:	Sun, 2 Feb 2003 08:24:49 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc:	DJGPP developers <djgpp-workers AT delorie DOT com>
Subject:	Re: symify docs
In-Reply-To:	<10302012320.AA22101@clio.rice.edu>
Message-ID:	<Pine.SUN.3.91.1030202081922.19460A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sat, 1 Feb 2003, Charles Sandmann wrote:

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

Please use @option for command-line switches.

> If @command{bfdsymify} is installed
> @command{symify} will pass the arguments to @command{bfdsymify}.

I'd suggest a "@pindex bfdsymify" here.

> @command{symify} reads the debug information from the executable you
> specify on the command line (with .exe extension) and puts it after the

I think ".exe" should be in @file.

> @item -o output.dmp
> 
> Output to file.  @command{symify} copies the traceback plus symbolic

This is better written as:

  @item -o @var{output-file}

  Output to the specified file @var{output-file}.

> @item -i input.dmp
> 
> Input from file.  @command{symify} reads the stack trace from the file

Same here.

There are similar issues with FSDB docs.

> @command{fsdb} is a full screen debugger for DJGPP images.  See the internal
> help for more information on usage.

I think we should explain here (and in the edebug32 section) how to call 
up the internal help screen.  It's not at all obvious, IMHO.

I suggest to document the FSDB environment variables as well.

Thanks!

- Raw text -