From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: [PATCHv4 0/2] Restore thread and frame patches
Date: Fri, 6 Nov 2020 23:02:06 +0000 [thread overview]
Message-ID: <cover.1604703416.git.andrew.burgess@embecosm.com> (raw)
In-Reply-To: <20201008095950.GN605036@embecosm.com>
V4 is a rebase of v3 to take account of a recent commit by Pedro. As
a result I've dropped patch #1 from the v3 series. The remaining two
patches have a couple of minor updates as a result, but Pedro's recent
commit basically replaced my patch #1.
[ I think the v3 patch #1 did add value that wasn't included in
Pedro's commit, but I'd rather this series just focus on the
remaining two patches for now. I might resurrect the old #1 at a
later date. ]
No changes to documentation in this iteration.
Retested, with no regressions.
Thanks,
Andrew
---
Andrew Burgess (2):
gdb: Restore previously selected thread when switching inferior
gdb: Track the current frame for each thread
gdb/ChangeLog | 34 ++
gdb/NEWS | 19 +
gdb/doc/ChangeLog | 14 +
gdb/doc/gdb.texinfo | 42 ++-
gdb/frame.c | 26 ++
gdb/gdbthread.h | 13 +-
gdb/inferior.c | 58 ++-
gdb/inferior.h | 10 +
gdb/testsuite/ChangeLog | 10 +
.../gdb.threads/restore-selected-frame.c | 85 +++++
.../gdb.threads/restore-selected-frame.exp | 336 ++++++++++++++++++
gdb/testsuite/gdb.threads/restore-thread.c | 248 +++++++++++++
gdb/testsuite/gdb.threads/restore-thread.exp | 219 ++++++++++++
gdb/thread.c | 61 +++-
14 files changed, 1160 insertions(+), 15 deletions(-)
create mode 100644 gdb/testsuite/gdb.threads/restore-selected-frame.c
create mode 100644 gdb/testsuite/gdb.threads/restore-selected-frame.exp
create mode 100644 gdb/testsuite/gdb.threads/restore-thread.c
create mode 100644 gdb/testsuite/gdb.threads/restore-thread.exp
--
2.25.4
next prev parent reply other threads:[~2020-11-06 23:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 22:24 [PATCHv3 0/3] " Andrew Burgess
2020-09-25 22:24 ` [PATCHv3 1/3] gdb: unify two copies of restore_selected_frame Andrew Burgess
2020-09-25 22:24 ` [PATCHv3 2/3] gdb: Restore previously selected thread when switching inferior Andrew Burgess
2020-09-26 6:09 ` Eli Zaretskii via Gdb-patches
2020-09-25 22:24 ` [PATCHv3 3/3] gdb: Track the current frame for each thread Andrew Burgess
2020-09-26 6:16 ` Eli Zaretskii via Gdb-patches
2020-09-26 8:31 ` Andreas Schwab
2020-09-26 8:54 ` Eli Zaretskii via Gdb-patches
2020-10-08 9:59 ` [PATCHv3 0/3] Restore thread and frame patches Andrew Burgess
2020-11-06 23:02 ` Andrew Burgess [this message]
2020-11-06 23:02 ` [PATCHv4 1/2] gdb: Restore previously selected thread when switching inferior Andrew Burgess
2020-11-09 15:02 ` Aktemur, Tankut Baris via Gdb-patches
2020-11-06 23:02 ` [PATCHv4 2/2] gdb: Track the current frame for each thread Andrew Burgess
2020-11-12 11:59 ` [PATCHv5 0/2] Restore thread and frame patches Andrew Burgess
2020-12-10 11:39 ` [PATCHv6 " Andrew Burgess
2020-12-10 11:39 ` [PATCHv6 1/2] gdb: Restore previously selected thread when switching inferior Andrew Burgess
2020-12-10 11:39 ` [PATCHv6 2/2] gdb: Track the current frame for each thread Andrew Burgess
2020-12-18 8:43 ` Aktemur, Tankut Baris via Gdb-patches
2021-01-04 15:07 ` Andrew Burgess
2021-01-04 16:08 ` Eli Zaretskii via Gdb-patches
2021-01-07 10:25 ` [PATCHv6 0/2] Restore thread and frame patches Andrew Burgess
2021-02-12 18:20 ` [PATCHv7 " Andrew Burgess
2021-02-12 18:20 ` [PATCHv7 1/2] gdb: Restore previously selected thread when switching inferior Andrew Burgess
2021-02-12 18:20 ` [PATCHv7 2/2] gdb: Track the current frame for each thread Andrew Burgess
2021-03-23 11:13 ` [PATCHv8] gdb: Restore previously selected thread when switching inferior Andrew Burgess
2021-03-23 11:43 ` Eli Zaretskii via Gdb-patches
2020-11-12 11:59 ` [PATCHv5 1/2] " Andrew Burgess
2020-11-12 11:59 ` [PATCHv5 2/2] gdb: Track the current frame for each thread Andrew Burgess
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.1604703416.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