public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/21792] New: Decode DWARF5 in eu-readelf
Date: Wed, 19 Jul 2017 17:54:00 -0000	[thread overview]
Message-ID: <bug-21792-10460@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 21792
           Summary: Decode DWARF5 in eu-readelf
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tools
          Assignee: unassigned at sourceware dot org
          Reporter: woodard at redhat dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

Created attachment 10274
  --> https://sourceware.org/bugzilla/attachment.cgi?id=10274&action=edit
clang compiled object that includes the example above

We are starting to use Clang 4.0.0 at LLNL and it is emitting some DWARF5
opcodes. Please add DWARF5 decoding to eu-readelf.

For example:
#include <string>
#include <vector>

std::vector<std::string> var;

and tangentially I saw something in the DWARF which neither readelf or
eu-readelf understands.
[   7e1]      namespace
               name                 (strp) "__cxx11"
               decl_file            (data1) 1
               decl_line            (data2) 2214
               ??? (0x89)           (flag_present) yes


Since clang is already emitting some DWARF5 we should at least be able to
decode what it is emitting reliably.

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

             reply	other threads:[~2017-07-19 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 17:54 woodard at redhat dot com [this message]
2017-09-20 18:38 ` [Bug tools/21792] " mark at klomp 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-21792-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).