From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27374] [dwz, dwarf5] .debug_names support
Date: Fri, 09 Feb 2024 19:58:50 +0000 [thread overview]
Message-ID: <bug-27374-11298-4zI79iPs5o@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27374-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27374
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
FWIW I'd recommend simply making the index after running dwz.
However, if you really want to have dwz understand how to make
an index, you should be aware of gdb extensions:
https://sourceware.org/gdb/current/onlinedocs/gdb.html/Debug-Names.html#Debug-Names
There will be more of these, I think -- actually to handle
dwz we need some.
Also, gdb does producer-sniffing and rejects most indexes,
so probably it will also need a patch if dwz gains this capability.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-02-09 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 13:07 [Bug default/27374] New: " vries at gcc dot gnu.org
2021-02-08 14:25 ` [Bug default/27374] " mark at klomp dot org
2021-02-19 11:36 ` mark at klomp dot org
2023-12-10 15:15 ` tromey at sourceware dot org
2024-01-18 20:38 ` tromey at sourceware dot org
2024-02-09 19:58 ` tromey at sourceware dot org [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=bug-27374-11298-4zI79iPs5o@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@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).