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

Fuzzer details

Fuzzer: fuzz_reader

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 82 31.5%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 178 68.4%
All colors 260 100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked Calltree index Parent function Callsite Largest blocked function
17 147 olefile.olefile.OleFileIO._open call site: 00147 olefile.olefile.OleFileIO.loadminifat
13 89 olefile.olefile.OleFileIO.loadfat_sect call site: 00089 olefile.olefile.OleFileIO.dumpsect
12 131 olefile.olefile.OleFileIO.loadfat call site: 00131 olefile.olefile.OleFileIO.dumpfat
6 191 olefile.olefile.OleStream.__init__ call site: 00191 olefile.olefile.OleFileIO._raise_defect
4 205 olefile.olefile.OleStream.__init__ call site: 00205 olefile.olefile.OleFileIO._raise_defect
3 4 olefile.olefile.isOleFile call site: 00004 .len
3 67 olefile.olefile.i16 call site: 00067 olefile.olefile.i16
3 255 olefile.olefile.OleFileIO.__init__ call site: 00255 olefile.olefile.OleFileIONotClosed.__init__
2 166 olefile.olefile.OleStream.__init__ call site: 00166 .len
2 178 olefile.olefile.OleStream.__init__ call site: 00178 olefile.olefile.OleFileIO._raise_defect
2 186 olefile.olefile.OleStream.__init__ call site: 00186 olefile.olefile.OleFileIO._raise_defect
1 9 olefile.olefile.isOleFile call site: 00009 .len

Runtime coverage analysis

Covered functions
Functions that are reachable but not covered
Reachable functions
Percentage of reachable functions covered
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
/ 1
...fuzz_reader 5
olefile.olefile 59