Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2 2/3] gdb: process startup files and startup command line options
Date: Tue, 26 Jan 2021 17:22:44 +0200	[thread overview]
Message-ID: <83eei72057.fsf@gnu.org> (raw)
In-Reply-To: <99a396b1db7b7a6caacdcbd966236cd59fc6fc2b.1611653889.git.andrew.burgess@embecosm.com> (message from Andrew Burgess on Tue, 26 Jan 2021 09:48:12 +0000)

> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Tue, 26 Jan 2021 09:48:12 +0000
> 
> Adds the ability to process commands at a new phase during GDB's
> startup.  This phase is earlier than the current initialisation file
> processing, before GDB has produced any output.

Thanks.

> +* GDB will now load and process commands from ~/.config/gdb/gdbstartup
> +  or ~/.gdbstartup if these files are present.  These files are
> +  processed earlier than any of the previous initialization files and
> +  can affect parts of GDB's startup that previously had already been
> +  completed before the initialization files were read, for example
> +  styling of the initial GDB greeting.
> +
> +* GDB now has two new options "--startup-command" and
> +  "--startup-eval-command" with corresponding short options "-sx" and
> +  "-sex" that allow options (that would normally appear in a
> +  gdbstartup file) to be passed on the command line.

This part is OK.

> +@item -startup-command @var{file}
> +@itemx -sx @var{file}
> +@cindex @code{--startup-command}
> +@cindex @code{-sx}
> +Execute commands from file @var{file} as early as possible during the
> +initialization process, before any output is produced.
> +@xref{Startup}.
> +
> +@item -startup-eval-command @var{command}
> +@itemx -sex @var{command}
> +@cindex @code{--startup-eval-command}
> +@cindex @code{-sex}
> +Execute a single @value{GDBN} command as early as possible during the
> +initialization process, before any output is produced.

"As early as possible" could be taken as meaning there's something
non-deterministic in choosing the stage where these commands are
executed.  How about "very early in the initialization process"
instead?

> +The files processed are split into two categories @dfn{startup files}
> +and @dfn{initialization files}.
> +
> +The startup file is loaded as early as possible during

The first sentence above says "files", the second says "the file", as
if there's only one.  Which one is it?

(And the same issue with "as early as possible" as before.)

> +@value{GDBN}'s startup, before the interpreter (@pxref{Interpreters})
> +has been initialised, and before the default target (@pxref{Targets}
> +is initialised.  Only @code{set} or @code{source} commands should be

Our convention is to use the US English spellings, so please use
"initialized".

> +restrictions.  Only commands that can appear in a startup file shold
                                                                  ^^^^^
A typo there.

> +While on Apple hosts the locations searched are:

Such a sentence shouldn't start with "while".  I suggest "By
contrast," instead.

  reply	other threads:[~2021-01-26 15:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26  9:48 [PATCHv2 0/3] Adding startup files to GDB Andrew Burgess
2021-01-26  9:48 ` [PATCHv2 1/3] gdb: refactor the initialization file lookup code Andrew Burgess
2021-01-26 15:09   ` Simon Marchi via Gdb-patches
2021-01-26  9:48 ` [PATCHv2 2/3] gdb: process startup files and startup command line options Andrew Burgess
2021-01-26 15:22   ` Eli Zaretskii via Gdb-patches [this message]
2021-01-26 15:32     ` Simon Marchi via Gdb-patches
2021-01-26 15:30   ` Simon Marchi via Gdb-patches
2021-01-26  9:48 ` [PATCHv2 3/3] gdb: add "set startup-quietly" command Andrew Burgess
2021-01-26 15:12   ` Eli Zaretskii via Gdb-patches
2021-02-18 16:41 ` [PATCHv3 0/3] Adding startup files to GDB Andrew Burgess
2021-02-18 16:41   ` [PATCHv3 1/3] gdb: refactor the initialization file lookup code Andrew Burgess
2021-02-18 16:41   ` [PATCHv3 2/3] gdb: process early initialization files and command line options Andrew Burgess
2021-02-18 17:46     ` Eli Zaretskii via Gdb-patches
2021-03-24 12:10       ` Andrew Burgess
2021-03-24 17:17         ` Eli Zaretskii via Gdb-patches
2021-02-18 16:41   ` [PATCHv3 3/3] gdb: add "set startup-quietly" command Andrew Burgess
2021-02-18 17:32     ` Eli Zaretskii via Gdb-patches
2021-03-24 12:08       ` Andrew Burgess
2021-03-31 20:11   ` [PATCHv3 0/3] Adding startup files to GDB Andrew Burgess
2021-04-02 19:20     ` Tom Tromey

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=83eei72057.fsf@gnu.org \
    --to=gdb-patches@sourceware.org \
    --cc=andrew.burgess@embecosm.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