High level conclusions

Fuzzers reach 84.88% code coverage.

Fuzzers reach 81.17% of cyclomatic complexity.

Fuzzers reach 67.17% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

311 / 463

Cyclomatic complexity statically reachable by fuzzers

2406 / 2964

Runtime code coverage of functions

393 / 463

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: ppmdenc_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	1	1.04%
gold	[1:9]	1	1.04%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	94	97.9%
All colors	96	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	30	AllocUnitsRare	call site: 00030	InsertNode

Runtime coverage analysis

Covered functions

53

Functions that are reachable but not covered

1

Reachable functions

49

Percentage of reachable functions covered

97.96%

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
ppmdenc_fuzzer.cc	1
sdk/C/Ppmd7.c	23
./common-buffer.h	7
sdk/C/Ppmd7Enc.c	7
sdk/C/Ppmd7Dec.c	3

Fuzzer: filters_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	1	2.63%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	37	97.3%
All colors	38	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	9	AesFuzzer::AesFuzzer(unsigned char const*, unsigned long)	call site: 00009

Runtime coverage analysis

Covered functions

62

Functions that are reachable but not covered

2

Reachable functions

39

Percentage of reachable functions covered

94.87%

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
filters_fuzzer.cc	16
sdk/C/Aes.c	1
sdk/C/CpuArch.c	5
sdk/C/7zCrc.c	1
sdk/C/XzCrc64.c	1

Fuzzer: lzmadec_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	2	9.09%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	20	90.9%
All colors	22	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	6	LzmaDec_Allocate	call site: 00006	LzmaDec_FreeProbs
1	17	LzmaDec_DecodeToDic	call site: 00017	LzmaDec_DecodeReal2

Runtime coverage analysis

Covered functions

19

Functions that are reachable but not covered

0

Reachable functions

15

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.

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
lzmadec_fuzzer.cc	1
sdk/C/LzmaDec.c	14

Fuzzer: lzma2dec_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	2	6.66%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	28	93.3%
All colors	30	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	8	LzmaDec_Allocate	call site: 00008	LzmaDec_FreeProbs
1	25	LzmaDec_DecodeToDic	call site: 00025	LzmaDec_DecodeReal2

Runtime coverage analysis

Covered functions

26

Functions that are reachable but not covered

0

Reachable functions

23

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.

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
lzma2dec_fuzzer.cc	2
sdk/C/Lzma2Dec.c	7
sdk/C/LzmaDec.c	13

Fuzzer: xzdec_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]	1	1.23%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	80	98.7%
All colors	81	100

Runtime coverage analysis

Covered functions

106

Functions that are reachable but not covered

1

Reachable functions

62

Percentage of reachable functions covered

98.39%

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
xzdec_fuzzer.cc	1
sdk/C/7zCrc.c	3
sdk/C/CpuArch.c	4
sdk/C/XzCrc64.c	2
sdk/C/XzDec.c	31
./common-buffer.h	5
sdk/C/Alloc.c	1
sdk/C/Xz.c	5
sdk/C/Sha256.c	4

Fuzzer: lzmaenc_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	7	4.51%
gold	[1:9]	2	1.29%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	146	94.1%
All colors	155	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	140	LzmaDec_DecodeReal2	call site: 00140	LzmaDec_DecodeReal2
1	27	LzmaEnc_Alloc	call site: 00027	LzmaEnc_FreeLits
1	29	LzmaEnc_Alloc	call site: 00029	MatchFinder_Free
1	36	MatchFinder_Create	call site: 00036	MatchFinder_Free
1	52	LzmaEnc_CodeOneBlock	call site: 00052	Flush
1	118	LzmaEnc_CodeOneBlock	call site: 00118	CheckErrors

Runtime coverage analysis

Covered functions

108

Functions that are reachable but not covered

2

Reachable functions

86

Percentage of reachable functions covered

97.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
lzmaenc_fuzzer.cc	1
sdk/C/LzmaEnc.c	48
sdk/C/LzFind.c	9
./common-buffer.h	7
sdk/C/LzmaDec.c	12

