From: David Blaikie <dblaikie@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: Mark Wielaard <mark@klomp.org>, gdb@sourceware.org
Subject: Re: DWARF5 and .gdb_index/.debug_names
Date: Tue, 1 Sep 2020 11:53:40 -0700 [thread overview]
Message-ID: <CAENS6EvmT18Hkx5FkgdAC0wju5n48wetjeZ+MFr3xOYcPhtYqQ@mail.gmail.com> (raw)
In-Reply-To: <878sdt736g.fsf@tromey.com>
On Tue, Sep 1, 2020 at 11:38 AM Tom Tromey <tom@tromey.com> wrote:
> >>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:
>
> Mark> During the BoF Pedro mentioned that the GDB DWARF5 .debug_names
> support
> Mark> is incomplete/wrong. I was wondering whether there was a good
> Mark> description of the issue and/or a bug report for it.
>
> It's been a while but last time I looked I thought gdb's process emitted
> incorrect names. I filed this bug, with analysis:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=24820
>
> gdb's reader probably also needs updating, since it relies on this same
> incorrect reading of the standard.
>
> Having gdb write the index is mildly bad anyway. It should be in the
> linker, and/or dwz or debuginfod. Putting it in gdb back in the
> .gdb_index days was a mistake.
>
FWIW, there are times where you might not want to add this at production
time - at least with lld, for instance, it takes significantly more
memory/linker time. So if you're building more often than you're debugging,
it might be nice to build without an index to speed up the build/test loop,
then only pay the index building cost when you end up wanting to debug
something.
- Dave
next prev parent reply other threads:[~2020-09-01 18:53 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 [this message]
2020-09-01 19:16 ` Pedro Alves
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=CAENS6EvmT18Hkx5FkgdAC0wju5n48wetjeZ+MFr3xOYcPhtYqQ@mail.gmail.com \
--to=dblaikie@gmail.com \
--cc=gdb@sourceware.org \
--cc=mark@klomp.org \
--cc=tom@tromey.com \
/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).