From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, dje@google.com, brobecker@adacore.com,
gdb-patches@sourceware.org
Subject: regroup --help text (was: Re: [PATCH] Display configuration details in --help)
Date: Fri, 12 Apr 2013 16:39:00 -0000 [thread overview]
Message-ID: <51681C92.4000502@redhat.com> (raw)
In-Reply-To: <83bo9k9ifl.fsf@gnu.org>
On 04/12/2013 11:01 AM, Eli Zaretskii wrote:
>> Date: Fri, 12 Apr 2013 11:58:48 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: palves@redhat.com, dje@google.com, brobecker@adacore.com, gdb-patches@sourceware.org
>>
>> I will take a shot on regrouping the --help text later.
>
> Howe about the following (if accepted, I will write a patch to
> implement this):
This is great. Many thanks.
>
> This is the GNU debugger. Usage:
>
> gdb [options] [executable-file [core-file or process-id]]
> gdb [options] --args executable-file [inferior-arguments ...]
>
> Selection of debuggee and its files:
>
> --args Arguments after executable-file are passed to inferior.
> --core=COREFILE Analyze the core dump COREFILE.
> --exec=EXECFILE Use EXECFILE as the executable.
> --pid=PID Attach to running process PID.
> --directory=DIR Search for source files in DIR.
> --se=FILE Use FILE as symbol file and executable file.
> --symbols=SYMFILE Read symbols from SYMFILE.
> --readnow Fully read symbol files on first access.
> --write Set writing into executable and core files.
>
> Initial commands and command files:
>
> --command=FILE, -x Execute GDB commands from FILE.
> --init-command=FILE, -ix
> Like -x but execute commands before loading inferior.
> --eval-command=COMMAND, -ex
> Execute a single GDB command.
> May be used multiple times and in conjunction
> with --command.
> --init-eval-command=COMMAND, -iex
> Like -ex but before loading inferior.
> --nh Do not read ~/.gdbinit.
> --nx Do not read any .gdbinit files in any directory.
>
> Output and user interface control:
>
> --epoch Output information used by epoch emacs-GDB interface.
> --fullname Output information used by emacs-GDB interface.
> --interpreter=INTERP
> Select a specific interpreter / user interface
> --tty=TTY Use TTY for input/output by the program being debugged.
> -w Use the GUI interface.
> --nw Do not use the GUI interface.
> --tui Use the text-mode user interface
> --dbx DBX compatibility mode.
> --xdb XDB compatibility mode.
> --quiet Do not print version number on startup.
>
> Miscellaneous options:
>
> -b BAUDRATE Set serial port baud rate used for remote debugging.
> --batch Exit after processing options.
> --batch-silent Like --batch, but suppress all gdb stdout output.
> --return-child-result
> GDB exit code will be the child's exit code.
> --cd=DIR Change current directory to DIR.
> -l TIMEOUT Set timeout in seconds for remote debugging.
>
> --configuration Print details about GDB configuration and then exit.
> --help Print this message and then exit.
> --version Print version information and then exit.
>
I'd suggest splitting the miscellaneous section as:
Operating modes:
--batch Exit after processing options.
--batch-silent Like --batch, but suppress all gdb stdout output.
--return-child-result
GDB exit code will be the child's exit code.
--configuration Print details about GDB configuration and then exit.
--help Print this message and then exit.
--version Print version information and then exit.
Remote debugging options:
-b BAUDRATE Set serial port baud rate used for remote debugging.
-l TIMEOUT Set timeout in seconds for remote debugging.
Other options:
--cd=DIR Change current directory to DIR.
--
Pedro Alves
next prev parent reply other threads:[~2013-04-12 14:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 17:46 [PATCH] Display configuration details in --help Eli Zaretskii
2013-03-21 18:00 ` Doug Evans
2013-03-21 18:25 ` Pedro Alves
2013-03-21 18:29 ` Joel Brobecker
2013-03-21 18:44 ` Eli Zaretskii
2013-03-21 19:11 ` Joel Brobecker
2013-03-21 20:39 ` Eli Zaretskii
2013-03-21 20:55 ` Joel Brobecker
2013-03-21 21:17 ` Tom Tromey
2013-03-21 22:23 ` Eli Zaretskii
2013-04-09 19:31 ` Eli Zaretskii
2013-04-09 19:46 ` Doug Evans
2013-04-09 20:04 ` Eli Zaretskii
2013-04-09 23:33 ` Doug Evans
2013-04-10 0:12 ` Pedro Alves
2013-04-10 0:48 ` Eli Zaretskii
2013-04-10 2:51 ` Doug Evans
2013-04-10 4:41 ` Eli Zaretskii
2013-04-11 2:41 ` Doug Evans
2013-04-11 1:20 ` Tom Tromey
2013-04-11 1:24 ` Pedro Alves
2013-04-11 2:43 ` Tom Tromey
2013-04-12 12:50 ` Eli Zaretskii
2013-04-12 14:43 ` Eli Zaretskii
2013-04-12 16:39 ` Pedro Alves [this message]
2013-06-22 11:31 ` regroup --help text in --help) Eli Zaretskii
2013-06-25 19:30 ` Pedro Alves
2013-07-06 7:35 ` Eli Zaretskii
2013-04-12 20:50 ` [PATCH] Display configuration details in --help Tom Tromey
2013-04-14 14:17 ` Joel Brobecker
2013-04-16 1:34 ` Doug Evans
2013-04-16 9:46 ` regroup --help text Eli Zaretskii
2013-04-17 8:10 ` Doug Evans
2013-04-17 12:28 ` Eli Zaretskii
2013-04-14 14:16 ` [PATCH] Display configuration details in --help Doug Evans
2013-04-10 0:38 ` Eli Zaretskii
2013-04-10 3:06 ` Doug Evans
2013-04-10 4:44 ` Eli Zaretskii
2013-03-21 18:53 ` Eli Zaretskii
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=51681C92.4000502@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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