Fuzzer: 7z_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	43	16.6%
gold	[1:9]	13	5.01%
yellow	[10:29]	7	2.70%
greenyellow	[30:49]	1	0.38%
lawngreen	50+	195	75.2%
All colors	259	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
9	147	CreateSuccessors	call site: 00147	AllocUnitsRare
7	208	SzReadHeader2	call site: 00208	SzReadAndDecodePackedStreams
5	186	SzFolder_Decode2	call site: 00186	Delta_Decode
3	139	ShrinkUnits	call site: 00139	SplitBlock
2	63	ReadSubStreamsInfo	call site: 00063	SkipData
2	165	AllocUnits	call site: 00165	AllocUnitsRare
2	231	ReadTime	call site: 00231	ReadTime
1	37	ReadPackInfo	call site: 00037	CountDefinedBits
1	68	ReadSubStreamsInfo	call site: 00068	SkipData
1	108	LzmaDec_DecodeToDic	call site: 00108	LzmaDec_DecodeReal2
1	157	CreateSuccessors	call site: 00157	RestartModel
1	159	UpdateModel	call site: 00159	RestartModel

Runtime coverage analysis

Covered functions

124

Functions that are reachable but not covered

6

Reachable functions

114

Percentage of reachable functions covered

94.74%

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
7z_fuzzer.cc	1
sdk/C/7zCrc.c	2
sdk/C/CpuArch.c	4
sdk/C/7zArcIn.c	34
./common-buffer.h	2
sdk/C/7zStream.c	3
sdk/C/7zBuf.c	3
sdk/C/7zDec.c	9
sdk/C/LzmaDec.c	11
sdk/C/Lzma2Dec.c	6
sdk/C/Ppmd7.c	23
sdk/C/Ppmd7Dec.c	3
sdk/C/Bcj2.c	2
sdk/C/Delta.c	3
sdk/C/Bra86.c	1
sdk/C/Bra.c	4
sdk/C/BraIA64.c	1

Fuzzer: lzma2enc_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	20	10.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	172	89.5%
All colors	192	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
7	77	LzmaEnc_CodeOneBlock	call site: 00077	Flush
4	65	LzmaEnc_InitPrices	call site: 00065	LzmaEnc_MemPrepare
3	92	LenEnc_Encode	call site: 00092	RangeEnc_ShiftLow
2	176	LzmaDec_DecodeReal2	call site: 00176	LzmaDec_DecodeReal2
1	43	LzmaEnc_Alloc	call site: 00043	LzmaEnc_FreeLits
1	45	LzmaEnc_Alloc	call site: 00045	MatchFinder_Free
1	52	MatchFinder_Create	call site: 00052	MatchFinder_Free
1	143	LzmaEnc_CodeOneBlock	call site: 00143	CheckErrors

Runtime coverage analysis

Covered functions

132

Functions that are reachable but not covered

5

Reachable functions

111

Percentage of reachable functions covered

95.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
lzma2enc_fuzzer.cc	1
sdk/C/Lzma2Enc.c	14
sdk/C/LzmaEnc.c	53
./common-buffer.h	7
sdk/C/LzFind.c	9
sdk/C/Lzma2Dec.c	7
sdk/C/LzmaDec.c	11

Fuzzer: xzenc_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	33	10.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	275	89.2%
All colors	308	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
7	126	LzmaEnc_CodeOneBlock	call site: 00126	Flush
4	114	LzmaEnc_InitPrices	call site: 00114	LzmaEnc_MemPrepare
3	23	Lzma2EncProps_Normalize	call site: 00023	XzEncProps_Normalize_Fixed
3	141	LenEnc_Encode	call site: 00141	RangeEnc_ShiftLow
3	152	LzmaEnc_CodeOneBlock	call site: 00152	GetOptimumFast
3	206	Xz_CompressBlock	call site: 00206	XzBlock_WriteHeader
2	269	MixCoder_SetFromMethod	call site: 00269	MixCoder_ResetFromMethod
1	40	Xz_WriteHeader	call site: 00040	XzEnc_FreeOutBufs
1	64	SeqInFilter_Init	call site: 00064	XzCheck_Update
1	92	LzmaEnc_Alloc	call site: 00092	LzmaEnc_FreeLits
1	94	LzmaEnc_Alloc	call site: 00094	MatchFinder_Free
1	101	MatchFinder_Create	call site: 00101	MatchFinder_Free

Runtime coverage analysis

Covered functions

229

Functions that are reachable but not covered

10

Reachable functions

174

Percentage of reachable functions covered

94.25%

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
xzenc_fuzzer.cc	1
sdk/C/7zCrc.c	3
sdk/C/CpuArch.c	4
sdk/C/XzCrc64.c	2
sdk/C/XzEnc.c	32
sdk/C/Lzma2Enc.c	13
sdk/C/LzmaEnc.c	53
./common-buffer.h	7
sdk/C/Xz.c	5
sdk/C/Sha256.c	4
sdk/C/XzDec.c	31
sdk/C/LzFind.c	9
sdk/C/Alloc.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
Bt4_MatchFinder_GetMatches	/src/lzma-fuzz/sdk/C/LzFind.c	2	['N/A', 'N/A']	4	0	459	39	15	13	0	80	80

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

