ABI Compliance Checker (ABICC) — a tool for checking backward binary and source-level compatibility of a C/C++ software library.
The tool analyzes changes in API/ABI (ABI=API+compiler ABI) that may break binary compatibility and/or source compatibility: changes in calling stack, v-table changes, removed symbols, renamed fields, etc.
The tool can create and compare ABI dumps for header files and shared objects of a library. The ABI dump for a library can also be created by the ABI Dumper tool (https://github.com/lvc/abi-dumper) if shared objects include debug-info.
The tool is intended for developers of software libraries and Linux maintainers who are interested in ensuring backward compatibility, i.e. allow old applications to run or to be recompiled with newer library versions.
The tool is a core of the ABI Tracker and Upstream Tracker projects: https://abi-laboratory.pro/tracker/
The tool is developed by Andrey Ponomarenko.
sudo make install prefix=/usr
- Perl 5
- GCC C++ (3.0 or newer)
- GNU Binutils
- ABI Dumper (1.1 or newer)
- Mac OS X
With ABI Dumper
Library should be compiled with
-g -OgGCC options to contain DWARF debug info
Create ABI dumps for both library versions using the ABI Dumper (https://github.com/lvc/abi-dumper) tool:
abi-dumper OLD.so -o ABI-1.dump -lver 1 abi-dumper NEW.so -o ABI-2.dump -lver 2
You can filter public ABI with the help of additional
-public-headersoption of the ABI Dumper tool
Compare ABI dumps to create report:
abi-compliance-checker -l NAME -old ABI-1.dump -new ABI-2.dump
abi-compliance-checker -lib NAME -old OLD.xml -new NEW.xml
NEW.xml are XML-descriptors:
<version> 1.0 </version> <headers> /path/to/headers/ </headers> <libs> /path/to/libraries/ </libs>
For advanced usage, see
doc/index.html or output of
The tool is tested properly in the ABI Tracker and Upstream Tracker projects, by the community and by the internal test suite:
There are about 100 test cases for C and 200 test cases for C++ API/ABI breaks.