From: "annulen at yandex dot ru" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/26674] New: dwz should be able to fix CRCs in .gnu_debuglink when optimizing separated debug files
Date: Tue, 29 Sep 2020 03:24:17 +0000 [thread overview]
Message-ID: <bug-26674-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26674
Bug ID: 26674
Summary: dwz should be able to fix CRCs in .gnu_debuglink when
optimizing separated debug files
Product: dwz
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: annulen at yandex dot ru
CC: dwz at sourceware dot org
Target Milestone: ---
Right now optimizing standalone debug files which were extracted from main ELF
files via objcopy prevents their use in gdb because .gnu_debuglink of main ELF
file has CRC which was not updated. It would be great if dwz could fix CRC
itself (path of main ELF file can be given through additional command line
argument), or at least provided separate tool for doing such fix (I'm aware of
sepdebugcrcfix but it's a part of rpm and isn't really user-friendly)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-09-29 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 3:24 annulen at yandex dot ru [this message]
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
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@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).