High level conclusions

Fuzzers reach 21.14% of cyclomatic complexity.

Fuzzers reach 4.705% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

12 / 255

Cyclomatic complexity statically reachable by fuzzers

74 / 350

Runtime code coverage of functions

96 / 255

Warning: The number of runtime covered functions are larger than the number of reachable functions. This means that Fuzz Introspector found there are more functions covered at runtime than what is considered reachable based on the static analysis. This is a limitation in the analysis as anything covered at runtime is by definition reachable by the fuzzers.
This is likely due to a limitation in the static analysis. In this case, the count of functions covered at runtime is the true value, which means this is what should be considered "achieved" by the fuzzer.

Use the project functions table below to query all functions that were not covered at runtime.

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: fuzz_roundtrip

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	19	59.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	13	40.6%
All colors	32	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
10	21	HashTable4KU16::new	call site: 00021	short_copy
4	14	lz4_flex::decompress_size_prepended	call site: 00014
3	5	super::uncompressed_size	call site: 00005
1	0	EP	call site: 00000
1	2	lz4_flex::compress_prepend_size	call site: 00002

Runtime coverage analysis

Covered functions

66

Functions that are reachable but not covered

2

Reachable functions

4

Percentage of reachable functions covered

50.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.

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
fuzz/fuzz_targets/fuzz_roundtrip.rs	4
src/block/compress.rs	3
src/block/decompress.rs	2
src/block/mod.rs	6
fuzz/fuzz_targets/fuzz_decomp_no_output_leak.rs	3
lz4_bin/src/main.rs	8
src/fastcpy.rs	5

Fuzzer: fuzz_roundtrip_cpp_compress

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	199	96.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	8	3.86%
All colors	207	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
117	0	EP	call site: 00000	FrameDecoder::read_to_end
59	131	SliceSink::capacity	call site: 00131	BlockInfo::read
12	118	SliceSink::extend_with_fill	call site: 00118	FrameDecoder::read_block
7	199	io::Result::extend_from_slice	call site: 00199
4	192	SliceSink::extend_from_slice_wild	call site: 00192	short_copy

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

5

Reachable functions

8

Percentage of reachable functions covered

37.5%

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
fuzz/fuzz_targets/fuzz_roundtrip_cpp_compress.rs	8
lz4_bin/src/main.rs	10
src/block/compress.rs	4
src/frame/decompress.rs	40
src/frame/header.rs	20
src/frame/compress.rs	1
src/block/hashtable.rs	1
src/sink.rs	6
src/fastcpy.rs	5

Fuzzer: fuzz_decomp_corrupt_block

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	196	94.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	12	5.76%
All colors	208	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
103	11	lz4_flex::frame::FrameDecoder::new	call site: 00011	FrameDecoder::read_to_end
59	128	SliceSink::capacity	call site: 00128	BlockInfo::read
12	115	SliceSink::extend_with_fill	call site: 00115	FrameDecoder::read_block
10	0	EP	call site: 00000
7	196	io::Result::extend_from_slice	call site: 00196
4	189	SliceSink::extend_from_slice_wild	call site: 00189	short_copy
1	206	lz4_flex::block::decompress_with_dict	call site: 00206

Runtime coverage analysis

Covered functions

62

Functions that are reachable but not covered

2

Reachable functions

5

Percentage of reachable functions covered

60.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.

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
fuzz/fuzz_targets/fuzz_decomp_corrupt_block.rs	5
lz4_bin/src/main.rs	10
src/block/compress.rs	4
src/frame/decompress.rs	40
src/frame/header.rs	20
src/frame/compress.rs	1
src/block/hashtable.rs	1
src/sink.rs	6
src/fastcpy.rs	5
src/block/decompress.rs	3

Fuzzer: fuzz_roundtrip_cpp_decompress

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	197	95.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	10	4.83%
All colors	207	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
118	8	HashTable4KU16::new	call site: 00008	FrameDecoder::read_to_end
59	127	SliceSink::capacity	call site: 00127	BlockInfo::read
11	195	io::Result::extend_from_slice	call site: 00195	FrameDecoder::read_to_end
5	0	EP	call site: 00000
4	188	SliceSink::extend_from_slice_wild	call site: 00188	short_copy

