From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/27639] Unknown DWARF DW_FORM_0x1f20 (GNU_ref_alt) and DWARF DW_FORM_0x1f21 (strp_alt)
Date: Wed, 20 Apr 2022 18:28:35 +0000 [thread overview]
Message-ID: <bug-27639-13298-uLCZphaZAd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27639-13298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27639
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
Summary|Unknown DWARF |Unknown DWARF
|DW_FORM_0x1f20 and DWARF |DW_FORM_0x1f20
|DW_FORM_0x1f21 |(GNU_ref_alt) and DWARF
| |DW_FORM_0x1f21 (strp_alt)
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Matthias Klose from comment #0)
> debugedit warns about unknown sections DWARF DW_FORM_0x1f20 and DWARF
> DW_FORM_0x1f21, when called for a binary which has been processed by dwz.
>
> These warnings should not be emitted when debugedit is just called to change
> the build-id.
How exactly are you calling debugedit? Which arguments are used?
And what exact warning do you see? unknown section names or unknown DWARF
FORMs?
In theory warnings about unknown forms should only be emitted when edit_dwarf2
is called. Which is guarded by:
if (!(do_build_id && no_recompute_build_id && !base_dir && !dest_dir)
&& name != NULL && strcmp (name, ".debug_info") == 0)
edit_dwarf2 (dso);
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-20 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 6:16 [Bug debugedit/27639] New: Unknown DWARF DW_FORM_0x1f20 and DWARF DW_FORM_0x1f21 doko at debian dot org
2022-04-20 18:28 ` mark at klomp dot org [this message]
2022-11-05 17:56 ` [Bug debugedit/27639] Unknown DWARF DW_FORM_0x1f20 (GNU_ref_alt) and DWARF DW_FORM_0x1f21 (strp_alt) lool at dooz dot org
2022-12-28 21:28 ` mark at klomp dot org
2022-12-28 21:41 ` mark at klomp dot 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-27639-13298-uLCZphaZAd@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=debugedit@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).