tracker/README at master · perror/tracker · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
                                Tracker Project
                               =================

'tracker' is a binary analysis tool that uses dynamic and static approaches to
get an as complete as possible disassembly of a binary with a minimum of false
positive instructions gathered (tracker must provide a proof that every single
trace it displays can be executable for real with an input that trigger its
execution).

It uses a fuzzer to extract a first couple of traces from the given binary and,
then, provides new inputs to the fuzzer with the help of static-analysis
techniques (symbolic execution and abstract interpretation applied on a CFG
extracted from previous traces).


Build the project for users
---------------------------
This project requires meson-build, the capstone library and a Linux platform.
To build it:

#> cd tracker/
#> meson --buildtype=release --prefix=/usr/local _build ./
#> cd _build/
#> ninja
#> ninja install


Build the project for developer
-------------------------------
Build the software and run the tests (buildtype: 'debug' or 'debugoptimized'):

#> cd tracker/
# meson --buildtype=debug _build .
#> cd _build/
#> ninja
#> ninja test

Run valgrind on the tests:

#> meson test --wrap='valgrind --leak-check=full --track-origins=yes --error-exitcode=1'

Having the tests with code coverage:

#> cd tracker/
# meson --buildtype=debug -Db_coverage=true _build ./
#> cd _build/
#> ninja
#> ninja test
#> ninja coverage-html
#> firefox meson-logs/coveragereport/index.html

Formatting the code with clang-format:

#> ninja clang-format

Perform some static-analysis on the code:
#> ninja clang-tidy


Reporting bugs
--------------
Bugs must be reported to Emmanuel Fleury <emmanuel.fleury@u-bordeaux.fr>