High level conclusions

Fuzzers reach 66.05% code coverage.

Fuzzers reach 38.92% of cyclomatic complexity.

Fuzzers reach 29.21% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

445 / 1523

Cyclomatic complexity statically reachable by fuzzers

3197 / 8214

Runtime code coverage of functions

1006 / 1523

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

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

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

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

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

Fuzzer: fuzz_dostring

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	686	98.8%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	8	1.15%
All colors	694	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
569	66	LLVMFuzzerTestOneInput	call site: 00066	root
64	1	LLVMFuzzerTestOneInput	call site: 00001	janet_ev_init
45	648	LLVMFuzzerTestOneInput	call site: 00648	janet_clear_memory
7	636	LLVMFuzzerTestOneInput	call site: 00636	janet_parser_eof
1	644	LLVMFuzzerTestOneInput	call site: 00644	janet_parser_eof

Runtime coverage analysis

Covered functions

136

Functions that are reachable but not covered

83

Reachable functions

210

Percentage of reachable functions covered

60.48%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
./test/fuzzers/fuzz_dostring.c	1
src/core/vm.c	2
src/core/symcache.c	8
src/core/table.c	11
src/core/gc.c	11
src/core/util.c	13
src/core/wrap.c	7
src/core/math.c	3
src/core/ev.c	13
src/core/net.c	2
src/core/parse.c	27
src/core/string.c	5
src/core/strtod.c	14
src/core/inttypes.c	2
src/core/abstract.c	5
src/core/tuple.c	3
src/core/value.c	7
src/core/buffer.c	10
src/core/capi.c	7
src/core/pp.c	23
src/core/struct.c	6
src/core/array.c	2

Fuzzer: fuzz_unmarshal

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	916	99.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	9	0.97%
All colors	925	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
779	66	LLVMFuzzerTestOneInput	call site: 00066	janet_unmarshal
64	1	LLVMFuzzerTestOneInput	call site: 00001	janet_ev_init
44	880	LLVMFuzzerTestOneInput	call site: 00880	janet_clear_memory
29	846	LLVMFuzzerTestOneInput	call site: 00846	janet_env_lookup_into

Runtime coverage analysis

Covered functions

173

Functions that are reachable but not covered

60

Reachable functions

231

Percentage of reachable functions covered

74.03%

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
./test/fuzzers/fuzz_unmarshal.c	1
src/core/vm.c	4
src/core/symcache.c	8
src/core/table.c	16
src/core/gc.c	11
src/core/util.c	24
src/core/wrap.c	8
src/core/math.c	4
src/core/ev.c	14
src/core/net.c	3
src/core/corelib.c	3
src/core/string.c	6
src/core/value.c	7
src/core/io.c	3
src/core/capi.c	7
src/core/buffer.c	12
src/core/pp.c	22
src/core/struct.c	7
src/core/strtod.c	1
src/core/parse.c	3
src/core/abstract.c	5
src/core/array.c	5
src/core/tuple.c	3
src/core/fiber.c	2
src/core/os.c	1
src/core/compile.c	1
src/core/debug.c	1
src/core/marsh.c	14
src/core/peg.c	1
src/core/asm.c	1
src/core/inttypes.c	1
src/core/filewatch.c	1
src/core/ffi.c	1
src/core/vector.c	1
src/core/bytecode.c	1

Fuzzer: fuzz_compile

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	2050	99.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	15	0.72%
All colors	2065	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
1021	1010	LLVMFuzzerTestOneInput	call site: 01010	janet_compile_lint
779	66	LLVMFuzzerTestOneInput	call site: 00066	janet_unmarshal
151	846	LLVMFuzzerTestOneInput	call site: 00846	root
64	1	LLVMFuzzerTestOneInput	call site: 00001	janet_ev_init
30	2034	LLVMFuzzerTestOneInput	call site: 02034	janet_clear_memory
3	1001	LLVMFuzzerTestOneInput	call site: 01001	janet_parser_checkdead
2	1006	LLVMFuzzerTestOneInput	call site: 01006	janet_nanbox_from_bits

Runtime coverage analysis

Covered functions

458

Functions that are reachable but not covered

92

Reachable functions

