From: "m.ostapenko at partner dot samsung.com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19173] Abidiff doesn't detect symbol size change in library.
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <bug-19173-9487-4fco6cTpnA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19173-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19173
--- Comment #7 from Maxim Ostapenko <m.ostapenko at partner dot samsung.com> ---
(In reply to Yury Gribov from comment #6)
> Max, what if debug info is missing? Does abidiff still report bug (based on
> .dynsym info)?
Nope, removing debug info removes the abidiff's report as well.
max@max:/tmp$ gcc libfoo.c -shared -fpic -o libfoo2.so -DLONG
max@max:/tmp$ gcc libfoo.c -shared -fpic -o libfoo.so
max@max:/tmp$ ~/install/libabigail/bin/abidiff libfoo.so libfoo2.so
Actually, libabigail documentation states that the tool relies on debug info
quite hardly, so I'm not sure that running abidiff on stripped libraries makes
sense. On the other hand, the bug might be quite common and reporting it might
be desirable even if debug info is missing (just as for added/removed
functions).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-10-26 9:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 [Bug default/19173] New: " m.ostapenko at partner dot samsung.com
2015-01-01 0:00 ` [Bug default/19173] " woodard at redhat dot com
2015-01-01 0:00 ` y.gribov at samsung dot com
2015-01-01 0:00 ` m.ostapenko at partner dot samsung.com
2015-01-01 0:00 ` dodji at redhat dot com
2015-01-01 0:00 ` dodji at redhat dot com
2015-01-01 0:00 ` jakub at redhat dot com
2015-01-01 0:00 ` mjw at redhat dot com
2015-01-01 0:00 ` dodji at redhat dot com
2015-01-01 0:00 ` y.gribov at samsung dot com
2015-01-01 0:00 ` m.ostapenko at partner dot samsung.com
2015-01-01 0:00 ` y.gribov at samsung dot com
2015-01-01 0:00 ` dodji at seketeli dot org
2015-01-01 0:00 ` m.ostapenko at partner dot samsung.com [this message]
2015-01-01 0:00 ` woodard at redhat dot com
2015-01-01 0:00 ` m.ostapenko at partner dot samsung.com
2015-01-01 0:00 ` jakub at redhat dot com
2015-01-01 0:00 ` m.ostapenko at partner dot samsung.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-19173-9487-4fco6cTpnA@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).