public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26908] abidw --abidiff /lib64/libclang-cpp.so.11  crashes in dwarf_dieoffset
Date: Sat, 28 Nov 2020 20:51:44 +0000	[thread overview]
Message-ID: <bug-26908-9487-tXdNnN6nLy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26908-9487@http.sourceware.org/bugzilla/>

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

--- Comment #4 from dodji at redhat dot com ---
Hello,

So clang and mozilla in particular have binaries that are so huge that I think
they'll need some very specific work for libabigail to handle them.  For
instance, just dumping the debug info of the libclang-cpp.so yields a file of
more than 20GB.  That is insane.  Just analyzing that in the current mode of
operation takes an herculean machine, at least.

I'll defer that work for later when we have more bandwidth, not because I don't
like clang, but because I think we can be helpful to many many many more
projects of realistic size in a shorter period of time.

Trying to read the binary however should not crash.  So I'll look at it
somewhat, but I won't be able to spend a lot of time on it for now.  I just
wanted to let you know about this.  I believe there is a bug opened for the
support of clang binaries (huge huge quasi pathological c++ binaries really),
if I am not mistaken.  If not, I think we should open one.

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

  parent reply	other threads:[~2020-11-28 20:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 20:43 [Bug default/26908] New: " 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 [this message]
2020-11-30  6:12 ` [Bug default/26908] libabigail's dwarf reader crashes while scanning a DW_TAG_partial_unit with no child node dodji at redhat dot com

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-tXdNnN6nLy@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).