High level conclusions

Fuzzers reach 0.088% of cyclomatic complexity.

Fuzzers reach 1.261% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

24 / 1902

Cyclomatic complexity statically reachable by fuzzers

3 / 3382

Runtime code coverage of functions

600 / 1902

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

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	626	94.1%
gold	[1:9]	4	0.60%
yellow	[10:29]	2	0.30%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	33	4.96%
All colors	665	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
482	162	Abbreviations::insert	call site: 00162	Writer::write_eh_pointer_data
23	9	DebugAbbrev::abbreviations	call site: 00009	ArrayVec::try_push
23	35	Reader::read_u8	call site: 00035	SubRange::read_slice
23	128	Reader::read_sleb128	call site: 00128	Abbreviations::insert
19	88	Reader::read_uleb128_u16	call site: 00088	Abbreviation::parse_has_children
14	73	Reader::read_uleb128	call site: 00073	Reader::read_u8
10	117	AttributeSpecification::new	call site: 00117	AttributeSpecification::parse
8	0	EP	call site: 00000	DebugAbbrev::abbreviations
7	65	Abbreviations::empty	call site: 00065	Abbreviation::parse
6	109	Reader::read_u8	call site: 00109	Abbreviation::parse_attributes
5	659	Abbreviations::insert	call site: 00659	Expression::set_target
2	158	Abbreviations::insert	call site: 00158	ArrayVec::try_push

Runtime coverage analysis

Covered functions

35

Functions that are reachable but not covered

3

Reachable functions

8

Percentage of reachable functions covered

62.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/debug_abbrev.rs	6
src/write/endian_vec.rs	6
src/write/op.rs	15
src/common.rs	1
src/read/abbrev.rs	18
src/read/util.rs	14
src/write/unit.rs	1
src/leb128.rs	10
src/read/reader.rs	15
src/read/endian_reader.rs	22
src/write/abbrev.rs	1
src/read/loclists.rs	3
src/read/addr.rs	19
src/write/line.rs	3
src/endianity.rs	24
src/read/op.rs	2
src/read/lookup.rs	8
src/read/cfi.rs	1
src/write/relocate.rs	24
src/write/writer.rs	24
crates/examples/src/bin/simple_write.rs	1
src/constants.rs	1

Fuzzer: debug_names

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	112	70.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	47	29.5%
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
41	0	EP	call site: 00000	NameIndex::find_by_bucket
23	46	Reader::read_u8	call site: 00046	SubRange::read_slice
14	80	Endianity::read_u32	call site: 00080	NameIndex::name_entries
12	128	Reader::read_word	call site: 00128	read::skip
9	95	NameIndex::name_entries	call site: 00095	Reader::read_offset
5	70	Reader::read_u8	call site: 00070	Endianity::read_u32
3	42	NameIndex::find_by_bucket	call site: 00042	read::skip
1	78	Endianity::read_u32	call site: 00078
1	113	Endianity::read_u32	call site: 00113
1	116	Reader::read_word	call site: 00116
1	125	Endianity::read_u64	call site: 00125
1	149	NameIndex::compile_unit	call site: 00149	NameIndex::local_type_unit

Runtime coverage analysis

Covered functions

72

Functions that are reachable but not covered

2

Reachable functions

15

Percentage of reachable functions covered

86.67%

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/debug_names.rs	11
src/write/op.rs	14
src/common.rs	1
src/read/addr.rs	6
src/read/util.rs	14
src/write/endian_vec.rs	1
src/write/unit.rs	1
src/read/reader.rs	8
src/read/names.rs	9
src/leb128.rs	3
src/read/endian_reader.rs	14
src/write/abbrev.rs	1
src/read/loclists.rs	3
src/endianity.rs	12
src/read/cfi.rs	1

