From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26908] libabigail's dwarf reader crashes while scanning a DW_TAG_partial_unit with no child node
Date: Mon, 30 Nov 2020 06:12:59 +0000 [thread overview]
Message-ID: <bug-26908-9487-91FJao2mlJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26908-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26908
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Summary|abidw --abidiff |libabigail's dwarf reader
|/lib64/libclang-cpp.so.11 |crashes while scanning a
|crashes in dwarf_dieoffset |DW_TAG_partial_unit with no
| |child node
Status|NEW |RESOLVED
--- Comment #5 from dodji at redhat dot com ---
Okay, it turned out this wasn't that difficult to handle after all :-)
This should be fixed by patch
https://sourceware.org/git/?p=libabigail.git;a=commit;h=2417efb2b7619ed2a2bd089d267833ee9d171eea,
applied to the master branch.
Note that just doing abidw --noout on the libclang-cpp.so binary takes 19
minutes and 11GB of RAM to complete. The full abidw --abidiff takes 5 hours to
complete on a power7 box here. As I said in my comment earlier, it would take
a separate "project" to bring those numbers down for binaries with such a
*huge* ABI surface as clang and the likes.
Thanks for reporting this issue!
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2020-11-30 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 20:43 [Bug default/26908] New: abidw --abidiff /lib64/libclang-cpp.so.11 crashes in dwarf_dieoffset woodard at redhat dot com
2020-11-16 21:17 ` [Bug default/26908] " woodard at redhat dot com
2020-11-21 0:34 ` woodard at redhat dot com
2020-11-23 17:51 ` woodard at redhat dot com
2020-11-28 20:51 ` dodji at redhat dot com
2020-11-30 6:12 ` dodji at redhat dot com [this message]
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-26908-9487-91FJao2mlJ@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).