From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 13 Release 2022-09-11 update
Date: Tue, 20 Sep 2022 08:33:29 +0200 [thread overview]
Message-ID: <206072e6-0e3b-dad8-d75b-e48564f95bf4@suse.de> (raw)
In-Reply-To: <87tu53kktz.fsf@tromey.com>
On 9/20/22 01:26, Tom Tromey wrote:
>>> My impression is that .gdb_index never really worked correctly for
>>> Ada.
>
> Tom> Hmm, I committed 7ab96794115 ("[gdb/symtab] Enable ada .gdb_index").
>
> Wow, I had completely forgotten about this.
> I see I even wrote a corresponding documentation patch.
>
>>> So, while that is a regression of sorts, since the feature isn't really
>>> usable for Ada in general,
>
> Tom> Um, can you elaborate a bit on why you think that?
>
> Loss of memory.
>
> Is there a bug open for this?
Yes, https://sourceware.org/bugzilla/show_bug.cgi?id=29179 .
> Anyway, I will look at it when I look
> into the other issues with the new DWARF reader.
>
OK. FWIW, I don't mind if we drop this feature if it's difficult to
repair or maintain going forward, or too expensive in terms of index
size, I'm just trying to make sure that we don't silently regress.
> I looked and I can't find my patch to change how .debug_names is
> constructed. Hopefully that won't be too hard to rewrite. However, I
> did find a patch that I had forgotten about that changes .debug_names so
> that it can write out a BFD, solving the string table problem (though I
> still didn't write the reader side of this).
Hm, interesting. Maybe you could post that patch to some PR?
Thanks,
- Tom
prev parent reply other threads:[~2022-09-20 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 18:26 Joel Brobecker
2022-09-11 18:58 ` Philippe Waroquiers
2022-09-14 15:58 ` Tom de Vries
2022-09-15 22:41 ` Tom Tromey
2022-09-16 11:55 ` Tom de Vries
2022-09-19 23:26 ` Tom Tromey
2022-09-20 6:33 ` 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=206072e6-0e3b-dad8-d75b-e48564f95bf4@suse.de \
--to=tdevries@suse.de \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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).