From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/21023] 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-24m9MJt6Wf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21023-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21023
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
This probably is something that elfutils should transparently support for
libabigail. But currently elfutils libdw doesn't support GNU DebugFission
dwp/split-dwarf. Parts of it are in the process of being standardized now for
DWARF5. But the standard hasn't been finalized and code for elfutils is not yet
there (and after DWARF5 public beta was released some details were changed).
For now I would recommend not using -gsplit-dwarf and dwp. If you are looking
for smaller or "split" DWARF then yse using eu-strip -o and dwz to create debug
multi-files. That is supported.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-02-01 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:00 [Bug default/21023] New: " andrew.c.morrow at gmail dot com
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 [this message]
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-24m9MJt6Wf@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).