From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27372] [dwz] DWARF CU type DW_UT_type unhandled -- Could not find DWARF abbreviation <n>
Date: Mon, 08 Feb 2021 14:30:08 +0000 [thread overview]
Message-ID: <bug-27372-11298-KkV01PMsoh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27372-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27372
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Tom de Vries from comment #1)
> Looks like a missing goto fail:
> ...
> diff --git a/dwz.c b/dwz.c
> index 10860bf..c0d0003 100644
> --- a/dwz.c
> +++ b/dwz.c
> @@ -6584,9 +6584,11 @@ read_debug_info (DSO *dso, int kind, unsigned int
> *die_count)
> {
> value = read_8 (ptr);
> if (value != DW_UT_compile && value != DW_UT_partial)
> - error (0, 0, "%s: DWARF CU type %s unhandled", dso->filename,
> - get_DW_UT_str (value));
> -
> + {
> + error (0, 0, "%s: DWARF CU type %s unhandled", dso->filename,
> + get_DW_UT_str (value));
> + goto fail;
> + }
> }
> else
> {
> ...
> after which we have:
> ...
> $ ./dwz a.out
> ./dwz: a.out: DWARF CU type DW_UT_type unhandled
> ...
Yes, please apply. Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-08 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 12:54 [Bug default/27372] New: " vries at gcc dot gnu.org
2021-02-08 12:56 ` [Bug default/27372] " vries at gcc dot gnu.org
2021-02-08 14:30 ` mark at klomp dot org [this message]
2021-02-09 7:35 ` 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-27372-11298-KkV01PMsoh@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).