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: [PATCH 0/3] Changes to 'maint info sections'
Date: Fri,  5 Feb 2021 21:29:08 +0000	[thread overview]
Message-ID: <cover.1612560410.git.andrew.burgess@embecosm.com> (raw)

Patch #1 - some refactoring of the testsuite.

Patch #2 - fixes a problem I have with 'maint info sections' not
           giving me the results I need.

Patch #3 - add command options and command completion for 'maint info
           sections'.

---

Andrew Burgess (3):
  gdb/testsuite: split 'maint info sections' tests to a new file
  gdb: 'maint info sections' - handle the no executable case
  gdb: change 'maint info section' to use command options

 gdb/ChangeLog                                 |  24 ++
 gdb/NEWS                                      |   5 +
 gdb/doc/ChangeLog                             |   5 +
 gdb/doc/gdb.texinfo                           |  29 +-
 gdb/maint.c                                   | 322 ++++++++++--------
 gdb/testsuite/ChangeLog                       |  18 +
 .../gdb.base/maint-info-sections.exp          | 184 ++++++++++
 gdb/testsuite/gdb.base/maint.exp              |  87 -----
 8 files changed, 435 insertions(+), 239 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/maint-info-sections.exp

-- 
2.25.4


             reply	other threads:[~2021-02-05 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 21:29 Andrew Burgess [this message]
2021-02-05 21:29 ` [PATCH 1/3] gdb/testsuite: split 'maint info sections' tests to a new file Andrew Burgess
2021-02-08 19:28   ` Tom Tromey
2021-02-05 21:29 ` [PATCH 2/3] gdb: 'maint info sections' - handle the no executable case Andrew Burgess
2021-02-08 19:29   ` Tom Tromey
2021-02-05 21:29 ` [PATCH 3/3] gdb: change 'maint info section' to use command options Andrew Burgess
2021-02-06  7:16   ` Eli Zaretskii via Gdb-patches
2021-02-08 19:32   ` 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.1612560410.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