From: Pedro Alves <pedro@palves.net>
To: Mark Wielaard <mark@klomp.org>, gdb@sourceware.org
Subject: Re: DWARF5 and .gdb_index/.debug_names
Date: Tue, 1 Sep 2020 20:16:46 +0100 [thread overview]
Message-ID: <c0a30d2b-a40f-b591-780f-6b37fb6f32e3@palves.net> (raw)
In-Reply-To: <e56fb5e13a0e04a40fc1c88205d3c0eaaa71919a.camel@klomp.org>
On 8/30/20 6:18 PM, Mark Wielaard wrote:
> dwz does support .gdb_index rewriting, but doesn't know about
> .debug_names yet. So could we as a first step, when switching the
> DWARF5 keep using .gdb_index? At least till any issues with gdb
> .debug_names are resolved and dwz supports it?
I'm not aware of anything that would force use of DWARF5 to also
imply use of .debug_names, or that would prevent using .gdb_index.
AFAIK, we can treat them as orthogonal.
Pedro Alves
next prev parent reply other threads:[~2020-09-01 19:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 17:18 Mark Wielaard
2020-08-31 7:21 ` Tom de Vries
2020-08-31 8:28 ` Jan Kratochvil
2020-09-01 3:07 ` David Blaikie
2020-09-01 18:38 ` Tom Tromey
2020-09-01 18:53 ` David Blaikie
2020-09-01 19:16 ` Pedro Alves [this message]
2020-09-01 22:00 ` Eric Christopher
2020-09-14 15:23 ` Gaius Mulley
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=c0a30d2b-a40f-b591-780f-6b37fb6f32e3@palves.net \
--to=pedro@palves.net \
--cc=gdb@sourceware.org \
--cc=mark@klomp.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).