High level conclusions

Fuzzer affdicfuzzer is blocked:

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

Fuzzer morphfuzzer is blocked:

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

Fuzzer persdicfuzzer is blocked:

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

Fuzzer hzfuzzer is blocked:

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

Fuzzer parserfuzzer is blocked:

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

Fuzzers reach 2.634% of cyclomatic complexity.

Fuzzers reach 5.605% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

31 / 553

Cyclomatic complexity statically reachable by fuzzers

112 / 4251

Runtime code coverage of functions

17 / 553

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

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	97	88.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	12	11.0%
All colors	109	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
53	3	LLVMFuzzerTestOneInput	call site: 00003	TextParser::check_urls
38	58	LLVMFuzzerTestOneInput	call site: 00058	TextParser::is_wordchar
5	100	LLVMFuzzerTestOneInput	call site: 00100	TextParser::check_urls
1	98	LLVMFuzzerTestOneInput	call site: 00098

Runtime coverage analysis

Covered functions

17

Functions that are reachable but not covered

41

Reachable functions

42

Percentage of reachable functions covered

2.38%

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
tools/parserfuzzer.cxx	11
parsers/textparser.cxx	20
hunspell/csutil.cxx	13

Fuzzer: hzfuzzer

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

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
17	3	LLVMFuzzerTestOneInput	call site: 00003	Hunzip::getbuf
5	22	LLVMFuzzerTestOneInput	call site: 00022	FileMgr::getline

Runtime coverage analysis

Covered functions

13

Functions that are reachable but not covered

20

Reachable functions

21

Percentage of reachable functions covered

4.76%

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
tools/hzfuzzer.cxx	6
hunspell/hunzip.cxx	11
hunspell/filemgr.cxx	3

Fuzzer: persdicfuzzer

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	5	20.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	20	80.0%
All colors	25	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
2	14	LLVMFuzzerTestOneInput	call site: 00014
1	17	LLVMFuzzerTestOneInput	call site: 00017
1	19	LLVMFuzzerTestOneInput	call site: 00019
1	21	LLVMFuzzerTestOneInput	call site: 00021

Runtime coverage analysis

Covered functions

286

Functions that are reachable but not covered

10

Reachable functions

11

Percentage of reachable functions covered

9.09%

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
tools/persdicfuzzer.cxx	11
hunspell/hunspell.cxx	5

Fuzzer: morphfuzzer

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	5	38.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	8	61.5%
All colors	13	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
2	0	EP	call site: 00000
1	7	LLVMFuzzerTestOneInput	call site: 00007
1	9	LLVMFuzzerTestOneInput	call site: 00009
1	11	LLVMFuzzerTestOneInput	call site: 00011

Runtime coverage analysis

Covered functions

324

Functions that are reachable but not covered

7

Reachable functions

8

Percentage of reachable functions covered

12.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
tools/morphfuzzer.cxx	6
hunspell/hunspell.cxx	3

Fuzzer: fuzzer

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+	3	100.%
All colors	3	100

Runtime coverage analysis

Covered functions

324

Functions that are reachable but not covered

2

Reachable functions

3

Percentage of reachable functions covered

33.33%

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
tools/fuzzer.cxx	3

Fuzzer: affdicfuzzer

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	4	30.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	9	69.2%
All colors	13	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
2	8	LLVMFuzzerTestOneInput	call site: 00008
1	0	EP	call site: 00000
1	11	LLVMFuzzerTestOneInput	call site: 00011

Runtime coverage analysis

Covered functions

368

Functions that are reachable but not covered

6

Reachable functions

7

Percentage of reachable functions covered

