High level conclusions

Fuzzers reach 83.04% of cyclomatic complexity.

Fuzzers reach 66.0% of all functions.

Fuzzer fuzz_format_sav is blocked:

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

Fuzzer fuzz_format_sas7bdat is blocked:

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

Fuzzer fuzz_format_xport is blocked:

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

Fuzzer fuzz_format_sas7bcat is blocked:

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

Fuzzer fuzz_format_por is blocked:

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

Fuzzer fuzz_format_dta is blocked:

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

Fuzzer fuzz_format_sas_commands is blocked:

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

Fuzzer fuzz_format_spss_commands is blocked:

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

Reachability and coverage overview

Functions statically reachable by fuzzers

264 / 400

Cyclomatic complexity statically reachable by fuzzers

2502 / 3013

Runtime code coverage of functions

24 / 400

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_format_spss_commands

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

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

51

Reachable functions

51

Percentage of reachable functions covered

0.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_format_spss_commands.c	1
fuzz/fuzz_format.c	7
readstat_parser.c	14
readstat_io_unistd.c	7
test/test_buffer_io.c	5
txt/readstat_spss_commands_read.rl	1
txt/readstat_copy.c	2
txt/readstat_schema.c	2
txt/commands_util.c	2

Fuzzer: fuzz_grammar_spss_format

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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	2	100.%
All colors	2	100

Runtime coverage analysis

Covered functions

2

Functions that are reachable but not covered

0

Reachable functions

2

Percentage of reachable functions covered

100.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_grammar_spss_format.c	1
spss/readstat_spss_parse.rl	1

Fuzzer: fuzz_format_stata_dictionary

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	16	26.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	44	73.3%
All colors	60	100

Fuzz blockers

The followings are the branches where fuzzer fails to bypass.

Unique non-covered Complexity	Unique Reachable Complexities	Unique Reachable Functions	All non-covered Complexity	All Reachable Complexity	Function Name	Function Callsite	Blocked Branch
0	7	1 : View List ['readstat_parser_free']	0	7	readstat_parser_init	call site: 00005	/src/readstat/src/readstat_parser.c:9
0	0	None	0	0	unistd_io_init	call site: 00007	/src/readstat/src/readstat_io_unistd.c:125
0	0	None	0	0	unistd_io_init	call site: 00011	/src/readstat/src/readstat_io_unistd.c:128
0	0	None	0	0	unistd_io_init	call site: 00014	/src/readstat/src/readstat_io_unistd.c:131
0	0	None	0	0	unistd_io_init	call site: 00017	/src/readstat/src/readstat_io_unistd.c:134
0	0	None	0	0	unistd_io_init	call site: 00020	/src/readstat/src/readstat_io_unistd.c:137
0	0	None	0	0	rt_seek_handler	call site: 00031	/src/readstat/src/test/test_buffer_io.c:22
0	0	None	0	0	rt_seek_handler	call site: 00031	/src/readstat/src/test/test_buffer_io.c:28
0	0	None	0	0	rt_seek_handler	call site: 00031	/src/readstat/src/test/test_buffer_io.c:31

Runtime coverage analysis

Covered functions

23

Functions that are reachable but not covered

21

Reachable functions

44

Percentage of reachable functions covered

52.27%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_format_stata_dictionary.c	1
fuzz/fuzz_format.c	7
readstat_parser.c	14
readstat_io_unistd.c	7
test/test_buffer_io.c	5
txt/readstat_stata_dictionary_read.rl	1
txt/readstat_copy.c	1
txt/readstat_schema.c	1

Fuzzer: fuzz_format_sas_commands

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

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

52

Reachable functions

52

Percentage of reachable functions covered

0.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_format_sas_commands.c	1
fuzz/fuzz_format.c	7
readstat_parser.c	14
readstat_io_unistd.c	7
test/test_buffer_io.c	5
txt/readstat_sas_commands_read.rl	1
txt/readstat_copy.c	2
txt/readstat_schema.c	2
txt/commands_util.c	2

Fuzzer: fuzz_compression_sav

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	1	20.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	80.0%
All colors	5	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
1	3	sav_decompress_row	call site: 00003	byteswap8

Runtime coverage analysis

