Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: [PATCHv3 0/3] Adding startup files to GDB
Date: Thu, 18 Feb 2021 16:41:01 +0000	[thread overview]
Message-ID: <cover.1613666280.git.andrew.burgess@embecosm.com> (raw)
In-Reply-To: <cover.1611653889.git.andrew.burgess@embecosm.com>

Changes since v2:

Patch #1

 - Make use of gdb::optional as Simon suggested.

Patch #2

 - Rename 'startup' files to 'earlyinit' files as Simon suggested.

 - Extensive documentation changes to address Eli's feedback, and to
   reflect the naming change.

 - Renamed the test script to reflect the naming change.

Patch #3

 - Updates to the documentation to (I hope) address Eli's feedback.


Thanks,
Andrew

---

Andrew Burgess (2):
  gdb: refactor the initialization file lookup code
  gdb: process early initialization files and command line options

Tom Tromey (1):
  gdb: add "set startup-quietly" command

 gdb/ChangeLog                              |  33 +++
 gdb/NEWS                                   |  19 ++
 gdb/config.in                              |   3 +
 gdb/configure                              |   6 +
 gdb/configure.ac                           |   3 +
 gdb/doc/ChangeLog                          |  14 ++
 gdb/doc/gdb.texinfo                        | 125 +++++++++-
 gdb/main.c                                 | 253 +++++++++++++++------
 gdb/testsuite/ChangeLog                    |  11 +
 gdb/testsuite/gdb.base/early-init-file.c   |  22 ++
 gdb/testsuite/gdb.base/early-init-file.exp | 149 ++++++++++++
 gdb/testsuite/lib/gdb-utils.exp            |   1 +
 gdb/top.c                                  |  33 +++
 gdb/top.h                                  |   5 +
 14 files changed, 603 insertions(+), 74 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/early-init-file.c
 create mode 100644 gdb/testsuite/gdb.base/early-init-file.exp

-- 
2.25.4


  parent reply	other threads:[~2021-02-18 16:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26  9:48 [PATCHv2 " 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
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 ` Andrew Burgess [this message]
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=cover.1613666280.git.andrew.burgess@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.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