From: "Andreas.Kromke at dreamchip dot de" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/23982] New: dwarf_formref_die() does not support DW_FORM_indirect
Date: Thu, 13 Dec 2018 17:21:00 -0000 [thread overview]
Message-ID: <bug-23982-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=23982
Bug ID: 23982
Summary: dwarf_formref_die() does not support DW_FORM_indirect
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libdw
Assignee: unassigned at sourceware dot org
Reporter: Andreas.Kromke at dreamchip dot de
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
This kind of indirect form is generated by some ARM compilers.
A temporary workaround might be:
Dwarf_Attribute *attr = dwarf_attr_integrate(die, DW_AT_type, &attr_mem);
if (attr != NULL)
{
unsigned int whatform = dwarf_whatform(attr);
while(whatform == DW_FORM_indirect)
{
uint64_t val;
const unsigned char *p = (const unsigned char *) attr->valp;
get_uleb128_unchecked(val, p);
whatform = (unsigned int) val;
attr_mem.form = whatform;
attr_mem.valp = (void *) p;
}
Dwarf_Die *type = dwarf_formref_die(attr, type_die);
...
However, this method is rather ugly, because it needs the internal function
get_uleb128_unchecked().
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-12-13 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 17:21 Andreas.Kromke at dreamchip dot de [this message]
2018-12-25 16:47 ` [Bug libdw/23982] " mark at klomp dot org
2019-01-02 17:12 ` Andreas.Kromke at dreamchip dot de
2019-01-13 16:39 ` mark at klomp dot org
2021-09-03 13:49 ` 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-23982-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).