High level conclusions

Fuzzers reach 87.01% of cyclomatic complexity.

Fuzzers reach 80.0% of all functions.

Fuzzer minigzip_fuzzer is blocked:

The runtime code coverage of minigzip_fuzzer covers 0.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer example_dict_fuzzer is blocked:

The runtime code coverage of example_dict_fuzzer covers 0.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer gzio_fuzzer is blocked:

The runtime code coverage of gzio_fuzzer covers 0.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer example_small_fuzzer is blocked:

The runtime code coverage of example_small_fuzzer covers 0.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer compress_fuzzer is blocked:

The runtime code coverage of compress_fuzzer covers 0.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer example_flush_fuzzer is blocked:

The runtime code coverage of example_flush_fuzzer covers 0.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Reachability and coverage overview

Functions statically reachable by fuzzers

132 / 165

Cyclomatic complexity statically reachable by fuzzers

1380 / 1586

Runtime code coverage of functions

68 / 165

The following table shows data about each function in the project. The functions included in this table correspond to all functions that exist in the executables of the fuzzers. As such, there may be functions that are from third-party libraries.

For further technical details on the meaning of columns in the below table, please see the Glossary .

Func name	Functions filename	Args	Function call depth	Reached by Fuzzers	Runtime reached by Fuzzers	Combined reached by Fuzzers	Fuzzers runtime hit	Func lines hit %	I Count	BB Count	Cyclomatic complexity	Functions reached	Reached by functions	Accumulated cyclomatic complexity	Undiscovered complexity

Fuzzer: example_flush_fuzzer

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	165	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	165	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
164	0	EP	call site: 00000	test_flush

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

63

Reachable functions

63

Percentage of reachable functions covered

0.0%

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
example_flush_fuzzer.c	3
zlib/compress.c	1
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	12
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: compress_fuzzer

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	157	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	157	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
156	0	EP	call site: 00000	check_compress_level

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

66

Reachable functions

66

Percentage of reachable functions covered

0.0%

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
compress_fuzzer.c	4
zlib/compress.c	2
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/uncompr.c	2
zlib/inflate.c	10
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: example_small_fuzzer

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	159	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	159	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
158	0	EP	call site: 00000	test_deflate

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

62

Reachable functions

62

Percentage of reachable functions covered

0.0%

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
example_small_fuzzer.c	3
zlib/compress.c	1
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	10
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/light/source_fileschecksum_fuzzer.c

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	7	14.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	85.1%
All colors	47	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00002	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00000	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00000	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00000	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00000	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00000	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00000	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00000	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00000	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

3

Reachable functions

18

Percentage of reachable functions covered

83.33%

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
inspector/light/source_fileschecksum_fuzzer.c	1
zlib/crc32.c	12
zlib/adler32.c	4

Fuzzer: inspector/source-codezlib_uncompress2_fuzzer.cc

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	18	36.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	32	64.0%
All colors	50	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00013	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00000	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00036	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00000	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00000	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00000	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00000	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00000	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00000	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

2

Reachable functions

21

Percentage of reachable functions covered

90.48%

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
inspector/source-codezlib_uncompress2_fuzzer.cc	1
zlib/uncompr.c	1
zlib/inflate.c	10
zlib/crc32.c	5
zlib/adler32.c	2
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/source-codecompress_fuzzer.c

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	74	47.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	83	52.8%
All colors	157	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00014	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00099	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00137	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00054	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00007	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00062	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00065	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00082	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00034	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

13

Reachable functions

66

Percentage of reachable functions covered

80.3%

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
inspector/source-codecompress_fuzzer.c	4
zlib/compress.c	2
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/uncompr.c	2
zlib/inflate.c	10
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/light/source_fileszlib_uncompress_fuzzer.cc

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	18	35.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	33	64.7%
All colors	51	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00014	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00000	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00037	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00000	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00000	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00000	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00000	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00000	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00000	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

2

Reachable functions

22

Percentage of reachable functions covered

90.91%

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
inspector/light/source_fileszlib_uncompress_fuzzer.cc	1
zlib/uncompr.c	2
zlib/inflate.c	10
zlib/crc32.c	5
zlib/adler32.c	2
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/light/source_filesexample_large_fuzzer.c

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	66	39.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	0.59%
lawngreen	50+	100	59.8%
All colors	167	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00012	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00098	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00150	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00053	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00005	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00061	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00064	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00081	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00033	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00034	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00034	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00034	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

7

Reachable functions

61

Percentage of reachable functions covered

88.52%

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
inspector/light/source_filesexample_large_fuzzer.c	3
zlib/deflate.c	17
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	10
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/light/source_filesexample_flush_fuzzer.c

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	86	52.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	79	47.8%
All colors	165	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00013	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00099	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00141	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00054	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00006	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00062	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00065	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00082	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00034	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

12