Runtime coverage analysis

Covered functions

66

Functions that are reachable but not covered

2

Reachable functions

4

Percentage of reachable functions covered

50.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.

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
fuzz/fuzz_targets/fuzz_roundtrip_cpp_decompress.rs	4
lz4_bin/src/main.rs	10
src/block/compress.rs	4
src/frame/decompress.rs	40
src/frame/header.rs	20
src/frame/compress.rs	1
src/block/hashtable.rs	1
src/sink.rs	6
src/fastcpy.rs	5

Fuzzer: fuzz_roundtrip_frame

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	118	51.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	112	48.6%
All colors	230	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
23	29	lz4_flex::frame::FrameEncoder::with_frame_info	call site: 00029	TrackWriteSize::write
8	14	SliceSink::extend_from_slice	call site: 00014
7	80	FrameInfo::read	call site: 00080
7	133	FrameInfo::read	call site: 00133
6	210	FrameDecoder::read_block	call site: 00210
5	0	EP	call site: 00000
5	69	FrameInfo::read	call site: 00069
5	122	FrameInfo::read	call site: 00122
4	7	SliceSink::extend_from_slice_wild	call site: 00007	short_copy
4	64	FrameInfo::read	call site: 00064
4	149	FrameDecoder::read_frame_info	call site: 00149
3	75	FrameInfo::read	call site: 00075

Runtime coverage analysis

Covered functions

130

Functions that are reachable but not covered

43

Reachable functions

74

Percentage of reachable functions covered

41.89%

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
fuzz/fuzz_targets/fuzz_roundtrip_frame.rs	20
src/sink.rs	6
src/fastcpy.rs	5
src/block/compress.rs	4
lz4_bin/src/main.rs	8
src/frame/compress.rs	4
src/frame/header.rs	24
src/frame/decompress.rs	34
src/block/hashtable.rs	1

Fuzzer: fuzz_decomp_corrupt_frame

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	60	26.7%
gold	[1:9]	2	0.89%
yellow	[10:29]	18	8.03%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	144	64.2%
All colors	224	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
17	206	SliceSink::extend_from_slice	call site: 00206	lz4_flex_frame_decompress
12	0	EP	call site: 00000	FrameDecoder::read_to_end
6	167	FrameDecoder::read_block	call site: 00167
5	199	FrameDecoder::read_to_end	call site: 00199
4	188	SliceSink::extend_from_slice_wild	call site: 00188	short_copy
2	21	FrameInfo::read	call site: 00021
2	45	FrameInfo::read	call site: 00045	TrackWriteSize::write
2	108	FrameDecoder::read_frame_info	call site: 00108
2	144	FrameDecoder::read_block	call site: 00144
1	28	FrameInfo::read	call site: 00028
1	50	FrameInfo::read	call site: 00050
1	53	FrameInfo::read	call site: 00053

Runtime coverage analysis

Covered functions

71

Functions that are reachable but not covered

6

Reachable functions

11

Percentage of reachable functions covered

45.45%

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
fuzz/fuzz_targets/fuzz_decomp_corrupt_frame.rs	7
lz4_bin/src/main.rs	10
src/block/compress.rs	4
src/frame/decompress.rs	40
src/frame/header.rs	20
src/frame/compress.rs	1
src/block/hashtable.rs	1
src/sink.rs	6
src/fastcpy.rs	5

Fuzzer: fuzz_decomp_no_output_leak

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	25	83.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	5	16.6%
All colors	30	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
12	0	EP	call site: 00000
11	15	HashTable4KU16::new	call site: 00015	short_copy
2	27	SliceSink::extend_with_fill	call site: 00027

Runtime coverage analysis

Covered functions

218

Functions that are reachable but not covered

6

Reachable functions

11

Percentage of reachable functions covered

