From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: Various eu-readelf --debug-dump improvements
Date: Sun, 10 Dec 2017 16:00:00 -0000 [thread overview]
Message-ID: <1512921624.15696.37.camel@klomp.org> (raw)
In-Reply-To: <1511971553-30135-1-git-send-email-mark@klomp.org>
On Wed, 2017-11-29 at 17:05 +0100, Mark Wielaard wrote:
> While working on the DWARF5 support I found various cases where the
> eu-readelf --debug-dump could be improved to provide a bit more information
> that helped debug issues. The following changes are not DWARF5 specific,
> but improve the --debug-dump output to make a more useful (IMHO).
>
> [PATCH 1/5] readelf: Adjust print_ops formatting.
> [PATCH 2/5] readelf: Print abbrev code for DIE with --debug-
> dump=info.
> [PATCH 3/5] readelf: Print actual file for decl_file and call_file.
> [PATCH 4/5] readelf: Print CU, base address and unresolved
> .debug_ranges.
> [PATCH 5/5] readelf: Print CU, base address and unresolved
> .debug_loc.
I pushed all five to master now.
prev parent reply other threads:[~2017-12-10 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 16:06 Mark Wielaard
2017-11-29 16:06 ` [PATCH 1/5] readelf: Adjust print_ops formatting Mark Wielaard
2017-11-29 16:06 ` [PATCH 3/5] readelf: Print actual file for decl_file and call_file attributes Mark Wielaard
2017-11-29 16:06 ` [PATCH 5/5] readelf: Print CU, base address and unresolved .debug_loc entries Mark Wielaard
2017-11-29 16:06 ` [PATCH 4/5] readelf: Print CU, base address and unresolved .debug_range entries Mark Wielaard
2017-11-29 16:06 ` [PATCH 2/5] readelf: Print abbrev code for DIE with --debug-dump=info Mark Wielaard
2017-12-10 16:00 ` 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=1512921624.15696.37.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).