From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: lsix@lancelotsix.com, Lancelot SIX <lancelot.six@amd.com>
Subject: [PATCH 0/3] Varobj re_set clanup
Date: Thu, 4 Aug 2022 14:02:28 +0100 [thread overview]
Message-ID: <20220804130231.2126565-1-lancelot.six@amd.com> (raw)
This series is a follow-up to this series:
https://sourceware.org/pipermail/gdb-patches/2022-August/191172.html
Patch 1 of the original series has already been merged.
Patch 2 of the original series is replaced by patch 2 of this series which is
much cleaner. Patch 1 and 3 are meant to simplify varobj lifecycle.
All feedbacks are welcome.
Best,
Lancelot.
Lancelot SIX (2):
gdb/varobj: Do not invalidate locals in varobj_invalidate_iter
gdb/varobj: Only re-evaluate invalid globals durin re_set
Tom de Vries (1):
gdb/varobj: Reset varobj after relocations have been computed
gdb/symfile.c | 6 +--
.../gdb.mi/mi-var-invalidate-shlib.exp | 42 ++++++++++++++++---
gdb/testsuite/gdb.mi/mi-var-invalidate.exp | 4 +-
gdb/varobj.c | 38 +++++------------
gdb/varobj.h | 5 ++-
5 files changed, 57 insertions(+), 38 deletions(-)
base-commit: f74a5e6f2ed5180ce28d6478a6d7a7a1982c5d43
--
2.34.1
next reply other threads:[~2022-08-04 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 13:02 Lancelot SIX via Gdb-patches [this message]
2022-08-04 13:02 ` [PATCH 1/3] gdb/varobj: Do not invalidate locals in varobj_invalidate_iter Lancelot SIX via Gdb-patches
2022-08-05 15:03 ` Tom de Vries via Gdb-patches
2022-08-04 13:02 ` [PATCH 2/3] gdb/varobj: Reset varobj after relocations have been computed Lancelot SIX via Gdb-patches
2022-08-09 10:55 ` Tom de Vries via Gdb-patches
2022-08-04 13:02 ` [PATCH 3/3] gdb/varobj: Only re-evaluate invalid globals during re_set Lancelot SIX via Gdb-patches
2022-08-09 10:55 ` Tom de Vries via Gdb-patches
2022-08-11 14:07 ` Lancelot SIX via Gdb-patches
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=20220804130231.2126565-1-lancelot.six@amd.com \
--to=gdb-patches@sourceware.org \
--cc=lancelot.six@amd.com \
--cc=lsix@lancelotsix.com \
/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