Fuzzer: debug_info

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	705	83.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	143	16.8%
All colors	848	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
423	203	Reader::read_null_terminated_slice	call site: 00203	Writer::write_eh_pointer_data
36	779	Endianity::read_u64	call site: 00779	Reader::read_offset
24	9	DebugInfo::units	call site: 00009	ArrayVec::try_push
23	46	Reader::read_u8	call site: 00046	SubRange::read_slice
23	138	Reader::read_sleb128	call site: 00138	Abbreviations::insert
19	98	Reader::read_uleb128_u16	call site: 00098	Abbreviation::parse_has_children
15	759	Endianity::read_u32	call site: 00759	Reader::read_u8
14	730	EntriesRaw::read_attributes	call site: 00730	read::skip
13	84	Reader::read_uleb128	call site: 00084	Reader::read_u8
12	627	Reader::read_null_terminated_slice	call site: 00627	read::skip
10	127	AttributeSpecification::new	call site: 00127	AttributeSpecification::parse
9	826	Endianity::read_u64	call site: 00826	Endianity::read_u32

Runtime coverage analysis

Covered functions

127

Functions that are reachable but not covered

4

Reachable functions

27

Percentage of reachable functions covered

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

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/debug_info.rs	8
src/write/op.rs	18
src/common.rs	1
src/read/unit.rs	64
src/read/util.rs	15
src/write/endian_vec.rs	6
src/write/unit.rs	1
src/read/reader.rs	15
src/read/addr.rs	24
src/read/abbrev.rs	20
src/leb128.rs	10
src/read/endian_reader.rs	22
src/write/abbrev.rs	1
src/read/loclists.rs	3
src/write/line.rs	3
src/endianity.rs	27
src/read/op.rs	2
src/read/lookup.rs	8
src/read/cfi.rs	1
src/write/relocate.rs	24
src/write/writer.rs	24
crates/examples/src/bin/simple_write.rs	1
src/constants.rs	1

Fuzzer: eh_frame_hdr

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	96	68.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	3	2.12%
lawngreen	50+	42	29.7%
All colors	141	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
36	70	AddrHeader::parse	call site: 00070	read::skip
24	19	Reader::read_u32	call site: 00019	SubRange::read_slice
5	51	Endianity::read_u32	call site: 00051	Reader::read_u64
4	65	Endianity::read_u64	call site: 00065
3	116	Endianity::read_u16	call site: 00116
3	123	Reader::read_u8	call site: 00123
2	4	EhFrameHdr::new	call site: 00004
2	108	Reader::read_u8	call site: 00108
2	129	Reader::read_u8	call site: 00129
2	135	AddrHeader::parse	call site: 00135	Reader::read_u8
2	138	AddrHeader::parse	call site: 00138
1	0	EP	call site: 00000

Runtime coverage analysis

Covered functions

58

Functions that are reachable but not covered

2

Reachable functions

10

Percentage of reachable functions covered

80.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/eh_frame_hdr.rs	8
src/write/op.rs	3
src/common.rs	1
src/read/cfi.rs	1
src/read/addr.rs	14
src/read/reader.rs	11
src/endianity.rs	14
src/read/endian_reader.rs	18
src/leb128.rs	3
src/write/abbrev.rs	1
src/write/endian_vec.rs	1
src/read/loclists.rs	3
src/read/util.rs	14
src/write/unit.rs	1

Fuzzer: eh_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	769	90.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	85	9.95%
All colors	854	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
202	463	constants::DwEhPe::format	call site: 00463	Writer::write_udata
134	257	ArrayVec::try_push	call site: 00257	Writer::write_udata
70	392	constants::DwEhPe::application	call site: 00392	Writer::write_eh_pointer_data
67	751	Reader::read_u8	call site: 00751	LineRow::execute
42	147	Reader::read_u8	call site: 00147	LineInstructions::next_instruction
23	62	Reader::read_u32	call site: 00062	SubRange::read_slice
19	193	Reader::read_uleb128	call site: 00193	Reader::read_address
19	233	Reader::read_null_terminated_slice	call site: 00233	Writer::write_udata
18	731	Endianity::read_u16	call site: 00731	read::skip
17	709	Reader::read_sleb128	call site: 00709	Reader::read_u8
16	837	Reader::read_null_terminated_slice	call site: 00837	PubStuffParser::parse_header
14	30	ArrayVec::try_push	call site: 00030	ArrayVec::try_push

