From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: [PATCH] libdw: set address size, offset size and version on fake CUs
Date: Sun, 12 Sep 2021 21:43:31 +0200 [thread overview]
Message-ID: <YT5YY1fwvoWzztwY@wildebeest.org> (raw)
In-Reply-To: <20210908201402.38174-1-mark@klomp.org>
Hi,
On Wed, Sep 08, 2021 at 10:14:02PM +0200, Mark Wielaard wrote:
> There are three "fake CUs" that are associated with .debug_loc,
> .debug_loclist and .debug_addr. These fake CUs are used for "fake
> attributes" to provide values that are stored in these sections
> instead of in the .debug_info section. These fake CUs didn't have the
> address size, offset size and DWARF version set. This meant that
> values that depended on those properties might not be interpreted
> correctly. One example was the value associated with a DW_OP_addrx
> (which comes from the .debug_addr section).
>
> Add a testcase using varlocs to test that addresses can correctly be
> retrieved for gcc/clang, DWARF4/5 and 32/64 bits objects.
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=28220
Added ChangeLog entries and pushed.
Cheers,
Mark
prev parent reply other threads:[~2021-09-12 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 20:14 Mark Wielaard
2021-09-12 19:43 ` Mark Wielaard [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=YT5YY1fwvoWzztwY@wildebeest.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).