From: "annulen at yandex dot ru" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/26674] dwz should be able to fix CRCs in .gnu_debuglink when optimizing separated debug files
Date: Tue, 29 Sep 2020 11:21:58 +0000 [thread overview]
Message-ID: <bug-26674-11298-qlLRixrwxE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26674-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26674
--- Comment #2 from Konstantin Tokarev <annulen at yandex dot ru> ---
Thanks, I didn't think about that way somehow. However, I still think there is
a room for usability improvement.
I think following way would be the most convenient:
1) we run dwz on "main" ELF files instead of extracted debug info
2) if .debug_info section is missing dwz optimizes file referenced in
.gnu_debuglink and updates CRC
3) if input file looks like "debug file", i.e. file produced by objcopy
--only-keep-debug, print a suggestion that dwz might need to be run on "main"
file or CRC will be off
In this workflow it would also be possible to use multifile mode without much
hassle.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-29 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 3:24 [Bug default/26674] New: " annulen at yandex dot ru
2020-09-29 5:25 ` [Bug default/26674] " vries at gcc dot gnu.org
2020-09-29 6:41 ` vries at gcc dot gnu.org
2020-09-29 11:21 ` annulen at yandex dot ru [this message]
2020-09-29 11:23 ` annulen at yandex dot ru
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-26674-11298-qlLRixrwxE@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).