Quickstart

This document will go through building and running Sigil2.

Building Sigil2

Note

The default compiler for CentOS 7 and older (gcc <5) does not support C++14. Install and enable the offical Devtoolset before compiling.

Clone and build Sigil2 from source:

$ git clone https://github.com/VANDAL/sigil2
$ cd sigil2
$ mkdir build && cd build
$ cmake{3} .. # CentOS 7 requires cmake3 package
$ make -j

This creates a build/bin folder containing the sigil2 executable. It can be run in place, or the entire bin folder can be moved, although it’s not advised to move it to a system location.

Running Sigil2

Sigil2 requires at least two arguments: the backend analysis tool, and the executable application to measure:

$ bin/sigil2 --backend=stgen --executable=./mybinary

The backend is the analysis tool that will process all the events in mybinary. In this example, stgen is the backend that processes events into a special event trace that is used in SynchroTrace.

More information on backends are in The Analysis Backend.

A third option frontend will change the underlying method for observing the application. By default, this is Valgrind:

$ bin/sigil2 --frontend=valgrind --backend=stgen --executable=./mybinary

Available frontends are discussed in The Profiling Frontend.

Dependencies

PACKAGE VERSION
gcc/g++ 5+
cmake 3.1.3+
make 3.8+
automake 1.13+
autoconf 2.69+
zlib 1.27+
git 1.8+