public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Tom Tromey <tom@tromey.com>
Cc: elfutils-devel@sourceware.org, Dodji Seketeli <dodji@seketeli.org>
Subject: Re: [PATCH] readelf: Print DIE offset in attribute reading error messages.
Date: Wed, 22 Nov 2017 11:36:00 -0000	[thread overview]
Message-ID: <1511350609.3112.20.camel@klomp.org> (raw)
In-Reply-To: <87bmjvxwwo.fsf@tromey.com>

On Tue, 2017-11-21 at 12:19 -0700, Tom Tromey wrote:
> > > > > > "Mark" == Mark Wielaard <mark@klomp.org> writes:
> 
> Mark> This has been really useful to debug some DWARF format issues, but it
> Mark> could be even more useful. Since we know the attribute name and form
> Mark> (or we would have generated an error earlier) add those to the error
> Mark> message too.
> 
> Thanks for doing this.
> 
> Does dwarflint also report the error that prompted this?

No, because I am actually testing my DWARF5 work and dwarflint doesn't
support DWARF5 yet. (Also dwarflint doesn't build with the GCC8 trunk
branch which I am using atm.) But also yes, in my tests I corrupted a
DWARF4 .debug_ranges section so it couldn't be read and then dwarflint
will yell and scream about attributes that references it. But also no,
because after that it seems to go into a loop and never finishes...
This might just be it finding too many issues with the missing ranges.
It does suppress warnings after finding too many duplicates, and I
haven't had the patience to let it finish.

> I tried dwarflint on my file, but there was a lot of output and I never
> did track down the precise problem, so I wasn't sure...

Yeah, dwarflint seems hyper sensitive :) Patches welcome!

Cheers,

Mark

  reply	other threads:[~2017-11-22 11:36 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
2017-11-21 10:21   ` Mark Wielaard
2017-11-21 19:19     ` Tom Tromey
2017-11-22 11:36       ` Mark Wielaard [this message]
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=1511350609.3112.20.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).