public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/30838] [gdb/symtab] Support .debug_types section in .gnu_debugaltlink file
Date: Wed, 20 Sep 2023 14:05:52 +0000 [thread overview]
Message-ID: <bug-30838-4717-IRkEbsH4T7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30838-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30838
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=973db6fae304c2bcafff5f169610f663adc9e817
commit 973db6fae304c2bcafff5f169610f663adc9e817
Author: Tom de Vries <tdevries@suse.de>
Date: Wed Sep 20 16:05:55 2023 +0200
[gdb/symtab] Error out for .debug_types section in dwz file
There are two methods to factor out type information in a dwarf4
executable:
- use -fdebug-info-types to generate type units in a .debug_types section,
and
- use dwz to create partial units.
The dwz method has an extra benefit: it also allows to factor out
information
between executables into a newly created .dwz file, pointed to by a
.gnu_debugaltlink section.
There is nothing prohibiting a .gnu_debugaltlink file to contain a
.debug_types section.
It's just not generated by dwz or any other tool atm, and consequently gdb
has
no support for it. Enhancement PR symtab/30838 is open about the lack of
support.
Make the current situation explicit by emitting a dwarf error:
...
(gdb) file struct-with-sig-2^M
Reading symbols from struct-with-sig-2...^M
Dwarf Error: .debug_types section not supported in dwz file^M
...
and add an assert in write_gdbindex:
...
+ /* See enhancement PR symtab/30838. */
+ gdb_assert (!(per_cu->is_dwz && per_cu->is_debug_types));
...
to clarify why we can use:
...
data_buf &cu_list = (per_cu->is_debug_types
? types_cu_list
: per_cu->is_dwz ? dwz_cu_list :
objfile_cu_list);
...
The test-case is a modified copy from gdb.dwarf2/struct-with-sig.exp, so it
keeps the copyright years range.
Tested on x86_64-linux.
Tested-By: Guinevere Larsen <blarsen@redhat.com>
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30838
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-20 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 15:04 [Bug symtab/30838] New: " vries at gcc dot gnu.org
2023-09-11 15:08 ` [Bug symtab/30838] " vries at gcc dot gnu.org
2023-09-11 15:16 ` vries at gcc dot gnu.org
2023-09-12 8:44 ` vries at gcc dot gnu.org
2023-09-20 14:05 ` cvs-commit at gcc dot gnu.org [this message]
2025-01-20 17:06 ` tromey at sourceware dot org
2025-01-24 10:39 ` sam at gentoo dot org
2025-08-01 4:35 ` cvs-commit at gcc dot gnu.org
2025-08-31 23:23 ` sam at gentoo dot org
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=bug-30838-4717-IRkEbsH4T7@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).