From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: [PATCH 3/3] libdw: Handle DW_OP_GNU_variable_value.
Date: Fri, 10 Nov 2017 15:38:00 -0000 [thread overview]
Message-ID: <1510328330.10879.91.camel@klomp.org> (raw)
In-Reply-To: <1509838266-10337-3-git-send-email-mark@klomp.org>
On Sun, 2017-11-05 at 00:31 +0100, Mark Wielaard wrote:
> Handle DW_OP_GNU_variable_value in dwarf_getlocation[_attr,_die].
> DW_OP_GNU_variable_value takes one argument a DIE reference that
> describes a value given by a location of const_value attribute.
>
> To test handling of the new operand the varlocs test is adapted
> to print out all DIEs and attributes with expressions or location
> lists (the original varlocs test only prints out variables and
> arguments of function DIEs).
Pushed to master.
next prev parent reply other threads:[~2017-11-10 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 23:31 [PATCH 1/3] readelf: " Mark Wielaard
2017-11-04 23:31 ` [PATCH 3/3] libdw: " Mark Wielaard
2017-11-10 15:38 ` Mark Wielaard [this message]
2017-11-04 23:31 ` [PATCH 2/3] libdw: Update acceptable forms and attributes for dwarf_getlocation Mark Wielaard
2017-11-10 15:38 ` Mark Wielaard
2017-11-10 15:38 ` [PATCH 1/3] readelf: Handle DW_OP_GNU_variable_value Mark Wielaard
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=1510328330.10879.91.camel@klomp.org \
--to=mark@klomp.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).