This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch 2/2] [+doc] New -iex and -ix: -ex and -x before inferior load
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 25 Feb 2012 17:59:43 +0200
- Subject: Re: [patch 2/2] [+doc] New -iex and -ix: -ex and -x before inferior load
- References: <20120225134940.GC15155@host2.jankratochvil.net>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 25 Feb 2012 14:49:40 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -78,6 +78,13 @@ show breakpoint condition-evaluation
> condition evaluation mode. The use of this extension can be controlled
> via the "set remote conditional-breakpoints-packet" command.
>
> +* New command line options
> +
> +--init-command=FILE, -ix Like --init-command, -x but execute it
^^^^^^^^^^^^^^
You meant "--command", I believe.
> + before loading inferior.
> +--init-eval-command=COMMAND, -iex Like --eval-command=COMMAND, -ex but
> + execute it before loading inferior.
Is it really a good idea to have 2- or 3-letter short options? It
started with -nw and -nx, which might make sense, then we added -ex,
and now -ix and -iex? If noting else, this will prevent us from ever
having -e and -i.
How about if we don't have short versions of these at all?
> +@cindex @code{-ix}
> +Execute commands from file @var{file} before gdbinit files or inferior loading.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"before loading gdbinit files or the inferior" is better.
> +@cindex @code{-iex}
> +Execute a single @value{GDBN} command before gdbinit files or inferior loading.
Likewise.
> +Execute commands and command files specified by the @samp{-iex} and
> +@samp{-ix} options in their specified order. Usually you should use the
> +@samp{-ex} and @samp{-x} options instead but this way you can apply
^
A comma is missing before "but".
OK with those changes.
Thanks.