From: simon.marchi@polymtl.ca
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: [PATCH 0/8] Handle foreign type units in .debug_names
Date: Mon, 16 Mar 2026 19:19:18 -0400 [thread overview]
Message-ID: <20260316232042.368080-1-simon.marchi@polymtl.ca> (raw)
From: Simon Marchi <simon.marchi@polymtl.ca>
Foreign type units is a fancy name for type units in .dwo files.
As we stand, in the presence of foreign type units, we produce bogus
indexes (both .gdb_index and .debug_names). So I think the minimum
would be to refuse creating indexes if there are foreign type units.
However, this series adds support for writing them to .debug_name and
reading them back.
For .gdb_index, the series just makes GDB refuse to create an index in
that case.
Note that this series depends on the enumerate series here:
https://inbox.sourceware.org/gdb-patches/20260220202002.860008-1-simon.marchi@efficios.com/T/#m75d30311589e79b52dcbdd840f8843ffa207000f
Simon Marchi (8):
gdb: refuse to produce .gdb_index when skeletonless type units are
present
gdb/dwarf: move dwo_unit and dwo_file to read.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/doc/gdb.texinfo | 6 +
gdb/dwarf2/cu.c | 11 +
gdb/dwarf2/index-write.c | 174 ++++++++-
gdb/dwarf2/read-debug-names.c | 355 +++++++++++++++---
gdb/dwarf2/read.c | 349 ++++++++---------
gdb/dwarf2/read.h | 208 +++++++++-
gdb/dwarf2/types.h | 2 +
...dwarf5-fission-debug-types-debug-names.exp | 29 ++
.../gdb.dwarf2/gdb-index-skeletonless-tu.c | 23 ++
.../gdb.dwarf2/gdb-index-skeletonless-tu.exp | 103 +++++
gdbsupport/common-utils.h | 12 +
11 files changed, 1032 insertions(+), 240 deletions(-)
create mode 100644 gdb/testsuite/boards/dwarf5-fission-debug-types-debug-names.exp
create mode 100644 gdb/testsuite/gdb.dwarf2/gdb-index-skeletonless-tu.c
create mode 100644 gdb/testsuite/gdb.dwarf2/gdb-index-skeletonless-tu.exp
base-commit: 9cc83ec0ce9b4b75e8cd2b0c46f23d4cbf4b2f2b
prerequisite-patch-id: 44023c5aa2f90e676c8b6f2479de04cf3ccb86fa
prerequisite-patch-id: acbee56e54b4f2ebd7a2b321eae58521699d66a3
prerequisite-patch-id: 1fe50e2f79d2cbbb73a5aff3b2f87506466443c2
--
2.53.0
next reply other threads:[~2026-03-16 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 23:19 simon.marchi [this message]
2026-03-16 23:19 ` [PATCH 1/8] gdb/dwarf: refuse to produce .gdb_index when skeletonless type units are present simon.marchi
2026-03-17 12:57 ` Eli Zaretskii
2026-03-16 23:19 ` [PATCH 2/8] gdb/dwarf: move dwo_unit and dwo_file to read.h simon.marchi
2026-03-16 23:19 ` [PATCH 3/8] gdb/dwarf: move dwarf2_cu::section to cu.c simon.marchi
2026-03-16 23:19 ` [PATCH 4/8] gdb/dwarf: add dwo_file::find_tus simon.marchi
2026-03-16 23:19 ` [PATCH 5/8] gdb/dwarf: generate foreign type units in .debug_names simon.marchi
2026-03-16 23:19 ` [PATCH 6/8] gdb/dwarf: add debug output in read-debug-names.c simon.marchi
2026-03-16 23:19 ` [PATCH 7/8] gdb/dwarf: add more context to complaints in mapped_debug_names_reader::scan_one_entry simon.marchi
2026-03-16 23:19 ` [PATCH 8/8] gdb/dwarf: read foreign type units 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=20260316232042.368080-1-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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