Functions statically reachable by fuzzers

325 / 463

Cyclomatic complexity statically reachable by fuzzers

2486 / 2964

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.

ppmdenc_fuzzer.cc

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

filters_fuzzer.cc

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=['AesFuzzer::AesFuzzer(unsigned char const*, unsigned long)']

lzmadec_fuzzer.cc

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=['LzmaDec_Allocate', 'LzmaDec_DecodeToDic']

lzma2dec_fuzzer.cc

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=['LzmaDec_Allocate', 'LzmaDec_DecodeToDic']

xzdec_fuzzer.cc

Dictionary

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

lzmaenc_fuzzer.cc

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=['LzmaDec_DecodeReal2', 'LzmaEnc_Alloc', 'MatchFinder_Create', 'LzmaEnc_CodeOneBlock']

7z_fuzzer.cc

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=['CreateSuccessors', 'SzReadHeader2', 'SzFolder_Decode2', 'ShrinkUnits', 'ReadSubStreamsInfo', 'AllocUnits', 'ReadTime', 'ReadPackInfo', 'LzmaDec_DecodeToDic']

lzma2enc_fuzzer.cc

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=['LzmaEnc_CodeOneBlock', 'LzmaEnc_InitPrices', 'LenEnc_Encode', 'LzmaDec_DecodeReal2', 'LzmaEnc_Alloc', 'MatchFinder_Create']

