This is similar and kind of related to 27208 but goes a bit deeper. abicompat currently only compares one library at a time when evaluating library compatibility. For example: abicompat app libfoo-v1 libfoo-v2 The app is also likely to have other dependencies which require ABI artifacts out of libfoo that the app itself may not use. app requires libfoo.so and libbar.so app only uses foo_init() libbar uses additional functions out of libfoo.so Currently abicompat would say that app is compatible with libfoo so long as foo_init() didn't change. However, if libfoo-v2 had changes that impacted libbar.so which is needed by the app then libfoo-v2 is not compatible with the app. Therefore the comparison currently done by abicompat where it simply looks at the undefined symbols in the app is not sufficient to guarantee that libfoo-v1 and libfoo-v2 are in fact compatible with the application. It must also look at the dependencies needed by app and include any symbols provided by them. To be able to address this problem while not breaking current behavior a new mode of operation is needed for abicompat one that loads the corpora not just for the app but also for all its dependencies and then does the abi comparison.
I would argue that this is a very important bug because it points out that all analysis that has been done with abicompat is potentially invalid. To address this problem I have been working on a branch which does this. It can be found here: https://github.com/woodard/libabigail/tree/newabicompat
To be able to do the full closure computation without the original ELF binaries the abixml file is required to include the undefined symbols.
The abixml file must include the undefined symbols in order to do the full closure computation without the original ELF binaries. By the way, if you're interested in One Year Masters Programs Online click the link https://www.onlinemasterscolleges.com/one-year-masters-programs-online