Runtime coverage analysis

Covered functions

168

Functions that are reachable but not covered

4

Reachable functions

18

Percentage of reachable functions covered

77.78%

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/eh_frame.rs	14
src/write/op.rs	14
src/common.rs	1
src/read/op.rs	7
src/read/util.rs	14
src/write/endian_vec.rs	6
src/write/unit.rs	1
src/read/cfi.rs	2
src/read/addr.rs	45
src/read/reader.rs	26
src/endianity.rs	23
src/read/endian_reader.rs	22
src/leb128.rs	10
src/write/abbrev.rs	1
src/read/loclists.rs	3
src/read/line.rs	21
src/read/lookup.rs	17
src/write/line.rs	6
src/write/relocate.rs	24
src/write/writer.rs	24
crates/examples/src/bin/simple_write.rs	1
src/constants.rs	1

Fuzzer: debug_aranges

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	36	87.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	5	12.1%
All colors	41	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
24	4	DebugAddr::headers	call site: 00004	ArrayVec::try_push
10	30	DebugAddr::headers	call site: 00030	ArrayVec::clone
1	0	EP	call site: 00000
1	2	DebugAranges::new	call site: 00002

Runtime coverage analysis

Covered functions

50

Functions that are reachable but not covered

2

Reachable functions

8

Percentage of reachable functions covered

75.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/debug_aranges.rs	6
src/write/op.rs	2
src/read/addr.rs	6
src/read/util.rs	14
src/write/endian_vec.rs	1
src/write/unit.rs	1
src/read/reader.rs	1
src/common.rs	1

Fuzzer: debug_line

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	1128	85.7%
gold	[1:9]	2	0.15%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	185	14.0%
All colors	1315	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
250	287	Reader::read_u8	call site: 00287	read::unsigned
196	89	Reader::read_null_terminated_slice	call site: 00089	Writer::write_eh_pointer_data
126	1006	Reader::read_address	call site: 01006	Expression::write
95	674	Reader::read_sleb128	call site: 00674	EntriesRaw::read_entry
51	887	Endianity::read_u64	call site: 00887	Dwarf::attr_string
47	572	Reader::read_null_terminated_slice	call site: 00572	DebugAbbrev::abbreviations
36	840	Endianity::read_u64	call site: 00840	Reader::read_offset
35	770	Reader::read_uleb128	call site: 00770	EntriesRaw::read_attributes
33	1268	LineRow::apply_line_advance	call site: 01268	PubStuffParser::parse_header
25	963	Reader::read_offset	call site: 00963	tests::test_line_program
24	38	Reader::read_u32	call site: 00038	SubRange::read_slice
24	538	Reader::read_null_terminated_slice	call site: 00538	read::skip

Runtime coverage analysis

Covered functions

90

Functions that are reachable but not covered

2

Reachable functions

8

Percentage of reachable functions covered

75.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/debug_line.rs	6
src/write/op.rs	33
src/common.rs	2
src/write/line.rs	47
src/read/lookup.rs	17
src/read/reader.rs	27
src/endianity.rs	28
src/read/endian_reader.rs	22
src/leb128.rs	10
src/write/abbrev.rs	1
src/write/endian_vec.rs	6
src/read/loclists.rs	3
src/read/cfi.rs	1
src/write/relocate.rs	26
src/write/writer.rs	24
src/read/op.rs	3
src/read/util.rs	15
src/write/unit.rs	1
crates/examples/src/bin/simple_write.rs	1
src/constants.rs	4
src/read/abbrev.rs	18
src/read/addr.rs	56
src/read/dwarf.rs	32
src/read/str.rs	15
src/read/lists.rs	1
src/read/unit.rs	57
src/read/names.rs	2
src/write/section.rs	1
benches/bench.rs	5
src/read/line.rs	21

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

