From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27544] New: [dwz] Handle dwarf errors more graciously
Date: Mon, 08 Mar 2021 13:47:42 +0000 [thread overview]
Message-ID: <bug-27544-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27544
Bug ID: 27544
Summary: [dwz] Handle dwarf errors more graciously
Product: dwz
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
I did an experiment with libxul debug info (from firefox).
I downloaded the firefox debuginfo package on openSUSE Leap 15.2.
I observed that there we no partial units.
Then I tried to run dwz, but after quite a while ran into a "cannot find
referenced DIE". I double checked, the error is correct.
It's a bit of a pity though, to not compress a rather large debug info file
because of a few invalid DIE references.
It would be nice if dwz could handle this more aggressively, say by treating
the invalid references as having the value 0.
However, we still would want to make a distinction between:
- "cannot find referenced DIE" because of input error
- "cannot find referenced DIE" because of dwz problem
so probably we'd need an input verification phase (PR25229).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-08 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 13:47 vries at gcc dot gnu.org [this message]
2021-03-12 10:56 ` [Bug default/27544] " 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-27544-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).