From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27463] New: [dwz] Unhandled DW_FORM_sdata for DW_AT_decl_line
Date: Wed, 24 Feb 2021 07:54:46 +0000 [thread overview]
Message-ID: <bug-27463-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27463
Bug ID: 27463
Summary: [dwz] Unhandled DW_FORM_sdata for DW_AT_decl_line
Product: dwz
Version: unspecified
Status: NEW
Severity: normal
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: ---
Regression since commit 4100572 "Handle DW_FORM_implicit_const for
DW_AT_decl_line".
With the gdb regression testsuite, using target board cc-with-dwz, we run into:
...
$ dwz
build/gdb/testsuite/outputs/gdb.trace/unavailable-dwarf-piece/unavailable-dwarf-piece
-o z
dwz: unavailable-dwarf-piece: Unhandled DW_FORM_sdata for DW_AT_decl_line
...
The commit added this code:
...
switch (form)
{
case DW_FORM_data1: value = read_8 (ptr); handled = true; break;
case DW_FORM_data2: value = read_16 (ptr); handled = true; break;
case DW_FORM_data4: value = read_32 (ptr); handled = true; break;
case DW_FORM_data8: value = read_64 (ptr); handled = true; break;
case DW_FORM_udata:
value = read_uleb128 (ptr); handled = true; break;
case DW_FORM_implicit_const:
value = t->values[i]; handled = true; break;
default:
error (0, 0, "%s: Unhandled %s for %s",
dso->filename, get_DW_FORM_str (form),
get_DW_AT_str (t->attr[i].attr));
return 1;
}
...
and the error case triggers.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-02-24 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 7:54 vries at gcc dot gnu.org [this message]
2021-02-26 16:06 ` [Bug default/27463] " mark at klomp dot org
2021-02-26 16:58 ` 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-27463-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).