24 / 1902

Cyclomatic complexity statically reachable by fuzzers

3 / 3382

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/debug_abbrev.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=['Abbreviations::insert', 'DebugAbbrev::abbreviations', 'Reader::read_u8', 'Reader::read_sleb128', 'Reader::read_uleb128_u16', 'Reader::read_uleb128', 'AttributeSpecification::new', 'Abbreviations::empty']

fuzz/fuzz_targets/debug_names.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=['Reader::read_u8', 'Endianity::read_u32', 'Reader::read_word', 'NameIndex::name_entries', 'NameIndex::find_by_bucket']

fuzz/fuzz_targets/debug_info.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=['Reader::read_null_terminated_slice', 'Endianity::read_u64', 'DebugInfo::units', 'Reader::read_u8', 'Reader::read_sleb128', 'Reader::read_uleb128_u16', 'Endianity::read_u32', 'EntriesRaw::read_attributes', 'Reader::read_uleb128']

fuzz/fuzz_targets/eh_frame_hdr.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=['AddrHeader::parse', 'Reader::read_u32', 'Endianity::read_u32', 'Endianity::read_u64', 'Endianity::read_u16', 'Reader::read_u8', 'EhFrameHdr::new']

fuzz/fuzz_targets/eh_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=['constants::DwEhPe::format', 'ArrayVec::try_push', 'constants::DwEhPe::application', 'Reader::read_u8', 'Reader::read_u32', 'Reader::read_uleb128', 'Reader::read_null_terminated_slice', 'Endianity::read_u16', 'Reader::read_sleb128']

fuzz/fuzz_targets/debug_aranges.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=['DebugAddr::headers', 'DebugAranges::new']

