From: Tom de Vries <tdevries@suse.de>
To: Guinevere Larsen <blarsen@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/symtab] Error out for .debug_types section in dwz file
Date: Wed, 20 Sep 2023 16:06:35 +0200 [thread overview]
Message-ID: <5b47cd2d-efa5-43df-942b-5129d5896dcb@suse.de> (raw)
In-Reply-To: <422fd996-6908-7663-9531-50654a6185cb@redhat.com>
On 9/20/23 11:18, Guinevere Larsen wrote:
> On 12/09/2023 10:43, Tom de Vries via Gdb-patches wrote:
>> 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.
>>
>> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30838
>> ---
>
> Hi! I tested this patch and it does not add any regression, and properly
> detects the situation.
>
Hi,
Thanks for testing this, committed.
- Tom
> Tested-By: Guinevere Larsen <blarsen@redhat.com>
>
prev parent reply other threads:[~2023-09-20 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 8:43 Tom de Vries
2023-09-20 9:18 ` Guinevere Larsen
2023-09-20 14:06 ` Tom de Vries [this message]
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=5b47cd2d-efa5-43df-942b-5129d5896dcb@suse.de \
--to=tdevries@suse.de \
--cc=blarsen@redhat.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).