14.29%

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
tools/affdicfuzzer.cxx	5
hunspell/hunspell.cxx	3

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
AffixMgr::compound_check	/src/hunspell/src/hunspell/affixmgr.cxx	11	['std::string', 'short', 'short', 'short', 'short', 'hentry**', 'hentry**', 'char', 'char', 'int*', 'AffixScratch']	10	0	287	81	350	128	1	636	623
AffixMgr::compound_check_morph	/src/hunspell/src/hunspell/affixmgr.cxx	11	['std::string', 'short', 'short', 'short', 'short', 'hentry**', 'hentry**', 'char', 'std::string', 'std::string*', 'AffixScratch']	8	0	272	69	269	155	1	876	613
AffixMgr::AffixMgr	/src/hunspell/src/hunspell/affixmgr.cxx	3	['char*', 'std::vector >', 'char*']	6	0	86	7	10	194	0	550	517
SuggestMgr::ngsuggest	/src/hunspell/src/hunspell/suggestmgr.cxx	4	['std::vector ', 'char*', 'std::vector >', 'int']	4	0	321	70	123	122	0	412	353
SuggestMgr::suggest	/src/hunspell/src/hunspell/suggestmgr.cxx	4	['std::vector ', 'std::string', 'int*', 'bool']	6	0	131	56	94	120	0	371	286
HashMgr::HashMgr	/src/hunspell/src/hunspell/hashmgr.cxx	3	['char*', 'char*', 'char*']	6	0	9	3	2	168	0	432	281
HunspellImpl::spell_internal	/src/hunspell/src/hunspell/hunspell.cxx	5	['std::string', 'std::vector ', 'int*', 'std::string*', 'std::chrono::steady_clock::time_point']	7	0	236	70	135	135	0	331	238
interactive_interface	/src/hunspell/src/tools/hunspell.cxx	3	['Hunspell**', 'char*', 'int']	6	0	105	22	24	152	0	279	235
HunspellImpl::suggest_internal	/src/hunspell/src/hunspell/hunspell.cxx	7	['std::string', 'std::vector ', 'std::vector ', 'bool', 'size_t', 'int', 'std::chrono::steady_clock::time_point']	6	0	217	65	88	163	0	325	136
SfxEntry::checkword	/src/hunspell/src/hunspell/affentry.cxx	9	['std::string', 'int', 'int', 'int', 'PfxEntry*', 'FLAG', 'FLAG', 'FLAG', 'AffixScratch']	5	0	45	17	21	53	0	143	116

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

Functions statically reachable by fuzzers

279 / 553

Cyclomatic complexity statically reachable by fuzzers

3241 / 4251

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.

tools/parserfuzzer.cxx

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

tools/hzfuzzer.cxx

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

tools/persdicfuzzer.cxx

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

tools/morphfuzzer.cxx

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

tools/fuzzer.cxx

Dictionary

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

tools/affdicfuzzer.cxx

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
AffixMgr::cpdpat_check(std::__1::basic_string ,std::__1::allocator >const&,unsignedlong,hentry*,hentry*,char,TraceCtxconst*,PfxEntry*,SfxEntry*,PfxEntry*,SfxEntry*)	40	21	52.5%

New fuzzers

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

affixmgr.cxx

Target file: /src/hunspell/src/hunspell/affixmgr.cxx
Target functions: AffixMgr::compound_check, AffixMgr::compound_check_morph, AffixMgr::AffixMgr

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target AffixMgr::compound_check */
  UNKNOWN_TYPE unknown_0;
  UNKNOWN_TYPE unknown_1;
  UNKNOWN_TYPE unknown_2;
  UNKNOWN_TYPE unknown_3;
  UNKNOWN_TYPE unknown_4;
  UNKNOWN_TYPE unknown_5;
  UNKNOWN_TYPE unknown_6;
  UNKNOWN_TYPE unknown_7;
  UNKNOWN_TYPE unknown_8;
  int *new_var9 = af_get_int_p();
  UNKNOWN_TYPE unknown_10;
  AffixMgr::compound_check(unknown_0, unknown_1, unknown_2, unknown_3, unknown_4, unknown_5, unknown_6, unknown_7, unknown_8, new_var9, unknown_10);

  /* target AffixMgr::compound_check_morph */
  UNKNOWN_TYPE unknown_11;
  UNKNOWN_TYPE unknown_12;
  UNKNOWN_TYPE unknown_13;
  UNKNOWN_TYPE unknown_14;
  UNKNOWN_TYPE unknown_15;
  UNKNOWN_TYPE unknown_16;
  UNKNOWN_TYPE unknown_17;
  UNKNOWN_TYPE unknown_18;
  UNKNOWN_TYPE unknown_19;
  UNKNOWN_TYPE unknown_20;
  UNKNOWN_TYPE unknown_21;
  AffixMgr::compound_check_morph(unknown_11, unknown_12, unknown_13, unknown_14, unknown_15, unknown_16, unknown_17, unknown_18, unknown_19, unknown_20, unknown_21);

  /* target AffixMgr::AffixMgr */
  char *new_var22 = ada_safe_get_char_p();
  UNKNOWN_TYPE unknown_23;
  char *new_var24 = ada_safe_get_char_p();
  AffixMgr::AffixMgr(new_var22, unknown_23, new_var24);

  af_safe_gb_cleanup();
}

