From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: [PATCH] libdw: Handle .debug_rnglists in dwarf_ranges.
Date: Mon, 28 May 2018 12:57:00 -0000 [thread overview]
Message-ID: <1527512251.12946.3.camel@klomp.org> (raw)
In-Reply-To: <20180524190830.1285-1-mark@klomp.org>
On Thu, 2018-05-24 at 21:08 +0200, Mark Wielaard wrote:
> Handle all new DW_RLE opcodes in .debug_rnglists in dwarf_ranges. Extract
> code for reading .debug_addr indexes from dwarf_formaddr as __libdw_addrx
> to reuse in __libdw_read_begin_end_pair_inc. And add new testcase.
Pushed this to master.
But I first regenerated the new test files with a newer GCC that fixes
the location expressions as promised for the just posted "libdw: Handle
.debug_loclists in dwarf_getlocation" patch.
It seemed better to only have one set in the tree.
Both testfileranges5.debug and testfilesplitranges5.debug got
regenerated (and the test results slightly adjusted) to show that the
ranges are identical for both, even though they are using completely
different DWARF encodings.
Cheers,
Mark
prev parent reply other threads:[~2018-05-28 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 19:08 Mark Wielaard
2018-05-28 12:57 ` 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=1527512251.12946.3.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).