fuzz/fuzz_targets/debug_line.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=['Reader::read_u8', 'Reader::read_null_terminated_slice', 'Reader::read_address', 'Reader::read_sleb128', 'Endianity::read_u64', 'Reader::read_uleb128', 'LineRow::apply_line_advance', 'Reader::read_offset']

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/gimli/src/read/pubtypes.rs	[]	[]
/src/gimli/src/read/dwarf.rs	['debug_line']	['debug_line']
/src/gimli/fuzz/fuzz_targets/eh_frame.rs	['eh_frame']	[]
/src/gimli/src/read/line.rs	['eh_frame', 'debug_line']	['eh_frame', 'debug_line']
/src/gimli/benches/bench.rs	['debug_line']	[]
/src/gimli/src/arch.rs	[]	[]
/src/gimli/src/read/unit.rs	['debug_info', 'debug_line']	['debug_info', 'debug_line']
/src/gimli/src/read/loclists.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_line']	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_line']
/src/gimli/src/write/unit.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']
/src/gimli/src/write/range.rs	[]	[]
/src/gimli/src/write/str.rs	[]	[]
/src/gimli/src/write/writer.rs	['debug_abbrev', 'debug_info', 'eh_frame', 'debug_line']	[]
/src/gimli/crates/examples/src/bin/simple_convert.rs	[]	[]
/src/gimli/src/read/endian_slice.rs	[]	[]
/src/gimli/fuzz/fuzz_targets/debug_info.rs	['debug_info']	[]
/src/gimli/tests/convert_self.rs	[]	[]
/src/gimli/src/read/relocate.rs	[]	[]
/src/gimli/src/leb128.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_line']	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_line']
/src/gimli/crates/examples/src/bin/dwarf-validate.rs	[]	[]
/src/gimli/src/read/reader.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']
/src/gimli/src/endianity.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_line']	['debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_line']
/src/gimli/src/write/op.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']
/src/gimli/src/write/relocate.rs	['debug_abbrev', 'debug_info', 'eh_frame', 'debug_line']	['debug_info', 'eh_frame', 'debug_line']
/src/gimli/crates/examples/src/bin/dwarfdump.rs	[]	[]
/src/gimli/src/write/abbrev.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_line']	[]
/src/gimli/src/read/addr.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']
/src/gimli/src/write/loc.rs	[]	[]
/src/gimli/src/read/str.rs	['debug_line']	['debug_line']
/src/gimli/src/write/cfi.rs	[]	[]
/src/gimli/src/constants.rs	['debug_abbrev', 'debug_info', 'eh_frame', 'debug_line']	['debug_info', 'eh_frame']
/src/gimli/src/case_fold.rs	[]	[]
/src/gimli/tests/parse_self.rs	[]	[]
/src/gimli/src/write/mod.rs	[]	[]
/src/gimli/src/read/aranges.rs	[]	[]
/src/gimli/src/read/value.rs	[]	[]
/src/gimli/src/common.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']
/src/gimli/fuzz/fuzz_targets/debug_abbrev.rs	['debug_abbrev']	[]
/src/gimli/src/write/endian_vec.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']
/src/gimli/src/read/mod.rs	[]	[]
/src/gimli/src/read/index.rs	[]	[]
/src/gimli/crates/examples/src/bin/simple.rs	[]	[]
/src/gimli/src/read/rnglists.rs	[]	[]
/src/gimli/src/read/op.rs	['debug_abbrev', 'debug_info', 'eh_frame', 'debug_line']	['debug_abbrev', 'debug_info', 'eh_frame', 'debug_line']
/src/gimli/src/read/abbrev.rs	['debug_abbrev', 'debug_info', 'debug_line']	['debug_abbrev', 'debug_info', 'debug_line']
/src/gimli/src/test_util.rs	[]	[]
/src/gimli/src/read/lists.rs	['debug_line']	['debug_line']
/src/gimli/src/read/pubnames.rs	[]	[]
/src/gimli/src/write/dwarf.rs	[]	[]
/src/gimli/src/read/macros.rs	[]	[]
/src/gimli/fuzz/fuzz_targets/debug_names.rs	['debug_names']	[]
/src/gimli/fuzz/fuzz_targets/debug_aranges.rs	['debug_aranges']	[]
/src/gimli/src/read/lookup.rs	['debug_abbrev', 'debug_info', 'eh_frame', 'debug_line']	['debug_abbrev', 'debug_info', 'eh_frame', 'debug_line']
/src/gimli/crates/examples/src/bin/convert.rs	[]	[]
/src/gimli/src/read/names.rs	['debug_names', 'debug_line']	['debug_names', 'debug_line']
/src/gimli/fuzz/fuzz_targets/debug_line.rs	['debug_line']	[]
/src/gimli/src/write/section.rs	['debug_line']	['debug_line']
/src/gimli/crates/examples/src/bin/simple_write.rs	['debug_abbrev', 'debug_info', 'eh_frame', 'debug_line']	['debug_abbrev', 'debug_info', 'eh_frame', 'debug_line']
/src/gimli/src/read/util.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_aranges', 'debug_line']
/src/gimli/src/write/line.rs	['debug_abbrev', 'debug_info', 'eh_frame', 'debug_line']	['debug_abbrev', 'debug_info', 'eh_frame', 'debug_line']
/src/gimli/src/read/cfi.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_line']	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_line']
/src/gimli/src/read/endian_reader.rs	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_line']	['debug_abbrev', 'debug_names', 'debug_info', 'eh_frame_hdr', 'eh_frame', 'debug_line']
/src/gimli/fuzz/fuzz_targets/eh_frame_hdr.rs	['eh_frame_hdr']	[]

Directories in report

Directory
/src/gimli/src/
/src/gimli/src/read/
/src/gimli/src/write/
/src/gimli/benches/
/src/gimli/tests/
/src/gimli/crates/examples/src/bin/
/src/gimli/fuzz/fuzz_targets/

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