Clone this repo:
  1. 9db842f Merge branch 'upstream-master' into 'main' by Giuliano Procida · 10 days ago main master
  2. b0ca59d remove stg and stgdiff --skip-dwarf option cont. by Giuliano Procida · 10 days ago upstream-master
  3. ae51ba1 test cases: add mutant qualifier typedef array test by Giuliano Procida · 10 days ago
  4. c89581f test cases: preserve type definition in array/simple_array test case by Giuliano Procida · 13 days ago
  5. 585b57e test cases: simplify reference/type_and_type diff test by Giuliano Procida · 13 days ago

Symbol-Type Graph (STG)

The STG (symbol-type graph) is an ABI representation and this project contains tools for the creation and comparison of such representations.

The ABI extraction tool, stg, emits a native ABI format. Parsers exist for libabigail's XML format, BTF and ELF / DWARF.

The ABI diff tool, stgdiff, supports multiple reporting options.

STG has a versioned native file format. Older formats can be read and rewritten as the latest.

NOTE: STG is under active developement. Tool arguments and behaviour are subject to change.

Getting STG


We intend to package STG for major distributions. Currently we have packages as follows:

Arch Linux (AUR)stg-git

Source Code

This source code is available at

Building from Source

Instructions are included for local and Docker builds.


STG is written in C++20. It is known to compile with GCC 11, Clang 14 or later versions.

ELF, BTFlibelf-develfutils-devel
native formatlibprotobuf-devprotobuf-devel
native formatprotobuf-compilerprotobuf-compiler

[^1]: jemalloc is optional, but will likely improve performance. [^2]: catch2 is optional, but required to build the test suite.

Local Build

Build STG using CMake as follows:

$ mkdir build && cd build
$ cmake ..
$ cmake --build . --parallel

Run the STG unit test suite:

$ ctest

Docker Build

A Dockerfile is provided to build a container with the STG tools:

$ docker build -t stg .

And then enter the container:

$ docker run -it stg

Note that the Dockerfile provides only a production image. To use Docker as a development environment, you can comment out everything after the line # second stage.

After that you may bind your development code to the container:

$ docker run -it $PWD:/src -it stg

The source code is added to /src, so when your code is bound you can edit on your host and re-compile in the container.


See for details.

Contact Information

Please send feedback, questions and bug reports to