From: Pedro Alves <palves@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Tom Tromey <tromey@redhat.com>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Display configuration details in --help
Date: Wed, 10 Apr 2013 00:12:00 -0000 [thread overview]
Message-ID: <51645982.8050904@redhat.com> (raw)
In-Reply-To: <CADPb22SQaWrBd4MOmMqFaAMc=KnX15hd=be3Ta_u3wGg=HGmXQ@mail.gmail.com>
On 04/09/2013 06:53 PM, Doug Evans wrote:
> On Tue, Apr 9, 2013 at 10:37 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>>> > fputs_unfiltered (_("\
>>> > --version Print version information and then exit.\n\
>>> > + --configuration Print details about GDB configuration and then exit.\n\
>>> > -w Use a window interface.\n\
>>> > --write Set writing into executable and core files.\n\
>>> > --xdb XDB compatibility mode.\n\
>>>
>>> The options here are (mostly) sorted alphabetically.
>>
>> Except where they aren't:
There's a pattern.
>>
>> --args Arguments after executable-file are passed to inferior
>> -b BAUDRATE Set serial port baud rate used for remote debugging.
>> --batch Exit after processing options.
>> --batch-silent As for --batch, but suppress all gdb stdout output.
>> >>> --return-child-result
Related to --batch.
>> GDB exit code will be the child's exit code.
>> --cd=DIR Change current directory to DIR.
>> --command=FILE, -x Execute GDB commands from FILE.
>> >>> --eval-command=COMMAND, -ex
>> Execute a single GDB command.
>> May be used multiple times and in conjunction
>> with --command.
>> >>> --init-command=FILE, -ix Like -x but execute it before loading inferior.
>> >>> --init-eval-command=COMMAND, -iex Like -ex but before loading inferior.
All these are related to --command.
>> >>> --core=COREFILE Analyze the core dump COREFILE.
Remove the ones above related to --command, and this one's
actually in place.
>> >>> --pid=PID Attach to running process PID.
--pid is kind of a cousin of --core, due to how BAR is
handled in "gdb FOO BAR".
>> --dbx DBX compatibility mode.
>> --directory=DIR Search for source files in DIR.
>> --epoch Output information used by epoch emacs-GDB interface.
>> --exec=EXECFILE Use EXECFILE as the executable.
>> --fullname Output information used by emacs-GDB interface.
>> --help Print this message.
>> --interpreter=INTERP
>> Select a specific interpreter / user interface
>> -l TIMEOUT Set timeout in seconds for remote debugging.
>> --nw Do not use a window interface.
>> --nx Do not read .gdbinit file.
>> --quiet Do not print version number on startup.
>> --readnow Fully read symbol files on first access.
>> --se=FILE Use FILE as symbol file and executable file.
>> --symbols=SYMFILE Read symbols from SYMFILE.
>> --tty=TTY Use TTY for input/output by the program being debugged.
>> --version Print version information and then exit.
>> -w Use a window interface.
>> --write Set writing into executable and core files.
>> --xdb XDB compatibility mode.
>>
>> Again, I'm not really wedded to the place where I inserted the new
>> option, but please tell me near which 'c' option to put it instead ;-).
>
> Right after --command works for me.
So if you imagine a right indent in the grouped options, the
list is actually sorted, so that'd break the existing logic. I'd suggest
either right after --version; right after --help; right before --core, or
a wholesale reevaluation of the current grouping (either sort all
alphabetically, or break "Options:" into groups).
--
Pedro Alves
next prev parent reply other threads:[~2013-04-09 18:41 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 17:46 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 [this message]
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 ` regroup --help text (was: Re: [PATCH] Display configuration details in --help) Pedro Alves
2013-06-22 11:31 ` regroup --help text " 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=51645982.8050904@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