From: Bruno Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Cc: eliz@gnu.org, Bruno Larsen <blarsen@redhat.com>
Subject: [PATCH v2 0/4] Small changes to "list" command
Date: Tue, 20 Jun 2023 17:52:56 +0200 [thread overview]
Message-ID: <20230620155259.2476415-1-blarsen@redhat.com> (raw)
I decided to tackle PR cli/30497, and while doing so, Andrew mentioned
that it would also be nice if we could explicitly ask GDB to print the
current location, so I also decided to add that into a series. The first
patch is just some groundwork preparation to make the rest smooth. On
the second pass, I realized that 'list +' isn't properly documented, so
I added it to the docs as well
Changes from v1:
* added new arguments to the docs
* Added patch 4, completely new.
* Fixed wording, per Eli's suggestions.
Bruno Larsen (4):
gdb/cli: Factor out code to list lines for the first time
gdb/cli: Improve UX when using list with no args
gdb/cli: add '.' as an argument for 'list' command
gdb/doc: document '+' argument for 'list' command
gdb/NEWS | 11 ++++
gdb/cli/cli-cmds.c | 95 +++++++++++++++++++++++++++------
gdb/doc/gdb.texinfo | 17 +++++-
gdb/source.c | 18 +++++++
gdb/source.h | 4 ++
gdb/testsuite/gdb.base/list.exp | 46 ++++++++++++++--
gdb/testsuite/gdb.base/list1.c | 2 +-
7 files changed, 170 insertions(+), 23 deletions(-)
--
2.40.1
next reply other threads:[~2023-06-20 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 15:52 Bruno Larsen [this message]
2023-06-20 15:52 ` [PATCH v2 1/4] gdb/cli: Factor out code to list lines for the first time Bruno Larsen
2023-06-20 15:52 ` [PATCH v2 2/4] gdb/cli: Improve UX when using list with no args Bruno Larsen
2023-06-20 16:19 ` Eli Zaretskii
2023-06-20 15:52 ` [PATCH v2 3/4] gdb/cli: add '.' as an argument for 'list' command Bruno Larsen
2023-06-20 16:22 ` Eli Zaretskii
2023-06-20 15:53 ` [PATCH v2 4/4] gdb/doc: document '+' " Bruno Larsen
2023-06-20 16:20 ` 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=20230620155259.2476415-1-blarsen@redhat.com \
--to=blarsen@redhat.com \
--cc=eliz@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).