From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Bruno Larsen <blarsen@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/doc]: Updated manpages to be consistent with help
Date: Wed, 13 Oct 2021 16:50:10 +0300 [thread overview]
Message-ID: <83bl3tniel.fsf@gnu.org> (raw)
In-Reply-To: <20211013130409.10711-1-blarsen@redhat.com> (message from Bruno Larsen via Gdb-patches on Wed, 13 Oct 2021 10:04:09 -0300)
> Date: Wed, 13 Oct 2021 10:04:09 -0300
> From: Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
>
> Updated manpages to be consistent with help information provided by the
> binary. The main changes are Making all long-form options have '--',
> instead of a single '-' and added most of the missing options to the
> manpage.
Thanks. The replacement of '-' by '--' are mechanical and don't need
any approval.
Many other changes replace something like this:
Use @file{file} as SOMETHING.
with something like this:
Use file @file{somefile} as SOMETHING.
I must confess that I prefer the former form, because it makes the
text more concise and easier to read, by avoiding one more "file".
> -@item -nh
> +@item --directory=@var{DIR}
> +@itemx -d @var{DIR}
> +Add @var{DIR} to the path to search for source files.
The string inside @var{..} should never be upper-case. (Yes, I know
this was in the original text.)
Also, here I'd prefer
Add @var{directory} to the path to search for source files.
because "DIR" doesn't necessarily speak for its being a directory.
> -@item -cd=@var{directory}
> -Run @value{GDBN} using @var{directory} as its working directory,
> +@item --batch-silent
> +Run in batch mode, just like @option{--batch}, but totally silent. All @value{GDBN}
> +output is supressed (stderr is unaffected). This is much quieter than
^^
Two spaces between sentences, please.
> +This is particularly useful when using targets that give 'Loading section'
^^^^^^^^^^^^^^^^^
This should be in @samp, not in literal quotes.
> +Note that targets that give their ourpur via GDB, as opposed to writting
^^^
@value{GDBN}
> +directly to stdout, will also be made silent.
"stdout" should be in @code. Or use "standard output" instead.
> +@item --args @var{prog} [@var{arglist}]
> +Change interpretation of command line so that arguments following this
> +option are passed as arguments to the inferior. As an example, take
^^
Two spaces.
> +Will start GDB with @option{-q}, not printing the introductory message. On
^^^ ^^
@value{GDBN}, and two spaces.
> +Starts GDB with the introductory message, and passes the option to the inferior.
@value{GDBN}
> +@item --pid=@var{PID}
> +Attach GDB to an already running program, with the PID @var{PID}.
Likewise. Also, @var{PID} should be @var{pid}.
> +@item --configuration
> +Prints details about GDB configuration and then exit.
@value{GDBN}
> +@item --cd=@var{DIR}
> +Run @value{GDBN} using @var{DIR} as its working directory,
> instead of the current directory.
Please replace "DIR" with "directory".
> -@item -fullname
> +@item --data-directory=@var{DIR}
> +@item -D
> +Run @value{GDBN} using @var{DIR} as its data directory. The data
> +directory is where @value{GDBN} searches for its auxiliary files.
Likewise.
> -@item -b @var{bps}
> +@item -b @var{BAUDRATE}
Uppercase @var again.
> -@item -tty=@var{device}
> +@item -l @var{TIMEOUT}
> +Set timeout, in seconds, for remote debugging.
And here.
Thanks.
next prev parent reply other threads:[~2021-10-13 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 13:04 Bruno Larsen via Gdb-patches
2021-10-13 13:50 ` Eli Zaretskii via Gdb-patches [this message]
2021-10-13 15:03 ` Bruno Larsen via Gdb-patches
2021-10-13 15:30 ` Sergio Durigan Junior via Gdb-patches
2021-10-14 13:10 ` Bruno Larsen via Gdb-patches
2021-10-14 18:56 ` Philippe Waroquiers via Gdb-patches
2021-10-15 13:27 ` Bruno Larsen via Gdb-patches
2021-10-16 11:44 ` Philippe Waroquiers via Gdb-patches
2021-10-19 13:24 ` Bruno Larsen via Gdb-patches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bl3tniel.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox