High level conclusions

Fuzzers reach 0.063% of cyclomatic complexity.

Fuzzers reach 0.725% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

13 / 1791

Cyclomatic complexity statically reachable by fuzzers

2 / 3141

Runtime code coverage of functions

528 / 1791

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	150	79.3%
gold	[1:9]	4	2.11%
yellow	[10:29]	2	1.05%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	33	17.4%
All colors	189	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	33	Reader::read_u8	call site: 00033	SubRange::read_slice
23	128	Reader::read_sleb128	call site: 00128	Abbreviations::insert
21	9	DebugAbbrev::abbreviations	call site: 00009	ArrayVec::try_push
19	86	Reader::read_uleb128_u16	call site: 00086	Abbreviation::parse_has_children
14	71	Reader::read_uleb128	call site: 00071	Reader::read_u8
13	114	AttributeSpecification::new	call site: 00114	AttributeSpecification::parse
8	0	EP	call site: 00000	DebugAbbrev::abbreviations
7	63	Abbreviations::empty	call site: 00063	Abbreviation::parse
7	162	Abbreviations::insert	call site: 00162	ArrayVec::try_push
5	107	Reader::read_u8	call site: 00107	Abbreviation::parse_attributes
4	184	Abbreviations::insert	call site: 00184	Expression::set_target
2	158	Abbreviations::insert	call site: 00158	ArrayVec::try_push

Runtime coverage analysis

Covered functions

36

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	1
src/write/op.rs	6
src/common.rs	3
src/read/abbrev.rs	18
src/read/util.rs	14
src/leb128.rs	6
src/read/reader.rs	5
src/read/endian_reader.rs	14
src/write/abbrev.rs	1
src/read/loclists.rs	3
src/read/addr.rs	18
src/write/line.rs	3
src/endianity.rs	5
src/read/op.rs	2
src/write/unit.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	174	67.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	83	32.2%
All colors	257	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	42	Reader::read_u8	call site: 00042	SubRange::read_slice
23	136	Reader::read_sleb128	call site: 00136	Abbreviations::insert
22	9	DebugInfo::units	call site: 00009	ArrayVec::try_push
19	94	Reader::read_uleb128_u16	call site: 00094	Abbreviation::parse_has_children
13	80	Reader::read_uleb128	call site: 00080	Reader::read_u8
13	122	AttributeSpecification::new	call site: 00122	AttributeSpecification::parse
8	0	EP	call site: 00000
7	72	Abbreviations::empty	call site: 00072	Abbreviation::parse
7	170	Abbreviations::insert	call site: 00170	ArrayVec::try_push
6	192	Abbreviations::insert	call site: 00192	EntriesCursor::next_dfs
5	33	DebugInfo::units	call site: 00033	DebugAbbrev::abbreviations
5	115	Reader::read_u8	call site: 00115	Abbreviation::parse_attributes

Runtime coverage analysis

Covered functions

132

Functions that are reachable but not covered

1

Reachable functions

12

Percentage of reachable functions covered

91.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_info.rs	10
src/write/op.rs	6
src/common.rs	3
src/read/unit.rs	21
src/read/util.rs	14
src/write/endian_vec.rs	1
src/read/reader.rs	6
src/read/addr.rs	28
src/read/abbrev.rs	18
src/leb128.rs	6
src/read/endian_reader.rs	14
src/write/abbrev.rs	1
src/read/loclists.rs	3
src/write/line.rs	3
src/endianity.rs	5
src/read/op.rs	3
src/write/unit.rs	3

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	1908	89.0%
gold	[1:9]	1	0.04%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	233	10.8%
All colors	2142	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
564	1204	Reader::read_offset	call site: 01204	Evaluation::evaluate
409	368	Reader::read_null_terminated_slice	call site: 00368	Writer::write_eh_pointer_data
178	1963	IncompleteLineProgram::rows	call site: 01963	Operation::parse
175	192	Reader::read_sleb128	call site: 00192	Unit::new_with_abbreviations
156	886	Reader::read_address	call site: 00886	impl_parse_self_debug_info
82	16	Dwarf::new	call site: 00016	DebugAbbrev::abbreviations
54	1149	Operation::parse	call site: 01149	Reader::read_offset
33	1908	LineRow::apply_line_advance	call site: 01908	PubStuffParser::parse_header
25	843	Reader::read_word	call site: 00843	tests::test_line_program
23	99	Reader::read_u8	call site: 00099	SubRange::read_slice
20	171	Reader::read_u8	call site: 00171	Abbreviation::parse_attributes
19	150	Reader::read_uleb128_u16	call site: 00150	Abbreviation::parse_has_children

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	37
src/common.rs	4
src/write/line.rs	47
src/write/unit.rs	3
src/read/util.rs	14
src/write/endian_vec.rs	6
src/read/cfi.rs	1
src/read/abbrev.rs	18
src/leb128.rs	13
src/read/reader.rs	40
src/read/endian_reader.rs	22
src/write/abbrev.rs	1
src/read/loclists.rs	3
src/read/addr.rs	79
src/endianity.rs	27
src/read/op.rs	62
src/read/dwarf.rs	35
src/read/str.rs	15
src/constants.rs	4
src/read/lists.rs	1
src/read/unit.rs	28
src/write/relocate.rs	26
src/write/writer.rs	25
crates/examples/src/bin/simple_write.rs	1
src/write/section.rs	1
src/write/str.rs	12
tests/parse_self.rs	46
tests/convert_self.rs	9
src/read/value.rs	30
src/write/range.rs	29
src/read/rnglists.rs	4
src/read/line.rs	35
src/read/lookup.rs	10

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	31	83.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	16.2%
All colors	37	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
22	4	DebugAddr::headers	call site: 00004	ArrayVec::try_push
4	32	AddrHeaderIter::next	call site: 00032	ArrayVec::clone
3	28	DebugAddr::headers	call site: 00028
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

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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	5
src/read/util.rs	14
src/write/endian_vec.rs	1
src/read/reader.rs	1
src/common.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	94	68.6%
gold	[1:9]	1	0.72%
yellow	[10:29]	1	0.72%
greenyellow	[30:49]	4	2.91%
lawngreen	50+	37	27.0%
All colors	137	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
34	69	AddrHeader::parse	call site: 00069	read::skip
24	19	Reader::read_u32	call site: 00019	SubRange::read_slice
6	0	EP	call site: 00000
5	51	Endianity::read_u32	call site: 00051	Reader::read_u64
3	65	Endianity::read_u64	call site: 00065
3	113	Endianity::read_u16	call site: 00113
3	120	Reader::read_u8	call site: 00120
2	105	Reader::read_u8	call site: 00105
2	128	AddrHeader::parse	call site: 00128
2	131	AddrHeader::parse	call site: 00131	Reader::read_u8
1	7	BaseAddresses::set_eh_frame	call site: 00007
1	10	BaseAddresses::set_eh_frame_hdr	call site: 00010

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	13
src/read/reader.rs	10
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

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	747	90.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	79	9.56%
All colors	826	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	445	constants::DwEhPe::format	call site: 00445	Writer::write_udata
134	253	ArrayVec::try_push	call site: 00253	Writer::write_udata
67	733	Reader::read_u8	call site: 00733	LineRow::execute
56	388	constants::DwEhPe::application	call site: 00388	Writer::write_eh_pointer_data
42	143	Reader::read_u8	call site: 00143	LineInstructions::next_instruction
23	59	Reader::read_u32	call site: 00059	SubRange::read_slice
23	802	u64::wrapping_add_sized	call site: 00802	PubStuffParser::parse_header
19	189	Reader::read_uleb128	call site: 00189	Reader::read_address
19	229	Reader::read_null_terminated_slice	call site: 00229	Writer::write_udata
18	713	Endianity::read_u16	call site: 00713	read::skip
17	691	Reader::read_sleb128	call site: 00691	Reader::read_u8
14	28	ArrayVec::try_push	call site: 00028	ArrayVec::try_push

Runtime coverage analysis

Covered functions

165

Functions that are reachable but not covered

3

Reachable functions

17

Percentage of reachable functions covered

82.35%

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

13 / 1791

Cyclomatic complexity statically reachable by fuzzers

2 / 3141

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

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_u8', 'Reader::read_sleb128', 'DebugInfo::units', 'Reader::read_uleb128_u16', 'Reader::read_uleb128', 'AttributeSpecification::new', 'Abbreviations::empty', 'Abbreviations::insert']

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_offset', 'Reader::read_null_terminated_slice', 'IncompleteLineProgram::rows', 'Reader::read_sleb128', 'Reader::read_address', 'Dwarf::new', 'Operation::parse', 'LineRow::apply_line_advance', 'Reader::read_word', 'Reader::read_u8']

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', 'AddrHeaderIter::next', 'DebugAranges::new']

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']

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', 'Reader::read_u8', 'constants::DwEhPe::application', 'Reader::read_u32', 'u64::wrapping_add_sized', 'Reader::read_uleb128', 'Reader::read_null_terminated_slice', 'Endianity::read_u16']

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

Directories in report

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

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