From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27474] New: [dwz] Report unknown dwarf problem only once
Date: Fri, 26 Feb 2021 12:33:56 +0000 [thread overview]
Message-ID: <bug-27474-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27474
Bug ID: 27474
Summary: [dwz] Report unknown dwarf problem only once
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 run the gdb testsuite with target boards cc-with-dwz and cc-with-dwz-m to
test dwz against gdb.
I have a grepping script that filters out known irrelevant dwz messages.
However, consider this output:
...
gdb compile failed, dwz:
/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.dwarf2/loclists-multiple-cus/loclists-multiple-cus-dw32:
Unknown DWARF DW_FORM_loclistx
dwz:
/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.dwarf2/loclists-multiple-cus/loclists-multiple-cus-dw32:
Couldn't read abbrev at offset 0x64
...
AFAICT, these are two error message caused by the same problem.
The "Unknown DWARF DW_FORM_loclistx" is specific enough to filter out.
But the "Couldn't read abbrev at offset 0x64" isn't.
It would be better if there was only one, specific error message for this.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2021-02-26 12:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-27474-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).