xzenc_fuzzer.cc

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=['LzmaEnc_CodeOneBlock', 'LzmaEnc_InitPrices', 'Lzma2EncProps_Normalize', 'LenEnc_Encode', 'Xz_CompressBlock', 'MixCoder_SetFromMethod', 'Xz_WriteHeader', 'SeqInFilter_Init', 'LzmaEnc_Alloc']

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
Lzma2EncProps_Normalize	90	43	47.77%	['xzenc_fuzzer', 'lzma2enc_fuzzer']
XzProps_Normalize	59	28	47.45%	['xzenc_fuzzer']

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/lzma-fuzz/sdk/C/7zAlloc.c	[]	[]
/src/lzma-fuzz/sdk/C/XzCrc64Opt.c	[]	[]
/src/lzma-fuzz/sdk/C/Aes.c	['filters_fuzzer']	['filters_fuzzer']
/src/lzma-fuzz/xzdec_fuzzer.cc	['xzdec_fuzzer']	['xzdec_fuzzer']
/src/lzma-fuzz/sdk/C/Sha256.c	['xzdec_fuzzer', 'xzenc_fuzzer']	['xzdec_fuzzer', 'xzenc_fuzzer']
/src/lzma-fuzz/sdk/C/AesOpt.c	[]	[]
/src/lzma-fuzz/./common-buffer.h	['ppmdenc_fuzzer', 'xzdec_fuzzer', 'lzmaenc_fuzzer', '7z_fuzzer', 'lzma2enc_fuzzer', 'xzenc_fuzzer']	[]
/src/lzma-fuzz/sdk/C/7zStream.c	['7z_fuzzer']	['7z_fuzzer']
/src/lzma-fuzz/sdk/C/Bra86.c	['7z_fuzzer']	['7z_fuzzer']
/src/lzma-fuzz/sdk/C/Lzma2Dec.c	['lzma2dec_fuzzer', '7z_fuzzer', 'lzma2enc_fuzzer']	['lzma2dec_fuzzer', '7z_fuzzer', 'lzma2enc_fuzzer']
/src/lzma-fuzz/xzenc_fuzzer.cc	['xzenc_fuzzer']	['xzenc_fuzzer']
/src/lzma-fuzz/sdk/C/Xz.c	['xzdec_fuzzer', 'xzenc_fuzzer']	['xzdec_fuzzer', 'xzenc_fuzzer']
/src/lzma-fuzz/sdk/C/LzmaEnc.c	['lzmaenc_fuzzer', 'lzma2enc_fuzzer', 'xzenc_fuzzer']	['lzmaenc_fuzzer', 'lzma2enc_fuzzer', 'xzenc_fuzzer']
/src/lzma-fuzz/lzmaenc_fuzzer.cc	['lzmaenc_fuzzer']	['lzmaenc_fuzzer']
/src/lzma-fuzz/sdk/C/BraIA64.c	['7z_fuzzer']	['7z_fuzzer']
/src/lzma-fuzz/ppmdenc_fuzzer.cc	['ppmdenc_fuzzer']	['ppmdenc_fuzzer']
/src/lzma-fuzz/sdk/C/Ppmd7Dec.c	['ppmdenc_fuzzer', '7z_fuzzer']	['ppmdenc_fuzzer', '7z_fuzzer']
/src/lzma-fuzz/sdk/C/7zCrcOpt.c	[]	[]
/src/lzma-fuzz/sdk/C/Alloc.c	['xzdec_fuzzer', 'xzenc_fuzzer']	['xzdec_fuzzer', 'xzenc_fuzzer']
/src/lzma-fuzz/sdk/C/Bra.c	['7z_fuzzer']	['7z_fuzzer']
/src/lzma-fuzz/./common-alloc.h	[]	[]
/src/lzma-fuzz/sdk/C/7zCrc.c	['filters_fuzzer', 'xzdec_fuzzer', '7z_fuzzer', 'xzenc_fuzzer']	['filters_fuzzer', 'xzdec_fuzzer', '7z_fuzzer', 'xzenc_fuzzer']
/src/lzma-fuzz/sdk/C/Ppmd7.c	['ppmdenc_fuzzer', '7z_fuzzer']	['ppmdenc_fuzzer', '7z_fuzzer']
/src/lzma-fuzz/7z_fuzzer.cc	['7z_fuzzer']	['7z_fuzzer']
/src/lzma-fuzz/sdk/C/XzDec.c	['xzdec_fuzzer', 'xzenc_fuzzer']	['xzdec_fuzzer', 'xzenc_fuzzer']
/src/lzma-fuzz/sdk/C/LzFind.c	['lzmaenc_fuzzer', 'lzma2enc_fuzzer', 'xzenc_fuzzer']	['lzmaenc_fuzzer', 'lzma2enc_fuzzer', 'xzenc_fuzzer']
/src/lzma-fuzz/sdk/C/Ppmd7Enc.c	['ppmdenc_fuzzer']	['ppmdenc_fuzzer']
/src/lzma-fuzz/sdk/C/Delta.c	['7z_fuzzer']	[]
/src/lzma-fuzz/lzma2enc_fuzzer.cc	['lzma2enc_fuzzer']	['lzma2enc_fuzzer']
/src/lzma-fuzz/sdk/C/7zBuf.c	['7z_fuzzer']	['7z_fuzzer']
/src/lzma-fuzz/sdk/C/7zDec.c	['7z_fuzzer']	['7z_fuzzer']
/src/lzma-fuzz/sdk/C/XzEnc.c	['xzenc_fuzzer']	['xzenc_fuzzer']
/src/lzma-fuzz/sdk/C/Lzma2Enc.c	['lzma2enc_fuzzer', 'xzenc_fuzzer']	['lzma2enc_fuzzer', 'xzenc_fuzzer']
/src/lzma-fuzz/sdk/C/XzCrc64.c	['filters_fuzzer', 'xzdec_fuzzer', 'xzenc_fuzzer']	['filters_fuzzer', 'xzdec_fuzzer', 'xzenc_fuzzer']
/src/lzma-fuzz/lzmadec_fuzzer.cc	['lzmadec_fuzzer']	['lzmadec_fuzzer']
/src/lzma-fuzz/lzma2dec_fuzzer.cc	['lzma2dec_fuzzer']	['lzma2dec_fuzzer']
/src/lzma-fuzz/filters_fuzzer.cc	['filters_fuzzer']	['filters_fuzzer']
/src/lzma-fuzz/sdk/C/LzmaDec.c	['lzmadec_fuzzer', 'lzma2dec_fuzzer', 'lzmaenc_fuzzer', '7z_fuzzer', 'lzma2enc_fuzzer']	['lzmadec_fuzzer', 'lzma2dec_fuzzer', 'lzmaenc_fuzzer', '7z_fuzzer', 'lzma2enc_fuzzer']
/src/lzma-fuzz/sdk/C/7zArcIn.c	['7z_fuzzer']	['7z_fuzzer']
/src/lzma-fuzz/sdk/C/CpuArch.c	['filters_fuzzer', 'xzdec_fuzzer', '7z_fuzzer', 'xzenc_fuzzer']	['filters_fuzzer', 'xzdec_fuzzer', '7z_fuzzer', 'xzenc_fuzzer']
/src/lzma-fuzz/sdk/C/Bcj2.c	['7z_fuzzer']	['7z_fuzzer']

Directories in report

Directory
/src/lzma-fuzz/./
/src/lzma-fuzz/sdk/C/
/src/lzma-fuzz/