Covered functions

2

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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_compression_sav.c	1
spss/readstat_sav_compress.c	1
readstat_bits.c	2

Fuzzer: fuzz_format_dta

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

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

96

Reachable functions

96

Percentage of reachable functions covered

0.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_format_dta.c	1
fuzz/fuzz_format.c	7
readstat_parser.c	14
readstat_io_unistd.c	7
test/test_buffer_io.c	5
stata/readstat_dta_read.c	27
stata/readstat_dta.c	4
readstat_bits.c	7
readstat_malloc.c	3
readstat_convert.c	1
stata/readstat_dta_parse_timestamp.rl	1

Fuzzer: fuzz_format_por

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

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

99

Reachable functions

99

Percentage of reachable functions covered

0.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_format_por.c	1
fuzz/fuzz_format.c	7
readstat_parser.c	14
readstat_io_unistd.c	7
test/test_buffer_io.c	5
spss/readstat_por_read.c	24
spss/readstat_por.c	3
CKHashTable.c	11
readstat_convert.c	1
spss/readstat_por_parse.rl	1
readstat_malloc.c	1
spss/readstat_spss.c	6

Fuzzer: fuzz_format_sas7bcat

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

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

76

Reachable functions

76

Percentage of reachable functions covered

0.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_format_sas7bcat.c	1
fuzz/fuzz_format.c	7
readstat_parser.c	14
readstat_io_unistd.c	7
test/test_buffer_io.c	5
sas/readstat_sas7bcat_read.c	10
sas/readstat_sas.c	8
readstat_bits.c	5
readstat_convert.c	1
readstat_malloc.c	3

Fuzzer: fuzz_format_xport

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

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

85

Reachable functions

85

Percentage of reachable functions covered

0.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_format_xport.c	1
fuzz/fuzz_format.c	7
readstat_parser.c	14
readstat_io_unistd.c	7
test/test_buffer_io.c	5
sas/readstat_xport_read.c	22
readstat_convert.c	1
readstat_malloc.c	3
sas/readstat_xport.c	1
readstat_bits.c	3
sas/readstat_sas.c	1
sas/ieee.c	5

Fuzzer: fuzz_format_sas7bdat

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

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

101

Reachable functions

101

Percentage of reachable functions covered

0.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_format_sas7bdat.c	1
fuzz/fuzz_format.c	7
readstat_parser.c	14
readstat_io_unistd.c	7
test/test_buffer_io.c	5
sas/readstat_sas7bdat_read.c	31
sas/readstat_sas.c	9
readstat_bits.c	5
readstat_malloc.c	3
readstat_convert.c	1
sas/readstat_sas_rle.c	1
readstat_error.c	1

Fuzzer: fuzz_format_sav

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

Runtime coverage analysis

Covered functions

0

Functions that are reachable but not covered

133

Reachable functions

133

Percentage of reachable functions covered

0.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzz/fuzz_format_sav.c	1
fuzz/fuzz_format.c	7
readstat_parser.c	14
readstat_io_unistd.c	7
test/test_buffer_io.c	5
spss/readstat_sav_read.c	33
spss/readstat_sav.c	2
readstat_malloc.c	3
spss/readstat_spss.c	10
readstat_bits.c	4
spss/readstat_sav_parse_timestamp.rl	2
spss/readstat_sav_parse_mr_name.rl	3
readstat_convert.c	1
spss/readstat_sav_parse.rl	6
CKHashTable.c	11
spss/readstat_sav_compress.c	1
spss/readstat_zsav_read.c	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
readstat_value_is_missing	/src/readstat/src/readstat_value.c	3	['size_t', 'size_t', 'N/A']	4	0	66	11	5	15	0	59	57
sas_rle_compressed_len	/src/readstat/src/sas/readstat_sas_rle.c	2	['N/A', 'size_t']	4	0	20	3	2	7	0	44	44

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

Functions statically reachable by fuzzers

287 / 400

Cyclomatic complexity statically reachable by fuzzers

2603 / 3013

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_format_spss_commands.c

Dictionary

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

fuzz/fuzz_grammar_spss_format.c

Dictionary

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

fuzz/fuzz_format_stata_dictionary.c

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=['LLVMFuzzerTestOneInput', 'unistd_io_init']

