From: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/2] "info locals" for clang-compiled inlined functions
Date: Wed, 14 Apr 2021 10:14:29 +0200 [thread overview]
Message-ID: <cover.1618387702.git.tankut.baris.aktemur@intel.com> (raw)
Hi,
This is the v2 of
https://sourceware.org/pipermail/gdb-patches/2021-February/176203.html
The revision includes:
* an additional patch to recognize DW_OP_fbreg as a location op in the
testsuite's Dwarf assembler.
* a new test that uses the Dwarf assembler.
* minor fixes that Simon Marchi commented on for v1.
Regards
Baris
Tankut Baris Aktemur (2):
testsuite, gdb: recognize DW_OP_fbreg in lib/dwarf.exp
gdb/dwarf2: fix "info locals" for clang-compiled inlined functions
gdb/dwarf2/read.c | 49 ++++++-
.../dw2-inline-with-lexical-scope.c | 47 ++++++
.../dw2-inline-with-lexical-scope.exp | 137 ++++++++++++++++++
gdb/testsuite/gdb.opt/inline-locals.c | 20 +++
gdb/testsuite/gdb.opt/inline-locals.exp | 30 ++++
gdb/testsuite/lib/dwarf.exp | 5 +
6 files changed, 287 insertions(+), 1 deletion(-)
create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-inline-with-lexical-scope.c
create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-inline-with-lexical-scope.exp
--
2.17.1
next reply other threads:[~2021-04-14 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 8:14 Tankut Baris Aktemur [this message]
2021-04-14 8:14 ` [PATCH v2 1/2] testsuite, gdb: recognize DW_OP_fbreg in lib/dwarf.exp Tankut Baris Aktemur
2021-04-14 9:50 ` Andrew Burgess
2021-04-14 8:14 ` [PATCH v2 2/2] gdb/dwarf2: fix "info locals" for clang-compiled inlined functions Tankut Baris Aktemur
2021-04-14 12:18 ` Aktemur, Tankut Baris
2021-04-14 15:46 ` Andrew Burgess
2021-04-14 17:00 ` Aktemur, Tankut Baris
2021-04-14 13:30 ` Simon Marchi
2021-04-14 17:08 ` Aktemur, Tankut Baris
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.1618387702.git.tankut.baris.aktemur@intel.com \
--to=tankut.baris.aktemur@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).