From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH v3 0/7] Handle foreign type units in .debug_names
Date: Mon, 11 May 2026 11:40:26 -0400 [thread overview]
Message-ID: <20260511154053.142576-1-simon.marchi@efficios.com> (raw)
This is v3 of:
https://inbox.sourceware.org/gdb-patches/20260416200256.386186-1-simon.marchi@efficios.com/
I merged the first patch of v2 ("gdb: refuse to produce .gdb_index when
skeletonless type units are present"), ensuring that GDB does not
produce bogus indexes in presence of foreign type units.
I addressed the review comments from v2, which were all pretty minor.
The first patch of this series moves the dwo data structures to a new
dwarf2/dwo.h header file, instead of dwarf2/read.h. That is the only
one worth re-reviewing, I think, all the others have the Approved-By tag
already.
Simon Marchi (7):
gdb/dwarf: move dwo_unit and dwo_file to dwo.h
gdb/dwarf: move dwarf2_cu::section to cu.c
gdb/dwarf: add dwo_file::find_tus
gdb/dwarf: generate foreign type units in .debug_names
gdb/dwarf: add debug output in read-debug-names.c
gdb/dwarf: add more context to complaints in
mapped_debug_names_reader::scan_one_entry
gdb/dwarf: read foreign type units
gdb/dwarf2/cu.c | 11 +
gdb/dwarf2/dwo.h | 239 +++++++++++
gdb/dwarf2/index-write.c | 165 ++++++--
gdb/dwarf2/read-debug-names.c | 357 +++++++++++++---
gdb/dwarf2/read.c | 390 ++++++++----------
gdb/dwarf2/read.h | 117 ++++--
gdb/dwarf2/types.h | 2 +
...dwarf5-fission-debug-types-debug-names.exp | 29 ++
8 files changed, 975 insertions(+), 335 deletions(-)
create mode 100644 gdb/dwarf2/dwo.h
create mode 100644 gdb/testsuite/boards/dwarf5-fission-debug-types-debug-names.exp
base-commit: 62cc7210c87a08a9e10955d9a240cfe0c0b5ee13
--
2.54.0
next reply other threads:[~2026-05-11 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 15:40 Simon Marchi [this message]
2026-05-11 15:40 ` [PATCH v3 1/7] gdb/dwarf: move dwo_unit and dwo_file to dwo.h Simon Marchi
2026-05-13 15:18 ` Tom Tromey
2026-05-13 17:30 ` Simon Marchi
2026-05-11 15:40 ` [PATCH v3 2/7] gdb/dwarf: move dwarf2_cu::section to cu.c Simon Marchi
2026-05-11 15:40 ` [PATCH v3 3/7] gdb/dwarf: add dwo_file::find_tus Simon Marchi
2026-05-11 15:40 ` [PATCH v3 4/7] gdb/dwarf: generate foreign type units in .debug_names Simon Marchi
2026-05-11 15:40 ` [PATCH v3 5/7] gdb/dwarf: add debug output in read-debug-names.c Simon Marchi
2026-05-11 15:40 ` [PATCH v3 6/7] gdb/dwarf: add more context to complaints in mapped_debug_names_reader::scan_one_entry Simon Marchi
2026-05-11 15:40 ` [PATCH v3 7/7] gdb/dwarf: read foreign type units Simon Marchi
2026-05-19 19:42 ` Guinevere Larsen
2026-05-19 20:10 ` Simon Marchi
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=20260511154053.142576-1-simon.marchi@efficios.com \
--to=simon.marchi@efficios.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