From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27208] abicompat doesn't check back calls.
Date: Tue, 19 Jan 2021 22:12:09 +0000 [thread overview]
Message-ID: <bug-27208-9487-Exo9uZOXJi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27208-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27208
--- Comment #1 from Ben Woodard <woodard at redhat dot com> ---
I think what needs to be done to fix this is in
perform_compat_check_in_normal_mode once you have gone through the undefined
symbol list from the app to the library. You need to go through all the
undefined symbols in the library and if they are defined in the app, then mark
them as needed in the library before the comparison.
(I haven't looked at the weak mode checking)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-19 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 21:54 [Bug default/27208] New: " woodard at redhat dot com
2021-01-19 21:56 ` [Bug default/27208] " woodard at redhat dot com
2021-01-19 22:12 ` woodard at redhat dot com [this message]
2021-03-04 18:12 ` woodard at redhat dot com
2021-05-17 18:14 ` woodard at redhat dot com
2021-05-17 18:45 ` [Bug default/27208] Eabicompat doesn't consider functions (or variables) whose symbol type is NOTYPE woodard at redhat dot com
2021-06-08 0:21 ` [Bug default/27208] abicompat " woodard at redhat dot com
2022-03-29 20:41 ` [Bug default/27208] abicompat doesn't consider references from the libraries to the main executable woodard at redhat dot com
2022-03-31 9:06 ` woodard at redhat dot com
2022-03-31 10:08 ` woodard at redhat dot com
2022-03-31 10:21 ` woodard 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-27208-9487-Exo9uZOXJi@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).