From: "tschwinge at sourceware 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: Mon, 06 Dec 2021 22:12:32 +0000 [thread overview]
Message-ID: <bug-21023-9487-Z68oI6FeJh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21023-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21023
Thomas Schwinge <tschwinge at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2021-12-06
Status|UNCONFIRMED |NEW
CC| |tschwinge at sourceware dot org
--- Comment #8 from Thomas Schwinge <tschwinge at sourceware dot org> ---
So I wanted to use libabigail on GCC '-gsplit-dwarf' object files
('*.o'/'*.dwo'), and found that it doesn't work. Then found this existing PR;
confirming that status is still as per Andrew's 2018-06-16 comment:
'eu-readelf'/elfutils (Ubuntu 0.176-1.1build1 in my case) appears to work, but
'abidw'/libabigail (current master branch) doesn't even open the '*.dwo' file,
per 'strace'.
If I wanted to try help implement that (but no promises how far I'll get...),
are Mark's 2018-06-05 comments here re "libabigail will need to use a few new
interfaces" still applicable, to get started?
Additionally, in PR25042 I saw Mark's 2019-09-30 comment that "logic [there] is
broken, [...] when dealing with split-dwarf DWO files", so I suppose that needs
to be reworked, too? Per Dodji's 2019-10-01 comment, "this optimization will
be unnecessary, hopefully".
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-06 22:12 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
2017-01-01 0:00 ` mark at klomp dot org
2017-01-01 0:00 ` andrew.c.morrow at gmail dot com
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 [this message]
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-Z68oI6FeJh@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).