public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug ada/24713] [ada] Support .gdb_index
Date: Thu, 16 Apr 2020 13:26:22 +0000 [thread overview]
Message-ID: <bug-24713-4717-9URwfute0a@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24713-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24713
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[ada] Support index |[ada] Support .gdb_index
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #2)
> FWIW gdb can make a .debug_names index now for Ada.
> It still can't create a .gdb_index -- but I tend to think
> we should just declare that one a "won't fix".
Because, as that commit says:
...
commit 3b00ef10a2a4750a86a04bb66eda3bf33d298be1
Author: Tom Tromey <tromey@adacore.com>
Date: Mon Jul 8 06:23:16 2019 -0600
Add Ada support for .debug_names
This patch adds support for Ada to .debug_names. I opted to leave
.gdb_index alone, because in my view it is a defunct format.
...
Changing title to restrict PR scope to .gdb_index, and marking it
resolved-wontfix.
If somebody want to add this functionality, this PR can always be reopened.
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2020-04-16 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-24713-4717@http.sourceware.org/bugzilla/>
2020-04-16 13:26 ` vries at gcc dot gnu.org [this message]
2020-06-02 8:51 ` vries at gcc dot gnu.org
2020-06-02 10:48 ` vries at gcc dot gnu.org
2020-06-10 12:47 ` cvs-commit at gcc dot gnu.org
2020-06-10 12:47 ` vries at gcc dot gnu.org
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=bug-24713-4717-9URwfute0a@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).