45.45%

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
fuzz/fuzz_targets/fuzz_decomp_no_output_leak.rs	8
src/block/decompress.rs	1
lz4_bin/src/main.rs	8
src/block/compress.rs	2
src/fastcpy.rs	5
src/sink.rs	1

Optimal target analysis

Remaining optimal interesting functions

The following table shows a list of functions that are optimal targets. Optimal targets are identified by finding the functions that in combination, yield a high code coverage.

Func name	Functions filename	Arg count	Args	Function depth	hitcount	instr count	bb count	cyclomatic complexity	Reachable functions	Incoming references	total cyclomatic complexity	Unreached complexity

Implementing fuzzers that target the above functions will improve reachability such that it becomes:

Functions statically reachable by fuzzers

12 / 255

Cyclomatic complexity statically reachable by fuzzers

74 / 350

All functions overview

If you implement fuzzers for these functions, the status of all functions in the project will be:

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

This sections provides heuristics that can be used as input to a fuzz engine when running a given fuzz target. The current focus is on providing input that is usable by libFuzzer.

fuzz/fuzz_targets/fuzz_roundtrip.rs

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['HashTable4KU16::new', 'lz4_flex::decompress_size_prepended', 'super::uncompressed_size', 'lz4_flex::compress_prepend_size']

fuzz/fuzz_targets/fuzz_roundtrip_cpp_compress.rs

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['SliceSink::capacity', 'SliceSink::extend_with_fill', 'io::Result::extend_from_slice', 'SliceSink::extend_from_slice_wild']

fuzz/fuzz_targets/fuzz_decomp_corrupt_block.rs

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['lz4_flex::frame::FrameDecoder::new', 'SliceSink::capacity', 'SliceSink::extend_with_fill', 'io::Result::extend_from_slice', 'SliceSink::extend_from_slice_wild', 'lz4_flex::block::decompress_with_dict']

fuzz/fuzz_targets/fuzz_roundtrip_cpp_decompress.rs

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['HashTable4KU16::new', 'SliceSink::capacity', 'io::Result::extend_from_slice', 'SliceSink::extend_from_slice_wild']

fuzz/fuzz_targets/fuzz_roundtrip_frame.rs

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['lz4_flex::frame::FrameEncoder::with_frame_info', 'SliceSink::extend_from_slice', 'FrameInfo::read', 'FrameDecoder::read_block', 'SliceSink::extend_from_slice_wild']

fuzz/fuzz_targets/fuzz_decomp_corrupt_frame.rs

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['SliceSink::extend_from_slice', 'FrameDecoder::read_block', 'fuzz_target', 'SliceSink::extend_from_slice_wild', 'FrameInfo::read', 'FrameDecoder::read_frame_info']

fuzz/fuzz_targets/fuzz_decomp_no_output_leak.rs

Dictionary

Use this with the libFuzzer -dict=DICT.file flag

Fuzzer function priority

Use one of these functions as input to libfuzzer with flag: -focus_function name

-focus_function=['HashTable4KU16::new', 'SliceSink::extend_with_fill']

This section shows analysis of runtime coverage data.

For futher technical details on how this section is generated, please see the Glossary .

Complex functions with low coverage

Func name	Function total lines	Lines covered at runtime	percentage covered	Reached by fuzzers

New fuzzers

The below fuzzers are templates and suggestions for how to target the set of optimal functions above

This section shows which files and directories are considered in this report. The main reason for showing this is fuzz introspector may include more code in the reasoning than is desired. This section helps identify if too many files/directories are included, e.g. third party code, which may be irrelevant for the threat model. In the event too much is included, fuzz introspector supports a configuration file that can exclude data from the report. See the following link for more information on how to create a config file: link

Files in report