Reachable functions

63

Percentage of reachable functions covered

80.95%

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
inspector/light/source_filesexample_flush_fuzzer.c	3
zlib/compress.c	1
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	12
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/source-codeexample_large_fuzzer.c

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	66	39.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	0.59%
lawngreen	50+	100	59.8%
All colors	167	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00012	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00098	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00150	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00053	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00005	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00061	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00064	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00081	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00033	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00034	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00034	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00034	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

7

Reachable functions

61

Percentage of reachable functions covered

88.52%

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
inspector/source-codeexample_large_fuzzer.c	3
zlib/deflate.c	17
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	10
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/source-codeminigzip_fuzzer.c

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	186	70.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	77	29.2%
All colors	263	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00044	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00142	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00227	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00097	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00037	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00105	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00108	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00125	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00077	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00078	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00078	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00078	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

51

Reachable functions

100

Percentage of reachable functions covered

49.0%

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
inspector/source-codeminigzip_fuzzer.c	6
zlib/gzlib.c	5
zlib/gzwrite.c	6
zlib/deflate.c	15
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/gzclose.c	1
zlib/gzread.c	9
zlib/inflate.c	9
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/light/source_fileszlib_uncompress2_fuzzer.cc

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	18	36.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	32	64.0%
All colors	50	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00013	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00000	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00036	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00000	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00000	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00000	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00000	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00000	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00000	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

2

Reachable functions

21

Percentage of reachable functions covered

90.48%

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
inspector/light/source_fileszlib_uncompress2_fuzzer.cc	1
zlib/uncompr.c	1
zlib/inflate.c	10
zlib/crc32.c	5
zlib/adler32.c	2
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: checksum_fuzzer

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	7	14.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	85.1%
All colors	47	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00002	/src/zlib/crc32.c:731
0	0	None	0	0	adler32_combine_	call site: 00045	/src/zlib/adler32.c:139

Runtime coverage analysis

Covered functions

15

Functions that are reachable but not covered

3

Reachable functions

18

Percentage of reachable functions covered

83.33%

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
checksum_fuzzer.c	1
zlib/crc32.c	12
zlib/adler32.c	4

Fuzzer: zlib_uncompress_fuzzer

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	24	47.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	27	52.9%
All colors	51	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
252	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	252	474	inflate	call site: 00037	/src/zlib/inflate.c:817
0	0	None	252	474	inflate	call site: 00012	/src/zlib/inflate.c:623
0	0	None	252	474	inflate	call site: 00012	/src/zlib/inflate.c:629
0	0	None	252	474	inflate	call site: 00027	/src/zlib/inflate.c:638
0	0	None	252	474	inflate	call site: 00027	/src/zlib/inflate.c:656
0	0	None	252	474	inflate	call site: 00043	/src/zlib/inflate.c:1137
0	0	None	21	46	inflate	call site: 00039	/src/zlib/inflate.c:847
0	0	None	0	369	uncompress2	call site: 00002	/src/zlib/uncompr.c:36
0	0	None	0	15	inflateReset2	call site: 00006	/src/zlib/inflate.c:150
0	0	None	0	15	inflateReset2	call site: 00006	/src/zlib/inflate.c:167
0	0	None	0	12	uncompress2	call site: 00011	/src/zlib/uncompr.c:70
0	0	None	0	0	adler32_z	call site: 00029	/src/zlib/adler32.c:72

Runtime coverage analysis

Covered functions

22

Functions that are reachable but not covered

5

Reachable functions

22

Percentage of reachable functions covered

77.27%

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
zlib_uncompress_fuzzer.cc	1
zlib/uncompr.c	2
zlib/inflate.c	10
zlib/crc32.c	5
zlib/adler32.c	2
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/light/source_filesexample_dict_fuzzer.c

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	91	53.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	78	46.1%
All colors	169	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00009	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00104	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00145	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00063	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00002	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00034	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00072	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00087	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00043	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00044	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00044	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00044	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

13

Reachable functions

63

Percentage of reachable functions covered

79.37%

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
inspector/light/source_filesexample_dict_fuzzer.c	3
zlib/deflate.c	17
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	11
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/source-codeexample_flush_fuzzer.c

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	86	52.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	79	47.8%
All colors	165	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00013	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00099	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00141	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00054	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00006	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00062	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00065	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00082	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00034	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

12

Reachable functions

63

Percentage of reachable functions covered

80.95%

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
inspector/source-codeexample_flush_fuzzer.c	3
zlib/compress.c	1
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	12
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/source-codechecksum_fuzzer.c

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	7	14.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	85.1%
All colors	47	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00002	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00000	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00000	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00000	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00000	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00000	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00000	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00000	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00000	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

3

Reachable functions

18

Percentage of reachable functions covered

83.33%

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
inspector/source-codechecksum_fuzzer.c	1
zlib/crc32.c	12
zlib/adler32.c	4

