public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "andrew.c.morrow at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/21023] New: The abidw tool does not appear to read dwarf from .dwp files associated with executables
Date: Sun, 01 Jan 2017 00:00:00 -0000	[thread overview]
Message-ID: <bug-21023-9487@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 21023
           Summary: The abidw tool does not appear to read dwarf from .dwp
                    files associated with executables
           Product: libabigail
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: andrew.c.morrow at gmail dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

$ abidw --version
1.0.rc7
I'm not actually sure if this is a bug in libabigail, or one of the supporting
libraries like libelf or libdw, but I'm starting here, since the end state I
want is that abidw works binaries built using DebugFission.

I would expect that abidw would search for DWARF info in the associated .dwp
file, however, it does not appear to do so.

On my Ubuntu 16.04 machine:

$ g++ --version
g++ (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609

$ dwp --version
GNU dwp (GNU Binutils for Ubuntu) 2.26.1

$ cat hello_world.cpp
#include <cstdlib>
#include <iostream>

int main(int argc, char* argv[]) {
    std::cout << "Hello, World!\n" << argc;
    return EXIT_SUCCESS;
}

$ g++ -g ./hello_world.cpp -o hello_world
$ abidw ./hello_world | cksum
1150852500 53174

$ g++ -gsplit-dwarf -g ./hello_world.cpp -o hello_world
$ dwp -e ./hello_world
$ abidw ./hello_world | cksum
2156308181 1319

As you can see from the sizes, running abidw against the DebugFission version
results in severely truncated output. Running under strace appears to confirm
that the dwp file was never stat'ed or read:

$ strace -f -o trace abidw ./hello_world | cksum
2156308181 1319
$ grep -c dwp trace
0

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

             reply	other threads:[~2017-01-04 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-01  0:00 andrew.c.morrow at gmail dot com [this message]
2017-01-01  0:00 ` [Bug default/21023] " andrew.c.morrow at gmail dot com
2017-01-01  0:00 ` andrew.c.morrow at gmail dot com
2017-01-01  0:00 ` mark at klomp dot org
2017-01-01  0:00 ` andrew.c.morrow at gmail dot com
2017-01-01  0:00 ` mark at klomp dot org
2018-01-01  0:00 ` mark at klomp dot org
2018-01-01  0:00 ` andrew.c.morrow at gmail dot com
2021-12-06 22:12 ` tschwinge at sourceware dot org
2021-12-07  9:19 ` mark at klomp dot org
2021-12-07  9:29 ` 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-21023-9487@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libabigail@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).