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

Fuzzer details

Fuzzer: fuzz_h11

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 142 79.3%
gold [1:9] 0 0.0%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 37 20.6%
All colors 179 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
59 77 h11._connection._body_framing call site: 00077 h11._connection.Connection._process_event
21 137 h11._connection._keep_alive call site: 00137 h11._connection.Connection._process_error
15 18 h11._util.validate call site: 00018 h11._util.validate
9 160 ...fuzz_h11.fuzz_connection call site: 00160 h11._connection.Connection._process_event
8 7 ...fuzz_h11.fuzz_headers call site: 00007 h11._util.bytesify
7 69 ...fuzz_h11.fuzz_connection call site: 00069 h11._connection.Connection.send_with_data_passthrough
6 45 h11._events.Request.__init__ call site: 00045 h11._util.bytesify
5 34 ...fuzz_h11.fuzz_headers call site: 00034 h11._headers.get_comma_header
3 53 h11._events.Request.__init__ call site: 00053 h11._util.validate
3 171 ...fuzz_h11.fuzz_connection call site: 00171 h11._connection.Connection.send
2 4 ...fuzz_h11.fuzz_headers call site: 00004 fdp.ConsumeBytes
2 176 ...fuzz_h11.fuzz_connection call site: 00176 h11._connection.Connection.receive_data

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_h11 18
h11._headers 18
h11._util 7
h11._events 9
h11._receivebuffer 1
h11._connection 33
h11._state 6