suggestmgr.cxx

Target file: /src/hunspell/src/hunspell/suggestmgr.cxx
Target functions: SuggestMgr::ngsuggest, SuggestMgr::suggest

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target SuggestMgr::ngsuggest */
  UNKNOWN_TYPE unknown_25;
  char *new_var26 = ada_safe_get_char_p();
  UNKNOWN_TYPE unknown_27;
  int new_var28 = ada_safe_get_int();
  SuggestMgr::ngsuggest(unknown_25, new_var26, unknown_27, new_var28);

  /* target SuggestMgr::suggest */
  UNKNOWN_TYPE unknown_29;
  UNKNOWN_TYPE unknown_30;
  int *new_var31 = af_get_int_p();
  UNKNOWN_TYPE unknown_32;
  SuggestMgr::suggest(unknown_29, unknown_30, new_var31, unknown_32);

  af_safe_gb_cleanup();
}

hashmgr.cxx

Target file: /src/hunspell/src/hunspell/hashmgr.cxx
Target functions: HashMgr::HashMgr

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target HashMgr::HashMgr */
  char *new_var33 = ada_safe_get_char_p();
  char *new_var34 = ada_safe_get_char_p();
  char *new_var35 = ada_safe_get_char_p();
  HashMgr::HashMgr(new_var33, new_var34, new_var35);

  af_safe_gb_cleanup();
}

hunspell.cxx

Target file: /src/hunspell/src/hunspell/hunspell.cxx
Target functions: HunspellImpl::spell_internal, HunspellImpl::suggest_internal

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target HunspellImpl::spell_internal */
  UNKNOWN_TYPE unknown_36;
  UNKNOWN_TYPE unknown_37;
  int *new_var38 = af_get_int_p();
  UNKNOWN_TYPE unknown_39;
  UNKNOWN_TYPE unknown_40;
  HunspellImpl::spell_internal(unknown_36, unknown_37, new_var38, unknown_39, unknown_40);

  /* target HunspellImpl::suggest_internal */
  UNKNOWN_TYPE unknown_44;
  UNKNOWN_TYPE unknown_45;
  UNKNOWN_TYPE unknown_46;
  UNKNOWN_TYPE unknown_47;
  UNKNOWN_TYPE unknown_48;
  int new_var49 = ada_safe_get_int();
  UNKNOWN_TYPE unknown_50;
  HunspellImpl::suggest_internal(unknown_44, unknown_45, unknown_46, unknown_47, unknown_48, new_var49, unknown_50);

  af_safe_gb_cleanup();
}

hunspell.cxx

Target file: /src/hunspell/src/tools/hunspell.cxx
Target functions: interactive_interface

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target interactive_interface */
  UNKNOWN_TYPE unknown_41;
  char *new_var42 = ada_safe_get_char_p();
  int new_var43 = ada_safe_get_int();
  interactive_interface(unknown_41, new_var42, new_var43);

  af_safe_gb_cleanup();
}

affentry.cxx

Target file: /src/hunspell/src/hunspell/affentry.cxx
Target functions: SfxEntry::checkword

#include "ada_fuzz_header.h"

