public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/22250] readelf should support --dwarf-start and --dwarf-depth
Date: Thu, 05 Oct 2017 16:40:00 -0000	[thread overview]
Message-ID: <bug-22250-10460-5OCk61w7jX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22250-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=22250

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Mark Wielaard from comment #1)

> Which properties of the above are important to you?
> Is the given selection mechanism of which DIEs to print the most convenient?
> Is it important to suppress header printing?
> Since this really is about printing something after an offset from the start
> of a section, should it be extended to other debug sections?

I implemented this stuff in objdump to support browsing DWARF in Emacs.
The Emacs mode dumps the "outline" of the DWARF into a buffer, then
you can click on a '...' to get more data there.  That explains why
header suppression is done...

However lately I wanted to use this with eu-readelf to track down that
bad DWARF bug: https://github.com/rust-lang/rust/issues/44412
In that case I wouldn't care so much about the headers.

But really it would be nice to have it all so that I could port the
Emacs mode to use eu-readelf.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2017-10-05 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 16:14 [Bug tools/22250] New: " tromey at sourceware dot org
2017-10-05 12:19 ` [Bug tools/22250] " mark at klomp dot org
2017-10-05 12:20 ` mark at klomp dot org
2017-10-05 12:31 ` mark at klomp dot org
2017-10-05 16:40 ` tromey at sourceware dot org [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=bug-22250-10460-5OCk61w7jX@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.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).