413

Percentage of reachable functions covered

77.72%

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
./test/fuzzers/fuzz_compile.c	1
src/core/vm.c	19
src/core/symcache.c	8
src/core/table.c	16
src/core/gc.c	34
src/core/util.c	26
src/core/wrap.c	8
src/core/math.c	4
src/core/ev.c	17
src/core/net.c	3
src/core/corelib.c	3
src/core/string.c	6
src/core/value.c	15
src/core/io.c	5
src/core/capi.c	9
src/core/buffer.c	12
src/core/pp.c	23
src/core/struct.c	7
src/core/strtod.c	14
src/core/parse.c	29
src/core/abstract.c	5
src/core/array.c	8
src/core/tuple.c	4
src/core/fiber.c	20
src/core/os.c	1
src/core/compile.c	32
src/core/debug.c	1
src/core/marsh.c	11
src/core/peg.c	1
src/core/asm.c	1
src/core/inttypes.c	3
src/core/filewatch.c	1
src/core/ffi.c	1
src/core/vector.c	2
src/core/bytecode.c	4
src/core/regalloc.c	10
src/core/specials.c	1
src/core/cfuns.c	1
src/core/emit.c	15

Fuzzer: fuzz_dobytes

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	2494	99.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	8	0.31%
All colors	2502	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
1627	848	LLVMFuzzerTestOneInput	call site: 00848	janet_loop
779	66	LLVMFuzzerTestOneInput	call site: 00066	janet_unmarshal
64	1	LLVMFuzzerTestOneInput	call site: 00001	janet_ev_init
24	2477	LLVMFuzzerTestOneInput	call site: 02477	janet_clear_memory

Runtime coverage analysis

Covered functions

1003

Functions that are reachable but not covered

74

Reachable functions

484

Percentage of reachable functions covered

84.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
./test/fuzzers/fuzz_dobytes.c	1
src/core/vm.c	19
src/core/symcache.c	8
src/core/table.c	16
src/core/gc.c	34
src/core/util.c	28
src/core/wrap.c	8
src/core/math.c	4
src/core/ev.c	52
src/core/net.c	3
src/core/corelib.c	3
src/core/string.c	6
src/core/value.c	15
src/core/io.c	5
src/core/capi.c	11
src/core/buffer.c	12
src/core/pp.c	24
src/core/struct.c	7
src/core/strtod.c	14
src/core/parse.c	31
src/core/abstract.c	8
src/core/array.c	8
src/core/tuple.c	4
src/core/fiber.c	21
src/core/os.c	1
src/core/compile.c	32
src/core/debug.c	2
src/core/marsh.c	23
src/core/peg.c	1
src/core/asm.c	1
src/core/inttypes.c	3
src/core/filewatch.c	1
src/core/ffi.c	1
src/core/vector.c	2
src/core/bytecode.c	5
src/core/run.c	1
src/core/regalloc.c	10
src/core/specials.c	1
src/core/cfuns.c	1
src/core/emit.c	15

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
cfun_peg_replace	/src/janet/src/core/peg.c	2	['int', 'N/A']	33	0	23	3	2	264	0	2040	303
janet_asm1	/src/janet/src/core/asm.c	4	['N/A', 'N/A', 'size_t', 'int']	31	0	2310	396	129	127	3	1039	330
os_execute	/src/janet/src/core/os.c	2	['int', 'N/A']	31	0	23	3	2	187	0	981	225
janetc_fn	/src/janet/src/core/specials.c	4	['N/A', 'N/A', 'int', 'N/A']	31	0	1150	203	69	296	0	2298	195
cfun_ffi_buffer_write	/src/janet/src/core/ffi.c	2	['int', 'N/A']	27	0	129	8	3	146	0	894	149
janetc_var	/src/janet/src/core/specials.c	4	['N/A', 'N/A', 'int', 'N/A']	32	0	195	31	9	289	0	2185	99
cfun_ev_thread	/src/janet/src/core/ev.c	2	['int', 'N/A']	37	0	329	51	13	349	0	2422	98
cfun_disasm	/src/janet/src/core/asm.c	2	['int', 'N/A']	27	0	277	36	17	149	0	810	83
janetc_if	/src/janet/src/core/specials.c	4	['N/A', 'N/A', 'int', 'N/A']	31	0	739	136	54	276	0	2120	80
cfun_net_connect	/src/janet/src/core/net.c	2	['int', 'N/A']	31	0	440	66	17	168	0	852	69

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

