abilint parses the native XML representation of an ABI as emitted by
abidw. Once it has parsed the XML representation of the ABI,
abilint builds and in-memory model from it. It then tries to save
it back to an XML form, to standard output. If that read-write
operation succeeds chances are the input XML ABI representation is
Note that the main intent of this tool to help debugging issues in the underlying Libabigail library.
Note also that
abilint can also read an ELF input file, build the
in-memory model for its ABI, and serialize that model back into XML to
standard output. In that case, the ELF input file must be
accompanied with its debug information in the DWARF format.
abilint [options] [<abi-file1>]
Display a short help message and exits.
–version | -v
Display the version of the program and exit.
When reading an ELF input file which debug information is split out into a separate file, this options tells
abilintwhere to find that separate debug information file.
Note that path must point to the root directory under which the debug information is arranged in a tree-like manner. Under Red Hat based systems, that directory is usually
Note also that this option is not mandatory for split debug information installed by your system’s package manager because then
abidiffknows where to find it.
For XML inputs, perform a text diff between the input and the memory model saved back to disk. This can help to spot issues in the handling of the XML format by the underlying Libabigail library.
Do not display anything on standard output. The return code of the command is the only way to know if the command succeeded.
--suppressions | suppr<path-to-suppression-specifications-file>
Use a suppression specification file located at path-to-suppression-specifications-file. Note that this option can appear multiple times on the command line. In that case, all of the provided suppression specification files are taken into account. ABI artifacts matched by the suppression specifications are suppressed from the output of this tool.
--headers-dir | --hd<headers-directory-path-1>
Specifies where to find the public headers of the first shared library that the tool has to consider. The tool will thus filter out types that are not defined in public headers.
--header-file | --hf<header-file-path>
Specifies where to find one of the public headers of the abi file that the tool has to consider. The tool will thus filter out types that are not defined in public headers.
--stdin | --
Read the input content from standard input.
Expect the input XML to represent a single translation unit.
Extract ABI information from CTF debug information, if present in the given object.