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/2] Fix regressions in varobj recreation
Date: Tue, 2 Aug 2022 13:47:22 +0100 [thread overview]
Message-ID: <20220802124724.284096-1-lancelot.six@amd.com> (raw)
Hi,
Tom de Vries noticed that a series I merged recently
(https://sourceware.org/pipermail/gdb-patches/2022-July/191085.html)
introduced regressions on some systems (reported in PR/29426).
This series aims at fixing those issues.
Patch #2 of the series is mostly about relaxing the testcase as I do not
see a way to "fix" the actual divergence of behavior of the tescase when
debugging PIE/non-PIE executable (see patch's description). Alternative
approaches are more than welcome.
Best,
Lancelot.
Lancelot SIX (2):
gdb: Fix regression in varobj recreation
gdb/testsuite: Accept PIE/noPIE programs in
gdb.mi/mi-var-invalidate-shlib.exp
gdb/testsuite/gdb.mi/mi-var-invalidate-shlib.exp | 2 +-
gdb/varobj.c | 9 +++++++--
2 files changed, 8 insertions(+), 3 deletions(-)
base-commit: 976f16630b1f7421d6693011333cf0f51417c498
--
2.34.1
next reply other threads:[~2022-08-02 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 12:47 Lancelot SIX via Gdb-patches [this message]
2022-08-02 12:47 ` [PATCH 1/2] gdb: Fix regression " Lancelot SIX via Gdb-patches
2022-08-02 13:26 ` Tom de Vries via Gdb-patches
2022-08-03 9:06 ` Six, Lancelot via Gdb-patches
2022-08-02 12:47 ` [PATCH 2/2] gdb/testsuite: Accept PIE/noPIE programs in gdb.mi/mi-var-invalidate-shlib.exp Lancelot SIX via Gdb-patches
2022-08-02 15:45 ` Tom de Vries via Gdb-patches
2022-08-03 9:35 ` Six, Lancelot via Gdb-patches
2022-08-03 11:51 ` Tom de Vries via Gdb-patches
2022-08-03 13:23 ` Six, Lancelot 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=20220802124724.284096-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