fuzz/fuzz_format_sas_commands.c

Dictionary

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

fuzz/fuzz_compression_sav.c

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=['sav_decompress_row']

fuzz/fuzz_format_dta.c

Dictionary

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

fuzz/fuzz_format_por.c

Dictionary

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

fuzz/fuzz_format_sas7bcat.c

Dictionary

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

fuzz/fuzz_format_xport.c

Dictionary

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

fuzz/fuzz_format_sas7bdat.c

Dictionary

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

fuzz/fuzz_format_sav.c

Dictionary

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

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
readstat_parse_stata_dictionary	381	118	30.97%	['fuzz_format_stata_dictionary']

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/readstat/src/fuzz/fuzz_format_stata_dictionary.c	['fuzz_format_stata_dictionary']	['fuzz_format_stata_dictionary']
/src/readstat/src/txt/commands_util.c	['fuzz_format_spss_commands', 'fuzz_format_sas_commands']	[]
/src/readstat/src/spss/readstat_spss.c	['fuzz_format_por', 'fuzz_format_sav']	[]
/src/readstat/src/spss/readstat_sav_parse_timestamp.rl	['fuzz_format_sav']	[]
/src/readstat/src/stata/readstat_dta.c	['fuzz_format_dta']	[]
/src/readstat/src/spss/readstat_por_read.c	['fuzz_format_por']	[]
/src/readstat/src/readstat_error.c	['fuzz_format_sas7bdat']	[]
/src/readstat/src/readstat_bits.c	['fuzz_compression_sav', 'fuzz_format_dta', 'fuzz_format_sas7bcat', 'fuzz_format_xport', 'fuzz_format_sas7bdat', 'fuzz_format_sav']	[]
/src/readstat/src/txt/readstat_schema.c	['fuzz_format_spss_commands', 'fuzz_format_stata_dictionary', 'fuzz_format_sas_commands']	['fuzz_format_stata_dictionary']
/src/readstat/src/spss/readstat_sav_read.c	['fuzz_format_sav']	[]
/src/readstat/src/txt/readstat_stata_dictionary_read.rl	['fuzz_format_stata_dictionary']	['fuzz_format_stata_dictionary']
/src/readstat/src/readstat_io_unistd.c	['fuzz_format_spss_commands', 'fuzz_format_stata_dictionary', 'fuzz_format_sas_commands', 'fuzz_format_dta', 'fuzz_format_por', 'fuzz_format_sas7bcat', 'fuzz_format_xport', 'fuzz_format_sas7bdat', 'fuzz_format_sav']	['fuzz_format_stata_dictionary']
/src/readstat/src/fuzz/fuzz_format_sas_commands.c	['fuzz_format_sas_commands']	[]
/src/readstat/src/fuzz/fuzz_grammar_spss_format.c	['fuzz_grammar_spss_format']	['fuzz_grammar_spss_format']
/src/readstat/src/txt/readstat_sas_commands_read.rl	['fuzz_format_sas_commands']	[]
/src/readstat/src/readstat_malloc.c	['fuzz_format_dta', 'fuzz_format_por', 'fuzz_format_sas7bcat', 'fuzz_format_xport', 'fuzz_format_sas7bdat', 'fuzz_format_sav']	[]
/src/readstat/src/spss/readstat_por.c	['fuzz_format_por']	[]
/src/readstat/src/sas/readstat_sas.c	['fuzz_format_sas7bcat', 'fuzz_format_xport', 'fuzz_format_sas7bdat']	[]
/src/readstat/src/fuzz/fuzz_format_por.c	['fuzz_format_por']	[]
/src/readstat/src/spss/readstat_sav.c	['fuzz_format_sav']	[]
/src/readstat/src/spss/readstat_spss_parse.rl	['fuzz_grammar_spss_format']	['fuzz_grammar_spss_format']
/src/readstat/src/fuzz/fuzz_format_spss_commands.c	['fuzz_format_spss_commands']	[]
/src/readstat/src/readstat_convert.c	['fuzz_format_dta', 'fuzz_format_por', 'fuzz_format_sas7bcat', 'fuzz_format_xport', 'fuzz_format_sas7bdat', 'fuzz_format_sav']	[]
/src/readstat/src/stata/readstat_dta_read.c	['fuzz_format_dta']	[]
/src/readstat/src/fuzz/fuzz_format_dta.c	['fuzz_format_dta']	[]
/src/readstat/src/sas/ieee.c	['fuzz_format_xport']	[]
/src/readstat/src/spss/readstat_sav_parse_mr_name.rl	['fuzz_format_sav']	[]
/src/readstat/src/readstat_parser.c	['fuzz_format_spss_commands', 'fuzz_format_stata_dictionary', 'fuzz_format_sas_commands', 'fuzz_format_dta', 'fuzz_format_por', 'fuzz_format_sas7bcat', 'fuzz_format_xport', 'fuzz_format_sas7bdat', 'fuzz_format_sav']	['fuzz_format_stata_dictionary']
/src/readstat/src/fuzz/fuzz_format_sas7bdat.c	['fuzz_format_sas7bdat']	[]
/src/readstat/src/spss/readstat_sav_compress.c	['fuzz_compression_sav', 'fuzz_format_sav']	['fuzz_compression_sav']
/src/readstat/src/fuzz/fuzz_format_sav.c	['fuzz_format_sav']	[]
/src/readstat/src/fuzz/fuzz_compression_sav.c	['fuzz_compression_sav']	['fuzz_compression_sav']
/src/readstat/src/sas/readstat_sas7bdat_read.c	['fuzz_format_sas7bdat']	[]
/src/readstat/src/sas/readstat_xport.c	['fuzz_format_xport']	[]
/src/readstat/src/txt/readstat_spss_commands_read.rl	['fuzz_format_spss_commands']	[]
/src/readstat/src/CKHashTable.c	['fuzz_format_por', 'fuzz_format_sav']	[]
/src/readstat/src/spss/readstat_sav_parse.rl	['fuzz_format_sav']	[]
/src/readstat/src/fuzz/fuzz_format.c	['fuzz_format_spss_commands', 'fuzz_format_stata_dictionary', 'fuzz_format_sas_commands', 'fuzz_format_dta', 'fuzz_format_por', 'fuzz_format_sas7bcat', 'fuzz_format_xport', 'fuzz_format_sas7bdat', 'fuzz_format_sav']	['fuzz_format_stata_dictionary']
/src/readstat/src/spss/readstat_por_parse.rl	['fuzz_format_por']	[]
/src/readstat/src/sas/readstat_xport_read.c	['fuzz_format_xport']	[]
/src/readstat/src/sas/readstat_sas_rle.c	['fuzz_format_sas7bdat']	[]
/src/readstat/src/fuzz/fuzz_format_sas7bcat.c	['fuzz_format_sas7bcat']	[]
/src/readstat/src/sas/readstat_sas7bcat_read.c	['fuzz_format_sas7bcat']	[]
/src/readstat/src/readstat_variable.c	[]	[]
/src/readstat/src/stata/readstat_dta_parse_timestamp.rl	['fuzz_format_dta']	[]
/src/readstat/src/fuzz/fuzz_format_xport.c	['fuzz_format_xport']	[]
/src/readstat/src/txt/readstat_copy.c	['fuzz_format_spss_commands', 'fuzz_format_stata_dictionary', 'fuzz_format_sas_commands']	[]
/src/readstat/src/readstat_writer.c	[]	[]
/src/readstat/src/test/test_buffer_io.c	['fuzz_format_spss_commands', 'fuzz_format_stata_dictionary', 'fuzz_format_sas_commands', 'fuzz_format_dta', 'fuzz_format_por', 'fuzz_format_sas7bcat', 'fuzz_format_xport', 'fuzz_format_sas7bdat', 'fuzz_format_sav']	['fuzz_format_stata_dictionary']
/src/readstat/src/readstat_value.c	[]	[]
/src/readstat/src/spss/readstat_zsav_read.c	['fuzz_format_sav']	[]

Directories in report

Directory
/src/readstat/src/sas/
/src/readstat/src/txt/
/src/readstat/src/
/src/readstat/src/test/
/src/readstat/src/stata/
/src/readstat/src/fuzz/
/src/readstat/src/spss/