int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
  af_safe_gb_init(data, size);

  /* target SfxEntry::checkword */
  UNKNOWN_TYPE unknown_51;
  int new_var52 = ada_safe_get_int();
  int new_var53 = ada_safe_get_int();
  int new_var54 = ada_safe_get_int();
  UNKNOWN_TYPE unknown_55;
  UNKNOWN_TYPE unknown_56;
  UNKNOWN_TYPE unknown_57;
  UNKNOWN_TYPE unknown_58;
  UNKNOWN_TYPE unknown_59;
  SfxEntry::checkword(unknown_51, new_var52, new_var53, new_var54, unknown_55, unknown_56, unknown_57, unknown_58, unknown_59);

  af_safe_gb_cleanup();
}

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/hunspell/src/parsers/textparser.cxx	['parserfuzzer']	['parserfuzzer']
/src/hunspell/src/hunspell/hunspelltrace.hxx	[]	[]
/src/hunspell/src/parsers/firstparser.cxx	[]	[]
/src/hunspell/src/hunspell/suggestmgr.cxx	[]	[]
/src/hunspell/src/hunspell/filemgr.cxx	['hzfuzzer']	['hzfuzzer']
/src/hunspell/src/hunspell/affixmgr.cxx	[]	[]
/src/hunspell/src/hunspell/hunversion.h	[]	[]
/src/hunspell/src/parsers/manparser.cxx	[]	[]
/src/hunspell/src/tools/affdicfuzzer.cxx	['affdicfuzzer']	['affdicfuzzer']
/src/hunspell/src/hunspell/suggestmgr.hxx	[]	[]
/src/hunspell/src/tools/hzip.cxx	[]	[]
/src/hunspell/src/tools/fuzzer.cxx	['fuzzer']	['fuzzer']
/src/hunspell/src/tools/morphfuzzer.cxx	['morphfuzzer']	['morphfuzzer']
/src/hunspell/src/hunspell/csutil.hxx	[]	[]
/src/hunspell/src/parsers/textparser.hxx	[]	[]
/src/hunspell/src/parsers/odfparser.cxx	[]	[]
/src/hunspell/src/hunspell/hunzip.cxx	['hzfuzzer']	['hzfuzzer']
/src/hunspell/src/hunspell/hunspell.hxx	[]	[]
/src/hunspell/src/tools/parserfuzzer.cxx	['parserfuzzer']	['parserfuzzer']
/src/hunspell/src/hunspell/hunspell.cxx	['persdicfuzzer', 'morphfuzzer', 'affdicfuzzer']	['persdicfuzzer', 'morphfuzzer', 'affdicfuzzer']
/src/hunspell/src/tools/persdicfuzzer.cxx	['persdicfuzzer']	['persdicfuzzer']
/src/hunspell/src/hunspell/replist.hxx	[]	[]
/src/hunspell/src/parsers/xmlparser.cxx	[]	[]
/src/hunspell/src/hunspell/hashmgr.cxx	[]	[]
/src/hunspell/src/hunspell/htypes.hxx	[]	[]
/src/hunspell/src/parsers/latexparser.cxx	[]	[]
/src/hunspell/src/hunspell/filemgr.hxx	[]	[]
/src/hunspell/src/hunspell/atypes.hxx	[]	[]
/src/hunspell/src/tools/hzfuzzer.cxx	['hzfuzzer']	['hzfuzzer']
/src/hunspell/src/hunspell/replist.cxx	[]	[]
/src/hunspell/src/hunspell/affentry.hxx	[]	[]
/src/hunspell/src/tools/munch.cxx	[]	[]
/src/hunspell/src/hunspell/phonet.cxx	[]	[]
/src/hunspell/src/hunspell/baseaffix.hxx	[]	[]
/src/hunspell/src/tools/hunspell.cxx	[]	[]
/src/hunspell/src/hunspell/hunzip.hxx	[]	[]
/src/hunspell/src/parsers/testparser.cxx	[]	[]
/src/hunspell/src/hunspell/hunspelltrace.cxx	[]	[]
/src/hunspell/src/hunspell/w_char.hxx	[]	[]
/src/hunspell/src/parsers/htmlparser.cxx	[]	[]
/src/hunspell/src/hunspell/affentry.cxx	[]	[]
/src/hunspell/src/hunspell/csutil.cxx	['parserfuzzer']	[]

Directories in report

Directory
/src/hunspell/src/hunspell/
/src/hunspell/src/parsers/
/src/hunspell/src/tools/

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