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

Fuzzer details

Fuzzer: fuzz_parsing

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 76 54.2%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 64 45.7%
All colors 140 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
47 24 netaddr.strategy.ipv6.str_to_int call site: 00024 netaddr.fbsocket._inet_pton_af_inet
12 92 netaddr.ip.parse_ip_network call site: 00092 netaddr.ip.cidr_abbrev_to_verbose
4 14 netaddr.ip.IPAddress.__init__ call site: 00014 .int
4 116 netaddr.ip.parse_ip_network call site: 00116 netaddr.ip.IPAddress.__init__
2 130 netaddr.strategy.ipv4.str_to_int call site: 00130 .int
1 9 netaddr.ip.IPAddress.__init__ call site: 00009 .isinstance
1 77 netaddr.ip.IPAddress.__init__ call site: 00077 .int
1 82 netaddr.strategy.ipv4.str_to_int call site: 00082 .int
1 88 netaddr.ip.IPNetwork.__init__ call site: 00088 netaddr.ip.parse_ip_network
1 90 netaddr.ip.parse_ip_network call site: 00090 .len
1 123 netaddr.strategy.ipv4.str_to_int call site: 00123 netaddr.ip.IPNetwork.__init__
1 125 netaddr.strategy.ipv4.str_to_int call site: 00125 .int

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.
Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.
Function name source code lines source lines hit percentage hit

Files reached

filename functions hit
/ 1
...fuzz_parsing 7
netaddr.ip 20
netaddr.compat 2
netaddr.strategy.ipv6 7
netaddr.fbsocket 18
netaddr.strategy.ipv4 17