Fuzz introspector
For issues and ideas: https://github.com/ossf/fuzz-introspector/issues

Fuzzer details

Fuzzer: bzip2_decompress_target

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 9 23.0%
gold [1:9] 0 0.0%
yellow [10:29] 1 2.56%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 29 74.3%
All colors 39 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
0 0 None 0 369 BZ2_bzDecompress call site /src/bzip2/bzlib.c:826
0 0 None 0 19 BZ2_decompress call site /src/bzip2/decompress.c:238
0 0 None 0 0 BZ2_bzDecompress call site /src/bzip2/bzlib.c:844
0 0 None 0 0 BZ2_bzBuffToBuffDecompress call site /src/bzip2/bzlib.c:1310
0 0 None 0 0 unRLE_obuf_to_output_FAST call site /src/bzip2/bzlib.c:666
0 0 None 0 0 BZ2_decompress call site /src/bzip2/decompress.c:512
0 0 None 0 0 BZ2_decompress call site /src/bzip2/decompress.c:519

Runtime coverage analysis

Covered functions
14
Functions that are reachable but not covered
3
Reachable functions
16
Percentage of reachable functions covered
81.25%
NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
bzip2_decompress_target.c 1
bzip2/bzlib.c 12
bzip2/decompress.c 2
bzip2/huffman.c 1

Fuzzer: bzip2_compress_target

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is
Color Runtime hitcount Callsite count Percentage
red 0 43 26.2%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 121 73.7%
All colors 164 100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity Unique Reachable Complexities Unique Reachable Functions All non-covered Complexity All Reachable Complexity Function Name Function Callsite Blocked Branch
0 0 None 49 210 sendMTFValues call site /src/bzip2/compress.c:261
0 0 None 42 203 sendMTFValues call site /src/bzip2/compress.c:302
0 0 None 42 203 sendMTFValues call site /src/bzip2/compress.c:436
0 0 None 21 101 mainSort call site /src/bzip2/blocksort.c:893
0 0 None 14 132 sendMTFValues call site /src/bzip2/compress.c:513
0 0 None 14 124 sendMTFValues call site /src/bzip2/compress.c:525
0 0 None 14 116 sendMTFValues call site /src/bzip2/compress.c:541
0 0 None 7 80 BZ2_blockSort call site /src/bzip2/blocksort.c:1069
0 0 None 7 80 BZ2_blockSort call site /src/bzip2/blocksort.c:1076
0 0 None 7 43 fallbackSort call site /src/bzip2/blocksort.c:229
0 0 None 7 43 fallbackSort call site /src/bzip2/blocksort.c:263
0 0 None 7 43 fallbackSort call site /src/bzip2/blocksort.c:308

Runtime coverage analysis

Covered functions
46
Functions that are reachable but not covered
4
Reachable functions
49
Percentage of reachable functions covered
91.84%
NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
bzip2_compress_target.c 1
bzip2/bzlib.c 24
bzip2/compress.c 9
bzip2/blocksort.c 9
bzip2/huffman.c 3
bzip2/decompress.c 2