From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/22250] New: readelf should support --dwarf-start and --dwarf-depth
Date: Wed, 04 Oct 2017 16:14:00 -0000 [thread overview]
Message-ID: <bug-22250-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=22250
Bug ID: 22250
Summary: readelf should support --dwarf-start and --dwarf-depth
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tools
Assignee: unassigned at sourceware dot org
Reporter: tromey at sourceware dot org
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
objdump supports --dwarf-start and --dwarf-depth options.
--dwarf-start specifies the DIE at which to begin dumping.
--dwarf-depth specifies how many levels down to print; if
there are more levels it just prints "...", like:
<0><2174>: Abbrev Number: 1 (DW_TAG_compile_unit)
<2175> DW_AT_producer : (indirect string, offset: 0x0): clang LLVM
(rustc version 1.20.0 (f3d6973f4 2017-08-27))
<2179> DW_AT_language : 28 (Unknown: 1c)
<217b> DW_AT_name : (indirect string, offset: 0x1621):
/checkout/src/libstd/lib.rs
<217f> DW_AT_stmt_list : 0x9f2
<2183> DW_AT_comp_dir : (indirect string, offset: 0x163d):
/checkout/obj
<2187> DW_AT_low_pc : 0x0
<218f> DW_AT_ranges : 0x2be80
<1><2193>: ...
These are handy for investigating large files with dwarf-mode that
is in binutils.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-10-04 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 16:14 tromey at sourceware dot org [this message]
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
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@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).