From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Cc: Tom Tromey <tom@tromey.com>, Dodji Seketeli <dodji@seketeli.org>
Subject: Re: [PATCH] readelf: Print DIE offset in attribute reading error messages.
Date: Thu, 16 Nov 2017 14:31:00 -0000 [thread overview]
Message-ID: <1510842678.6966.33.camel@klomp.org> (raw)
In-Reply-To: <1507042757-27353-1-git-send-email-mark@klomp.org>
On Tue, 2017-10-03 at 16:59 +0200, Mark Wielaard wrote:
> When processing large files it is useful to know the DIE offset if
> printing of attributes fails (especially when redirecting the output).
> With this change the error message looks like:
>
> eu-readelf: DIE [2aeb8ef1] cannot get attribute value: invalid DWARF
Got another report about a large debug file where this improved error
message would have been really handy. So I pushed it to master now.
Cheers,
Mark
next prev parent reply other threads:[~2017-11-16 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 14:59 Mark Wielaard
2017-11-16 14:31 ` Mark Wielaard [this message]
2017-11-21 10:21 ` Mark Wielaard
2017-11-21 19:19 ` Tom Tromey
2017-11-22 11:36 ` Mark Wielaard
2017-11-23 8:39 ` Dodji Seketeli
2017-11-24 10:22 ` Mark Wielaard
2017-11-22 11:59 ` 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=1510842678.6966.33.camel@klomp.org \
--to=mark@klomp.org \
--cc=dodji@seketeli.org \
--cc=elfutils-devel@sourceware.org \
--cc=tom@tromey.com \
/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).