Source file	Reached by	Covered by
/src/lz4_flex/src/frame/header.rs	['fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame']	['fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame']
/src/lz4_flex/src/fastcpy.rs	['fuzz_roundtrip', 'fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame', 'fuzz_decomp_no_output_leak']	[]
/src/lz4_flex/src/sink.rs	['fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame', 'fuzz_decomp_no_output_leak']	['fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame', 'fuzz_decomp_no_output_leak']
/src/lz4_flex/src/frame/mod.rs	[]	[]
/src/lz4_flex/fuzz/fuzz_targets/fuzz_roundtrip_cpp_compress.rs	['fuzz_roundtrip_cpp_compress']	[]
/src/lz4_flex/fuzz/fuzz_targets/fuzz_roundtrip_frame.rs	['fuzz_roundtrip_frame']	[]
/src/lz4_flex/lz4_bin/src/main.rs	['fuzz_roundtrip', 'fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame', 'fuzz_decomp_no_output_leak']	['fuzz_roundtrip', 'fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame', 'fuzz_decomp_no_output_leak']
/src/lz4_flex/tests/tests.rs	[]	[]
/src/lz4_flex/fuzz/fuzz_targets/fuzz_roundtrip_cpp_decompress.rs	['fuzz_roundtrip_cpp_decompress']	[]
/src/lz4_flex/fuzz/fuzz_targets/fuzz_decomp_corrupt_block.rs	['fuzz_decomp_corrupt_block']	[]
/src/lz4_flex/fuzz/fuzz_targets/fuzz_decomp_no_output_leak.rs	['fuzz_roundtrip', 'fuzz_decomp_no_output_leak']	[]
/src/lz4_flex/src/block/mod.rs	['fuzz_roundtrip']	['fuzz_roundtrip']
/src/lz4_flex/src/block/compress.rs	['fuzz_roundtrip', 'fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame', 'fuzz_decomp_no_output_leak']	['fuzz_roundtrip', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_no_output_leak']
/src/lz4_flex/benches/binggan_bench.rs	[]	[]
/src/lz4_flex/src/fastcpy_unsafe.rs	[]	[]
/src/lz4_flex/src/block/decompress.rs	['fuzz_roundtrip', 'fuzz_decomp_corrupt_block', 'fuzz_decomp_no_output_leak']	[]
/src/lz4_flex/src/frame/compress.rs	['fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame']	['fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame']
/src/lz4_flex/src/frame/decompress.rs	['fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame']	['fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame']
/src/lz4_flex/miri_tests/src/main.rs	[]	[]
/src/lz4_flex/fuzz/fuzz_targets/fuzz_decomp_corrupt_frame.rs	['fuzz_decomp_corrupt_frame']	[]
/src/lz4_flex/fuzz/fuzz_targets/fuzz_roundtrip.rs	['fuzz_roundtrip']	[]
/src/lz4_flex/src/block/decompress_safe.rs	[]	[]
/src/lz4_flex/src/block/hashtable.rs	['fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame']	['fuzz_roundtrip_cpp_compress', 'fuzz_decomp_corrupt_block', 'fuzz_roundtrip_cpp_decompress', 'fuzz_roundtrip_frame', 'fuzz_decomp_corrupt_frame']
/src/lz4_flex/benchmarks/src/main.rs	[]	[]

Directories in report

Directory
/src/lz4_flex/benchmarks/src/
/src/lz4_flex/fuzz/fuzz_targets/
/src/lz4_flex/src/
/src/lz4_flex/src/frame/
/src/lz4_flex/src/block/
/src/lz4_flex/lz4_bin/src/
/src/lz4_flex/tests/
/src/lz4_flex/benches/
/src/lz4_flex/miri_tests/src/

This section shows a list of 3rd party function calls and their relative coverage information. By static analysis of the target project code, all of the 3rd party function call and their caller information, including the source file and line number that initiate the call are captured. The caller source code file and line number are shown in column 2 while column 1 is the function name of the 3rd party function call. Each occurrent of the 3rd party function call will occuply a separate row. Column 3 of each row indicate if the 3rd party call in the source file line is unreachable. Column 4 lists all fuzzers that have covered that particular system call in that specific location (source file and line)during their dynamic fuzzing.

Function in each files in report

Target sink	Callsite location	Reached by fuzzer	Covered by Fuzzers