Static analysis tool to detect ABI breaks in C++ [closed]

by

abi-compliance-checker – a tool for checking backward binary/source-level compatibility of a shared C/C++ library (DSO):

A tool for checking backward binary and source-level compatibility of a C/C++ library. The tool checks header files and shared libraries of old and new versions and analyzes changes in API and ABI (ABI=API+compiler ABI) that may break binary and/or source compatibility: changes in calling stack, v-table changes, removed symbols, renamed fields, etc.

enter image description here

icheck – C interface ABI/API checker:

A tool for statically checking C interfaces for API and ABI changes. All changes to type declarations that can cause ABI changes should be detected, along with most API changes.
icheck is intended for use with libraries, as a method of preventing ABI drift.

shlib-compat – ABI compatibility checker for shared libraries with symbol versioning:

shlib-compat uses dwarf debugging symbols to recreate and compare definitions of exported
symbols, including function arguments and structural types.

Also you might be interested in the linux upstream tracker and linux abi tracker services. They are both powered by the abi-compliance-checker tool.

More Related Contents:

  1. Using includes with c++ shared libraries
  2. How to add additional libraries to Visual Studio project?
  3. Difference between static and shared libraries?
  4. C/C++ with GCC: Statically add resource files to executable/library
  5. What open source C++ static analysis tools are available? [closed]
  6. When to use dynamic vs. static libraries
  7. C++ Dynamic Shared Library on Linux
  8. How to Generate a calling graph for C++ code
  9. How do you find what version of libstdc++ library is installed on your linux machine?
  10. Force GCC to notify about undefined references in shared libraries
  11. Linking a shared library with another shared lib in linux
  12. Compilation fails with “relocation R_X86_64_32 against `.rodata.str1.8′ can not be used when making a shared object”
  13. How to check what shared libraries are loaded at run time for a given process?
  14. How to raise warning if return value is disregarded?
  15. Dead code detection in legacy C/C++ project [closed]
  16. Elegantly call C++ from C
  17. std::vector, default construction, C++11 and breaking changes
  18. How to create a shared library with cmake?
  19. How to link using GCC without -l nor hardcoding path for a library that does not follow the libNAME.so naming convention?
  20. What are good practices regarding shared libraries on Linux?
  21. Why does aggregate initialization not work anymore since C++20 if a constructor is explicitly defaulted or deleted?
  22. “relocation R_X86_64_32S against ” linking Error
  23. cmake find_package specify path
  24. Why is CMake designed so that it removes runtime path when installing
  25. Load 32-bit shared library from 64-bit application?
  26. Convert a Static Library to a Shared Library (create libsome.so from libsome.a): where’s my symbols?
  27. Dead code identification (C++)
  28. What does exactly the warning mean about hidden symbol being referenced by DSO?
  29. can’t extract data from a structure array c++ [closed]
  30. How do I iterate over the words of a string?

Leave a Comment