From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: GDB 13 Release 2022-09-11 update
Date: Mon, 19 Sep 2022 17:26:00 -0600 [thread overview]
Message-ID: <87tu53kktz.fsf@tromey.com> (raw)
In-Reply-To: <876e3b8c-b251-be35-5e4e-c75be25ea0e4@suse.de> (Tom de Vries's message of "Fri, 16 Sep 2022 13:55:09 +0200")
>> 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? Anyway, I will look at it when I look
into the other issues with the new DWARF reader.
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).
Tom
next prev parent reply other threads:[~2022-09-19 23:26 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 [this message]
2022-09-20 6:33 ` Tom de Vries
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=87tu53kktz.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).