The tool is intended to be used with ABI Compliance Checker tool for tracking
ABI changes of a C/C++ library or kernel module.

The tool is developed by Andrey Ponomarenko: ;

Monitor new versions of a software library, try to build them
and create profiles for abi-tracker

This tool visualizes an ABI changes timeline of a C/C++ software library.

It requires input profile of the library in JSON format. It can be created
manually or automatically generated by the ABI Monitor.

bbe is a sed-like editor for binary files. Instead of reading input in
lines as sed, bbe reads arbitrary blocks from an input stream and performs
byte-related transformations on found blocks.

A library to support the benchmarking of functions, similar to unit-tests.

Cram is a functional testing framework for command line applications
based on Mercurial's `unified test format'.

Cram tests look like snippets of interactive shell sessions. Cram runs
each command and compares the command output in the test with the
command's actual output.

Gengetopt is a tool to generate C code to parse getopt styled command line
arguments.
It's similar or even more powerful than the well known libpopt but does not
add any run or compile time dependencies to your projects. Moreover
reading/writing the options from/to config files is also supported.

Security-oriented fuzzer with powerful analysis options. Supports
evolutionary, feedback-driven fuzzing based on code coverage
(software and hardware).

libb64 is a library of ANSI C routines for fast encoding/decoding data into and
from a base64-encoded format. C++ wrappers are included, as well as the source
code for standalone encoding and decoding executables.

msitools is a set of programs to inspect and build Windows Installer
(.MSI) files. It is based on libmsi, a portable library to read and
write .MSI files.

msitools plans to be a solution for packaging and deployment of
cross-compiled Windows applications.

The tool does the following:

1. Extracts input packages
2. Searches for *.debuginfo, *.so and header files
3. Creates ABI dumps of all found shared objects
4. Filters out private part of the ABI using info from header files
5. Matches shared objects in old and new packages
6. Compares ABI dumps of corresponding objects
7. Creates backward binary/source compatibility reports
The pkg-abidiff tool is based on the ABI Compliance Checker tool. It is executed on every shared object found in the RPM. You can find reports of the ABI Compliance Checker by following the links in the "Shared Objects" section of the output report: https://abi-laboratory.pro/examples/compat_report/x86_64/libssh4/0.5.3-2.1.1/0.6.3-8.1/

The ABI Compliance Checker tool is designed to compare particular shared objects (or debug info ABI dumps). The pkg-abidiff is designed to compare sets of shared objects in RPM packages. Also it searches for all necessary data in RPMs and provides all necessary options to ABI Compliance Checker.

A tool for visualizing changes in Linux software packages (RPM, DEB, TAR.GZ, etc).
The tool is intended for Linux maintainers who are interested in ensuring
compatibility of old and new versions of packages.

Radamsa is a test case generator for robustness testing, aka a fuzzer. It
can be used to test how well a program can stand malformed and potentially
malicious inputs. It operates based on given sample inputs and thus
requires minimal effort to set up. The main selling points of radamsa are
that it is easy to use, contains several old and new fuzzing algorithms, is
easy to script from command line and has already been used to find a slew
of bugs in programs that actually matter.

Rtags is Clang based source file indexer supporting C/C++/Objective-C(++) code.

Sysdig is open source, system-level exploration: capture system state and
activity from a running Linux instance, then save, filter and analyze.
Think of it as strace + tcpdump + lsof + awesome sauce. With a little Lua
cherry on top.

The basic idea is fairly simple. As 'fuzz testing' suggests, we call syscalls
at random, with random arguments. Not an original idea, and one that has been
done many times before on Linux, and on other operating systems. Where
Trinity differs is that the arguments it passes are not purely random.

Txt2man converts flat ASCII text to man page format. It is a shell
script using gnu awk, that should run on any Unix like system.

It is intended for developers of software libraries and maintainers of Linux
distributions who are interested in ensuring backward binary compatibility.

The tool is developed by Andrey Ponomarenko

Tools for building software

ccache is a compiler cache. It speeds up recompilation by caching the
result of previous compilations and detecting when the same compilation is
being done again. Supported languages are C, C++, Objective-C and
Objective-C++.

GYP is a tool to generates native Visual Studio, Xcode and SCons and/or make
build files from a platform-independent input format. Its syntax is a universal
cross-platform build representation that still allows sufficient per-platform
flexibility to accommodate irreconcilable differences

Various compilers

Various IDEs

Open source builds of the VSCode IDE and related software (currently the standalone language servers)

to quote wikipedia:
Software Configuration Management (SCM) is part of configuration management (CM). Roger Pressman (in his book) Software Engineering: A Practitioner's Approach, says that software configuration management (SCM) is a "set of activities designed to control change by identifying the work products that are likely to change, establishing relationships among them, defining mechanisms for managing different versions of these work products, controlling the changes imposed, and auditing and reporting on the changes made." In other words, SCM is a methodology to control and manage a software development project.

SCM concerns itself with answering the question: somebody did something, how can one reproduce it? Often the problem involves not reproducing "it" identically, but with controlled, incremental changes. Answering the question will thus become a matter of comparing different results and of analysing their differences. Traditional CM typically focused on controlled creation of relatively simple products. Nowadays, implementers of SCM face the challenge of dealing with relatively minor increments under their own control, in the context of the complex system being developed.