Fuzzer: gzio_fuzzer

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	273	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	273	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
272	0	EP	call site: 00000	gzclose

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

109

Reachable functions

109

Percentage of reachable functions covered

0.0%

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
gzio_fuzzer.c	1
zlib/gzlib.c	15
zlib/gzwrite.c	12
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/gzread.c	13
zlib/inflate.c	9
zlib/inftrees.c	1
zlib/inffast.c	1
zlib/gzclose.c	1

Fuzzer: example_dict_fuzzer

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	169	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	169	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
168	0	EP	call site: 00000	test_dict_deflate

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

63

Reachable functions

63

Percentage of reachable functions covered

0.0%

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
example_dict_fuzzer.c	3
zlib/deflate.c	17
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	11
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: zlib_uncompress2_fuzzer

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	24	48.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	2	4.0%
lawngreen	50+	24	48.0%
All colors	50	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
252	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	252	474	inflate	call site: 00036	/src/zlib/inflate.c:817
0	0	None	252	474	inflate	call site: 00011	/src/zlib/inflate.c:623
0	0	None	252	474	inflate	call site: 00011	/src/zlib/inflate.c:629
0	0	None	252	474	inflate	call site: 00026	/src/zlib/inflate.c:638
0	0	None	252	474	inflate	call site: 00026	/src/zlib/inflate.c:656
0	0	None	252	474	inflate	call site: 00042	/src/zlib/inflate.c:1137
0	0	None	21	46	inflate	call site: 00038	/src/zlib/inflate.c:847
0	0	None	0	369	uncompress2	call site: 00001	/src/zlib/uncompr.c:36
0	0	None	0	15	inflateReset2	call site: 00005	/src/zlib/inflate.c:150
0	0	None	0	15	inflateReset2	call site: 00005	/src/zlib/inflate.c:167
0	0	None	0	12	uncompress2	call site: 00010	/src/zlib/uncompr.c:70
0	0	None	0	0	adler32_z	call site: 00028	/src/zlib/adler32.c:72

Runtime coverage analysis

Covered functions

21

Functions that are reachable but not covered

5

Reachable functions

21

Percentage of reachable functions covered

76.19%

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
zlib_uncompress2_fuzzer.cc	1
zlib/uncompr.c	1
zlib/inflate.c	10
zlib/crc32.c	5
zlib/adler32.c	2
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/light/source_filescompress_fuzzer.c

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	74	47.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	83	52.8%
All colors	157	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00014	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00099	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00137	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00054	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00007	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00062	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00065	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00082	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00034	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

13

Reachable functions

66

Percentage of reachable functions covered

80.3%

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
inspector/light/source_filescompress_fuzzer.c	4
zlib/compress.c	2
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/uncompr.c	2
zlib/inflate.c	10
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: example_large_fuzzer

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	68	40.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	0.59%
lawngreen	50+	98	58.6%
All colors	167	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
21	21	1 : View List ['crc32']	472	630	deflate	call site: 00053	/src/zlib/deflate.c:1160
21	21	1 : View List ['crc32']	21	21	read_buf	call site: 00061	/src/zlib/deflate.c:227
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00098	/src/zlib/deflate.c:1212
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00005	/src/zlib/deflate.c:499
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00064	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00081	/src/zlib/trees.c:1047
0	0	None	640	879	deflate	call site: 00033	/src/zlib/deflate.c:974
0	0	None	640	869	deflate	call site: 00034	/src/zlib/deflate.c:1009
0	0	None	640	869	deflate	call site: 00034	/src/zlib/deflate.c:1011
0	0	None	640	869	deflate	call site: 00034	/src/zlib/deflate.c:1013
0	0	None	640	867	deflate	call site: 00037	/src/zlib/deflate.c:1024
0	0	None	640	838	deflate	call site: 00041	/src/zlib/deflate.c:1039

Runtime coverage analysis

Covered functions

55

Functions that are reachable but not covered

10

Reachable functions

61

Percentage of reachable functions covered

83.61%

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
example_large_fuzzer.c	3
zlib/deflate.c	17
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	10
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/light/source_filesgzio_fuzzer.c

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	189	69.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	0.36%
lawngreen	50+	83	30.4%
All colors	273	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00028	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00123	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00190	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00078	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00021	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00086	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00089	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00106	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00058	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00059	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00059	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00059	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

59

Reachable functions

109

Percentage of reachable functions covered

45.87%

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
inspector/light/source_filesgzio_fuzzer.c	1
zlib/gzlib.c	15
zlib/gzwrite.c	12
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/gzread.c	13
zlib/inflate.c	9
zlib/inftrees.c	1
zlib/inffast.c	1
zlib/gzclose.c	1

