From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/24509] eu-readelf does not know how to dissect DW_AT_discr_list
Date: Thu, 16 May 2019 15:28:00 -0000 [thread overview]
Message-ID: <bug-24509-10460-pPhGhZtoHu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24509-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24509
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Mark Wielaard <mark at klomp dot org> ---
commit 643cbb275d65533472c0f53391f9fc1d5d9a2efc
Author: Mark Wielaard <mark@klomp.org>
Date: Sun May 5 23:18:36 2019 +0200
readelf: Decode DW_AT_discr_list block attributes.
Decode DW_AT_descr_list blocks using the DW_DSC values.
This requires knowing the signedness of the discriminant.
Which means the attr_callback function needs access to the
parent DIE. Pass the whole DIE path, plus the current level.
That way the type of the discriminant can be looked up in
the variant_part (parent) DIE of the variant DIE (which has
the discr_list attribute).
Add a testcase using both signed and unsigned discriminants.
https://sourceware.org/bugzilla/show_bug.cgi?id=24509
Signed-off-by: Mark Wielaard <mark@klomp.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2019-05-16 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 20:47 [Bug tools/24509] New: " tromey at sourceware dot org
2019-05-01 22:36 ` [Bug tools/24509] " mark at klomp dot org
2019-05-02 15:51 ` tromey at sourceware dot org
2019-05-02 16:07 ` tromey at sourceware dot org
2019-05-02 21:48 ` mark at klomp dot org
2019-05-09 14:01 ` tromey at sourceware dot org
2019-05-10 17:44 ` mark at klomp dot org
2019-05-16 15:28 ` mark at klomp dot org [this message]
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-24509-10460-pPhGhZtoHu@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).