Functions statically reachable by fuzzers

619 / 1523

Cyclomatic complexity statically reachable by fuzzers

4661 / 8214

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.

./test/fuzzers/fuzz_dostring.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']

./test/fuzzers/fuzz_unmarshal.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']

./test/fuzzers/fuzz_compile.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']

./test/fuzzers/fuzz_dobytes.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']

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
janet_length	36	14	38.88%	['fuzz_dobytes', 'fuzz_compile']
janet_put	46	22	47.82%	['fuzz_dobytes', 'fuzz_compile']
janetc_moveback	33	18	54.54%	['fuzz_dobytes', 'fuzz_compile']
janet_continue_no_check	73	40	54.79%	['fuzz_dobytes', 'fuzz_compile']
cfun_channel_choice	49	23	46.93%	['fuzz_dobytes']
janet_loop1_impl	58	26	44.82%	['fuzz_dobytes']
janet_ev_default_threaded_callback	48	18	37.5%	['fuzz_dobytes']
cfun_to_bytes	38	18	47.36%	['fuzz_dobytes']
cfun_io_fread	37	19	51.35%	['fuzz_dobytes']
cfun_net_sockaddr	37	20	54.05%	['fuzz_dobytes']
cfun_net_connect	109	44	40.36%	['fuzz_dobytes']
cfun_net_listen	61	26	42.62%	['fuzz_dobytes']
cfun_net_setsockopt	56	25	44.64%	['fuzz_dobytes']
cfun_parse_insert	38	12	31.57%	['fuzz_dobytes']
janet_putindex	45	9	20.0%	['fuzz_dobytes', 'fuzz_compile']
janet_call	52	27	51.92%	['fuzz_dobytes', 'fuzz_compile']
janet_channel_pop_with_lock	46	16	34.78%	['fuzz_dobytes']
cfun_it_s64_compare	34	11	32.35%	['fuzz_dobytes']
os_execute_impl	175	75	42.85%	['fuzz_dobytes']
os_execute_env	31	9	29.03%	['fuzz_dobytes']
os_stat_or_lstat	39	21	53.84%	['fuzz_dobytes']
peg_rule	596	192	32.21%	['fuzz_dobytes']

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/janet/src/core/math.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/parse.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/value.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/buffer.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/vector.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/filewatch.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/net.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/wrap.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/struct.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/debug.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/ffi.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/tuple.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/bytecode.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/emit.c	['fuzz_compile', 'fuzz_dobytes']	['fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/corelib.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/./test/fuzzers/fuzz_compile.c	['fuzz_compile']	[]
/src/janet/src/core/state.c	[]	[]
/src/janet/./test/fuzzers/fuzz_unmarshal.c	['fuzz_unmarshal']	[]
/src/janet/src/core/abstract.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/cfuns.c	['fuzz_compile', 'fuzz_dobytes']	['fuzz_compile', 'fuzz_dobytes']
/src/janet/./test/fuzzers/fuzz_dobytes.c	['fuzz_dobytes']	[]
/src/janet/src/core/gc.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/util.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/string.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/regalloc.c	['fuzz_compile', 'fuzz_dobytes']	['fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/run.c	['fuzz_dobytes']	['fuzz_dobytes']
/src/janet/./test/fuzzers/fuzz_dostring.c	['fuzz_dostring']	[]
/src/janet/src/core/strtod.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/specials.c	['fuzz_compile', 'fuzz_dobytes']	['fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/asm.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/pp.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/vm.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/compile.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/fiber.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/array.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/ev.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/os.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/inttypes.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/table.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/symcache.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/capi.c	['fuzz_dostring', 'fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/io.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/peg.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']
/src/janet/src/core/marsh.c	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']	['fuzz_unmarshal', 'fuzz_compile', 'fuzz_dobytes']

Directories in report

Directory
/src/janet/./test/fuzzers/
/src/janet/src/core/