Fuzzer: inspector/light/source_filesminigzip_fuzzer.c

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	186	70.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	77	29.2%
All colors	263	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00044	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00142	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00227	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00097	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00037	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00105	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00108	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00125	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00077	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00078	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00078	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00078	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

51

Reachable functions

100

Percentage of reachable functions covered

49.0%

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
inspector/light/source_filesminigzip_fuzzer.c	6
zlib/gzlib.c	5
zlib/gzwrite.c	6
zlib/deflate.c	15
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/gzclose.c	1
zlib/gzread.c	9
zlib/inflate.c	9
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/light/source_filesexample_small_fuzzer.c

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	80	50.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	79	49.6%
All colors	159	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00013	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00099	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00141	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00054	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00006	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00062	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00065	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00082	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00034	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

11

Reachable functions

62

Percentage of reachable functions covered

82.26%

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
inspector/light/source_filesexample_small_fuzzer.c	3
zlib/compress.c	1
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	10
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/source-codeexample_dict_fuzzer.c

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	91	53.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	78	46.1%
All colors	169	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00009	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00104	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00145	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00063	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00002	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00034	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00072	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00087	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00043	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00044	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00044	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00044	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

13

Reachable functions

63

Percentage of reachable functions covered

79.37%

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
inspector/source-codeexample_dict_fuzzer.c	3
zlib/deflate.c	17
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	11
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: minigzip_fuzzer

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	263	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	263	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
262	0	EP	call site: 00000	file_uncompress

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

100

Reachable functions

100

Percentage of reachable functions covered

0.0%

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
minigzip_fuzzer.c	6
zlib/gzlib.c	5
zlib/gzwrite.c	6
zlib/deflate.c	15
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/gzclose.c	1
zlib/gzread.c	9
zlib/inflate.c	9
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/source-codezlib_uncompress_fuzzer.cc

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	18	35.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	33	64.7%
All colors	51	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00014	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00000	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00037	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00000	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00000	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00000	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00000	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00000	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00000	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00000	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

2

Reachable functions

22

Percentage of reachable functions covered

90.91%

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
inspector/source-codezlib_uncompress_fuzzer.cc	1
zlib/uncompr.c	2
zlib/inflate.c	10
zlib/crc32.c	5
zlib/adler32.c	2
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/source-codeexample_small_fuzzer.c

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	80	50.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	79	49.6%
All colors	159	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00013	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00099	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00141	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00054	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00006	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00062	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00065	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00082	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00034	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00035	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

11

Reachable functions

62

Percentage of reachable functions covered

82.26%

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
inspector/source-codeexample_small_fuzzer.c	3
zlib/compress.c	1
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/inflate.c	10
zlib/inftrees.c	1
zlib/inffast.c	1

Fuzzer: inspector/source-codegzio_fuzzer.c

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	189	69.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	0.36%
lawngreen	50+	83	30.4%
All colors	273	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
14	14	2 : View List ['byte_swap', 'crc_word_big']	14	14	crc32_z	call site: 00028	/src/zlib/crc32.c:731
7	7	1 : View List ['_tr_align']	7	31	deflate	call site: 00123	/src/zlib/deflate.c:1212
0	474	6 : View List ['updatewindow', 'crc32', 'inflate_table', 'fixedtables', 'inflate_fast', 'adler32']	0	474	inflate	call site: 00190	/src/zlib/inflate.c:817
0	21	1 : View List ['crc32']	451	630	deflate	call site: 00078	/src/zlib/deflate.c:1160
0	21	1 : View List ['deflateEnd']	0	21	deflateInit2_	call site: 00021	/src/zlib/deflate.c:499
0	21	1 : View List ['crc32']	0	21	read_buf	call site: 00086	/src/zlib/deflate.c:227
0	17	2 : View List ['_tr_stored_block', 'flush_pending']	0	17	deflate_stored	call site: 00089	/src/zlib/deflate.c:1800
0	7	1 : View List ['_tr_stored_block']	0	14	_tr_flush_block	call site: 00106	/src/zlib/trees.c:1047
0	0	None	451	879	deflate	call site: 00058	/src/zlib/deflate.c:974
0	0	None	451	869	deflate	call site: 00059	/src/zlib/deflate.c:1009
0	0	None	451	869	deflate	call site: 00059	/src/zlib/deflate.c:1011
0	0	None	451	869	deflate	call site: 00059	/src/zlib/deflate.c:1013

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

59

Reachable functions

109

Percentage of reachable functions covered

45.87%

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
inspector/source-codegzio_fuzzer.c	1
zlib/gzlib.c	15
zlib/gzwrite.c	12
zlib/deflate.c	16
zlib/crc32.c	5
zlib/adler32.c	2
zlib/trees.c	20
zlib/gzread.c	13
zlib/inflate.c	9
zlib/inftrees.c	1
zlib/inffast.c	1
zlib/gzclose.c	1