High level conclusions

Fuzzers reach 64.43% code coverage.

Fuzzers reach 45.43% of cyclomatic complexity.

Fuzzers reach 44.91% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

543 / 1209

Cyclomatic complexity statically reachable by fuzzers

3130 / 6889

Runtime code coverage of functions

779 / 1209

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: cms_gdb_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	12	19.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	50	80.6%
All colors	62	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
6	8	_cmsContextGetClientChunk	call site: 00008	_cmsEnterCriticalSectionPrimitive
4	3	_cmsMallocZero	call site: 00003	cmsSignalError
1	26	ToSpherical	call site: 00026	cmsSignalError
1	28	GetPoint	call site: 00028	cmsSignalError

Runtime coverage analysis

Covered functions

27

Functions that are reachable but not covered

12

Reachable functions

35

Percentage of reachable functions covered

65.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
cms_gdb_fuzzer.c	1
lcmscmssm.c	15
lcmscmserr.c	3
lcmscmsplugin.c	3
lcms./lcms2_internal.h	2
lcmscmsmtrx.c	3

Fuzzer: cms_md5_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	68	30.7%
gold	[1:9]	1	0.45%
yellow	[10:29]	1	0.45%
greenyellow	[30:49]	2	0.90%
lawngreen	50+	149	67.4%
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
27	82	cmsOpenProfileFromMemTHR	call site: 00082	cmsSaveProfileToFile
12	167	_cmsWriteAlignment	call site: 00167	_cmsGetTagTypeHandler
6	10	_cmsContextGetClientChunk	call site: 00010	_cmsEnterCriticalSectionPrimitive
4	34	cmsOpenIOhandlerFromMem	call site: 00034	_cmsFree
4	186	cmsSaveProfileToIOhandler	call site: 00186	_cmsUnlockMutex
3	30	_cmsMalloc	call site: 00030	_cmsFree
2	116	cmsOpenIOhandlerFromNULL	call site: 00116	_cmsFree
2	162	SaveTags	call site: 00162	_cmsFree
1	1	LLVMFuzzerTestOneInput	call site: 00001	cmsOpenProfileFromMemTHR
1	5	_cmsMallocZero	call site: 00005	cmsSignalError
1	8	cmsSignalError	call site: 00008	__assert_fail
1	21	_cmsCreateMutex	call site: 00021	_cmsFree

Runtime coverage analysis

Covered functions

70

Functions that are reachable but not covered

22

Reachable functions

72

Percentage of reachable functions covered

69.44%

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
cms_md5_fuzzer.c	1
lcmscmsio0.c	24
lcmscmserr.c	10
lcmscmsplugin.c	14
lcms./lcms2_internal.h	2
lcmscmstypes.c	3
lcmscmswtpnt.c	1
lcmscmsmd5.c	5

Fuzzer: cms_dict_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	80	34.0%
gold	[1:9]	2	0.85%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	153	65.1%
All colors	235	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
16	144	cmsCreateContext	call site: 00144	cmsDeleteContext
6	39	RegisterTypesPlugin	call site: 00039	_cmsPluginMalloc
5	127	cmsCreateContext	call site: 00127	DupPluginOptimizationList
4	6	_cmsMalloc	call site: 00006	cmsSignalError
4	27	_cmsFree	call site: 00027	cmsDeleteContext
4	96	_cmsAllocCurvesPluginChunk	call site: 00096	DupPluginCurvesList
4	103	_cmsAllocFormattersPluginChunk	call site: 00103	DupFormatterFactoryList
3	109	cmsCreateContext	call site: 00109	DupTagTypeList
3	117	cmsCreateContext	call site: 00117	DupTagList
3	122	cmsCreateContext	call site: 00122	DupPluginIntentsList
3	134	cmsCreateContext	call site: 00134	DupPluginTransformList
3	183	generateWideString	call site: 00183	cmsDeleteContext

Runtime coverage analysis

Covered functions

79

Functions that are reachable but not covered

17

Reachable functions

90

Percentage of reachable functions covered

81.11%

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
cms_dict_fuzzer.c	2
lcmscmsplugin.c	10
lcmscmserr.c	20
lcms./lcms2_internal.h	2
lcmscmsintrp.c	2
lcmscmstypes.c	9
lcmscmspack.c	3
lcmscmscnvrt.c	3
lcmscmsgamma.c	3
lcmscmsopt.c	3
lcmscmsxform.c	5
lcmscmsnamed.c	22

Fuzzer: cms_cie_cam02_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	71	30.7%
gold	[1:9]	6	2.59%
yellow	[10:29]	139	60.1%
greenyellow	[30:49]	2	0.86%
lawngreen	50+	13	5.62%
All colors	231	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
16	144	cmsCreateContext	call site: 00144	cmsDeleteContext
6	39	RegisterTypesPlugin	call site: 00039	_cmsPluginMalloc
5	127	cmsCreateContext	call site: 00127	DupPluginOptimizationList
4	6	_cmsMalloc	call site: 00006	cmsSignalError
4	27	_cmsFree	call site: 00027	cmsDeleteContext
4	96	_cmsAllocCurvesPluginChunk	call site: 00096	DupPluginCurvesList
4	103	_cmsAllocFormattersPluginChunk	call site: 00103	DupFormatterFactoryList
3	109	cmsCreateContext	call site: 00109	DupTagTypeList
3	117	cmsCreateContext	call site: 00117	DupTagList
3	122	cmsCreateContext	call site: 00122	DupPluginIntentsList
3	134	cmsCreateContext	call site: 00134	DupPluginTransformList
2	32	cmsUnregisterPluginsTHR	call site: 00032	_cmsContextGetClientChunk

Runtime coverage analysis

Covered functions

69

Functions that are reachable but not covered

21

Reachable functions

87

Percentage of reachable functions covered

75.86%

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
cms_cie_cam02_fuzzer.c	1
lcmscmsplugin.c	10
lcmscmserr.c	17
lcms./lcms2_internal.h	2
lcmscmsintrp.c	2
lcmscmstypes.c	9
lcmscmspack.c	3
lcmscmscnvrt.c	3
lcmscmsgamma.c	3
lcmscmsopt.c	3
lcmscmsxform.c	5
lcmscmscam02.c	19

Fuzzer: cmsIT8_load_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	58	16.4%
gold	[1:9]	5	1.42%
yellow	[10:29]	4	1.13%
greenyellow	[30:49]	5	1.42%
lawngreen	50+	280	79.5%
All colors	352	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
10	265	HeaderSection	call site: 00265	AddToList
7	317	WriteHeader	call site: 00317	Writef
6	12	_cmsContextGetClientChunk	call site: 00012	_cmsEnterCriticalSectionPrimitive
4	253	HeaderSection	call site: 00253	InSymbol
3	294	cmsIT8SaveToFile	call site: 00294	SynError
2	303	WriteStr	call site: 00303	cmsSignalError
2	306	WriteHeader	call site: 00306	Writef
2	310	Writef	call site: 00310	WriteStr
1	7	_cmsMallocZero	call site: 00007	cmsSignalError
1	10	cmsSignalError	call site: 00010	__assert_fail
1	23	AllocBigBlock	call site: 00023	_cmsFree
1	25	_cmsFree	call site: 00025	SynError

Runtime coverage analysis

Covered functions

70

Functions that are reachable but not covered

26

Reachable functions

92

Percentage of reachable functions covered

71.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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
cmsIT8_load_fuzzer.c	1
lcmscmscgats.c	59
lcmscmserr.c	5
lcmscmsplugin.c	3
lcms./lcms2_internal.h	2

Fuzzer: cms_transform_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	375	44.5%
gold	[1:9]	2	0.23%
yellow	[10:29]	17	2.01%
greenyellow	[30:49]	2	0.23%
lawngreen	50+	446	52.9%
All colors	842	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
41	119	_cmsUnlockMutex	call site: 00119	SaveTags
29	82	cmsOpenProfileFromMemTHR	call site: 00082	cmsSaveProfileToFile
28	808	cmsMLUdup	call site: 00808	cmsCreateTransformTHR
20	738	cmsCreateExtendedTransform	call site: 00738	_cmsCreateGamutCheckPipeline
17	525	OptimizeByResampling	call site: 00525	PrelinOpt16alloc
15	791	cmsCreateExtendedTransform	call site: 00791	_cmsCompileProfileSequence
10	683	cmsDoTransform	call site: 00683	cmsCloseProfile
9	563	cmsReverseToneCurveEx	call site: 00563	cmsBuildTabulatedToneCurve16
9	635	cmsD50_xyY	call site: 00635	cmsCreateRGBProfileTHR
9	672	cmsStageAllocToneCurves	call site: 00672	cmsCreateTransformTHR
8	30	_cmsMalloc	call site: 00030	_cmsFree
8	161	cmsGetProfileVersion	call site: 00161	_cmsGetTagTypeHandler

Runtime coverage analysis

Covered functions

366

Functions that are reachable but not covered

63

Reachable functions

253

Percentage of reachable functions covered

75.1%

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
cms_transform_fuzzer.c	1
lcmscmsio0.c	43
lcmscmserr.c	13
lcmscmsplugin.c	15
lcms./lcms2_internal.h	5
lcmscmstypes.c	4
lcmscmswtpnt.c	6
lcmscmsvirt.c	7
lcmscmsgamma.c	20
lcmscmsintrp.c	5
lcmscmsnamed.c	16
lcmscmspcs.c	10
lcmscmsmtrx.c	5
lcmscmsxform.c	15
lcmscmslut.c	42
lcmscmspack.c	4
lcmscmsopt.c	19
lcmscmsgmt.c	3
lcmscmscnvrt.c	2
lcmscmsio1.c	3

Fuzzer: cms_virtual_profile_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	353	36.2%
gold	[1:9]	7	0.71%
yellow	[10:29]	25	2.56%
greenyellow	[30:49]	5	0.51%
lawngreen	50+	584	59.9%
All colors	974	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
41	119	_cmsUnlockMutex	call site: 00119	SaveTags
29	82	cmsOpenProfileFromMemTHR	call site: 00082	cmsSaveProfileToFile
28	808	cmsMLUdup	call site: 00808	cmsCreateTransformTHR
20	738	cmsCreateExtendedTransform	call site: 00738	_cmsCreateGamutCheckPipeline
12	888	cmsTransform2DeviceLink	call site: 00888	IsPCS
10	683	cmsDoTransform	call site: 00683	cmsCloseProfile
9	672	cmsStageAllocToneCurves	call site: 00672	cmsCreateTransformTHR
9	797	cmsAllocProfileSequenceDescription	call site: 00797	GetMLUFromProfile
8	30	_cmsMalloc	call site: 00030	_cmsFree
8	161	cmsGetProfileVersion	call site: 00161	_cmsGetTagTypeHandler
8	182	_cmsSearchTag	call site: 00182	SaveTags
8	635	cmsD50_xyY	call site: 00635	cmsCreateRGBProfileTHR

Runtime coverage analysis

Covered functions

412

Functions that are reachable but not covered

52

Reachable functions

274

Percentage of reachable functions covered

81.02%

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
cms_virtual_profile_fuzzer.c	1
lcmscmsio0.c	43
lcmscmserr.c	13
lcmscmsplugin.c	15
lcms./lcms2_internal.h	5
lcmscmstypes.c	4
lcmscmswtpnt.c	6
lcmscmsvirt.c	16
lcmscmsgamma.c	21
lcmscmsintrp.c	5
lcmscmsnamed.c	19
lcmscmspcs.c	10
lcmscmsmtrx.c	5
lcmscmsxform.c	17
lcmscmslut.c	46
lcmscmspack.c	4
lcmscmsopt.c	19
lcmscmsgmt.c	3
lcmscmscnvrt.c	2
lcmscmsio1.c	4

Fuzzer: cms_devicelink_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	192	51.6%
gold	[1:9]	3	0.80%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	68	18.2%
lawngreen	50+	109	29.3%
All colors	372	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
80	259	cmsPipelineFree	call site: 00259	cmsCloseProfile
24	340	_cmsMalloc	call site: 00340	SaveTags
8	123	AllocateToneCurveStruct	call site: 00123	cmsFreeToneCurve
7	96	cmsStageAllocToneCurves	call site: 00096	cmsEvalToneCurveFloat
6	8	_cmsContextGetClientChunk	call site: 00008	_cmsEnterCriticalSectionPrimitive
6	216	_cmsGetTagTypeHandler	call site: 00216	cmsSignalError
5	192	_cmsSearchTag	call site: 00192	_cmsDeleteTagByPos
4	46	cmsStageAllocCLut16bitGranular	call site: 00046	FromFloatTo16
4	64	_cmsSetInterpolationRoutine	call site: 00064	_cmsFree
4	209	cmsWriteTag	call site: 00209	cmsSignalError
4	241	cmsMLUsetASCII	call site: 00241	AddMLUBlock
3	200	_cmsNewTag	call site: 00200	_cmsDeleteTagByPos

Runtime coverage analysis

Covered functions

122

Functions that are reachable but not covered

43

Reachable functions

134

Percentage of reachable functions covered

67.91%

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
cms_devicelink_fuzzer.c	1
lcmscmsvirt.c	5
lcmscmserr.c	13
lcmscmsplugin.c	12
lcms./lcms2_internal.h	5
lcmscmsio0.c	26
lcmscmslut.c	23
lcmscmspcs.c	2
lcmscmsintrp.c	5
lcmscmsgamma.c	12
lcmscmsnamed.c	12
lcmscmstypes.c	3
lcmscmsio1.c	1
lcmscmswtpnt.c	1

Fuzzer: cms_transform_extended_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	364	31.4%
gold	[1:9]	12	1.03%
yellow	[10:29]	10	0.86%
greenyellow	[30:49]	8	0.69%
lawngreen	50+	764	65.9%
All colors	1158	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
41	120	_cmsUnlockMutex	call site: 00120	SaveTags
29	83	cmsOpenProfileFromMemTHR	call site: 00083	cmsSaveProfileToFile
25	1122	_cmsCompileProfileSequence	call site: 01122	cmsCreateTransformTHR
16	786	cmsCreateContext	call site: 00786	cmsDeleteContext
10	1010	cmsDoTransform	call site: 01010	cmsCloseProfile
8	31	_cmsMalloc	call site: 00031	_cmsFree
8	162	cmsGetProfileVersion	call site: 00162	_cmsGetTagTypeHandler
8	183	_cmsSearchTag	call site: 00183	SaveTags
8	367	AllocateToneCurveStruct	call site: 00367	cmsFreeToneCurve
8	1000	cmsCreateExtendedTransform	call site: 01000	cmsDetectRGBProfileGamma
7	588	run_test	call site: 00588	cmsCreateBCHSWabstractProfileTHR
6	113	_cmsLockMutex	call site: 00113	cmsOpenIOhandlerFromNULL

Runtime coverage analysis

Covered functions

493

Functions that are reachable but not covered

50

Reachable functions

336

Percentage of reachable functions covered

85.12%

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
cms_transform_extended_fuzzer.c	2
lcmscmsio0.c	43
lcmscmserr.c	26
lcmscmsplugin.c	22
lcms./lcms2_internal.h	5
lcmscmstypes.c	13
lcmscmswtpnt.c	7
lcmscmsvirt.c	19
lcmscmspcs.c	25
lcmscmsnamed.c	16
lcmscmsmtrx.c	5
lcmscmslut.c	46
lcmscmsgamma.c	23
lcmscmsintrp.c	7
lcmscmspack.c	7
lcmscmscnvrt.c	5
lcmscmsopt.c	22
lcmscmsxform.c	19
lcmscmsgmt.c	3
lcmscmsio1.c	3

Fuzzer: cms_transform_all_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	270	32.4%
gold	[1:9]	7	0.84%
yellow	[10:29]	7	0.84%
greenyellow	[30:49]	11	1.32%
lawngreen	50+	536	64.5%
All colors	831	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
41	120	_cmsUnlockMutex	call site: 00120	SaveTags
29	83	cmsOpenProfileFromMemTHR	call site: 00083	cmsSaveProfileToFile
29	598	cmsCreateRGBProfileTHR	call site: 00598	cmsCloseProfile
25	802	_cmsCompileProfileSequence	call site: 00802	cmsCreateTransformTHR
8	31	_cmsMalloc	call site: 00031	_cmsFree
8	162	cmsGetProfileVersion	call site: 00162	_cmsGetTagTypeHandler
8	183	_cmsSearchTag	call site: 00183	SaveTags
7	430	AllocateToneCurveStruct	call site: 00430	_cmsFree
6	11	_cmsContextGetClientChunk	call site: 00011	_cmsEnterCriticalSectionPrimitive
6	113	_cmsLockMutex	call site: 00113	cmsOpenIOhandlerFromNULL
6	570	cmsWriteTag	call site: 00570	cmsSignalError
6	758	cmsIsMatrixShaper	call site: 00758	cmsCreateExtendedTransform

Runtime coverage analysis

Covered functions

424

Functions that are reachable but not covered

41

Reachable functions

251

Percentage of reachable functions covered

83.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
cms_transform_all_fuzzer.c	2
lcmscmsio0.c	43
lcmscmserr.c	13
lcmscmsplugin.c	15
lcms./lcms2_internal.h	5
lcmscmstypes.c	4
lcmscmswtpnt.c	6
lcmscmsxform.c	15
lcmscmslut.c	42
lcmscmspack.c	4
lcmscmsopt.c	19
lcmscmsmtrx.c	5
lcmscmspcs.c	10
lcmscmsgamma.c	20
lcmscmsintrp.c	5
lcmscmsnamed.c	16
lcmscmsgmt.c	3
lcmscmsvirt.c	4
lcmscmscnvrt.c	2
lcmscmsio1.c	3

Fuzzer: cms_overwrite_transform_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	379	45.6%
gold	[1:9]	8	0.96%
yellow	[10:29]	18	2.16%
greenyellow	[30:49]	7	0.84%
lawngreen	50+	418	50.3%
All colors	830	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
41	119	_cmsUnlockMutex	call site: 00119	SaveTags
37	597	cmsCreateRGBProfileTHR	call site: 00597	_cmsStageAllocIdentityCurves
29	82	cmsOpenProfileFromMemTHR	call site: 00082	cmsSaveProfileToFile
28	798	cmsMLUdup	call site: 00798	cmsCreateTransformTHR
20	728	cmsCreateExtendedTransform	call site: 00728	_cmsCreateGamutCheckPipeline
17	369	OptimizeByResampling	call site: 00369	PrelinOpt16alloc
13	783	cmsCreateExtendedTransform	call site: 00783	_cmsCompileProfileSequence
10	673	cmsDoTransform	call site: 00673	cmsCloseProfile
9	662	cmsStageAllocToneCurves	call site: 00662	cmsCreateTransformTHR
8	30	_cmsMalloc	call site: 00030	_cmsFree
8	161	cmsGetProfileVersion	call site: 00161	_cmsGetTagTypeHandler
8	182	_cmsSearchTag	call site: 00182	SaveTags

Runtime coverage analysis

Covered functions

349

Functions that are reachable but not covered

60

Reachable functions

250

Percentage of reachable functions covered

76.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
cms_overwrite_transform_fuzzer.c	1
lcmscmsio0.c	43
lcmscmserr.c	13
lcmscmsplugin.c	15
lcms./lcms2_internal.h	5
lcmscmstypes.c	4
lcmscmswtpnt.c	6
lcmscmsxform.c	15
lcmscmslut.c	42
lcmscmspack.c	4
lcmscmsopt.c	19
lcmscmsmtrx.c	5
lcmscmspcs.c	10
lcmscmsgamma.c	20
lcmscmsintrp.c	5
lcmscmsnamed.c	16
lcmscmsgmt.c	3
lcmscmsvirt.c	4
lcmscmscnvrt.c	2
lcmscmsio1.c	3

Fuzzer: cms_postscript_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	403	27.7%
gold	[1:9]	13	0.89%
yellow	[10:29]	18	1.23%
greenyellow	[30:49]	22	1.51%
lawngreen	50+	998	68.6%
All colors	1454	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
41	265	_cmsUnlockMutex	call site: 00265	SaveTags
29	228	cmsOpenProfileFromMemTHR	call site: 00228	cmsSaveProfileToFile
29	436	cmsCreateRGBProfileTHR	call site: 00436	cmsCloseProfile
28	952	cmsMLUdup	call site: 00952	cmsCreateTransformTHR
16	144	cmsCreateContext	call site: 00144	cmsDeleteContext
13	937	cmsCreateExtendedTransform	call site: 00937	_cmsCompileProfileSequence
9	609	_MultiplyMatrix	call site: 00609	_RemoveElement
8	176	cmsOpenIOhandlerFromMem	call site: 00176	_cmsFree
8	307	cmsGetProfileVersion	call site: 00307	_cmsGetTagTypeHandler
8	328	_cmsSearchTag	call site: 00328	SaveTags
8	519	AllocateToneCurveStruct	call site: 00519	cmsFreeToneCurve
6	39	RegisterTypesPlugin	call site: 00039	_cmsPluginMalloc

Runtime coverage analysis

Covered functions

468

Functions that are reachable but not covered

63

Reachable functions

378

Percentage of reachable functions covered

83.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
cms_postscript_fuzzer.c	1
lcmscmsplugin.c	23
lcmscmserr.c	26
lcms./lcms2_internal.h	5
lcmscmsintrp.c	7
lcmscmstypes.c	13
lcmscmspack.c	8
lcmscmscnvrt.c	5
lcmscmsgamma.c	23
lcmscmsopt.c	22
lcmscmsxform.c	21
lcmscmsio0.c	45
lcmscmswtpnt.c	6
lcmscmsps2.c	32
lcmscmsvirt.c	6
lcmscmspcs.c	14
lcmscmsnamed.c	24
lcmscmsmtrx.c	5
lcmscmslut.c	53
lcmscmsgmt.c	3
lcmscmsio1.c	11
lcmscmssamp.c	5

Fuzzer: cms_universal_transform_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	379	45.6%
gold	[1:9]	6	0.72%
yellow	[10:29]	10	1.20%
greenyellow	[30:49]	2	0.24%
lawngreen	50+	433	52.1%
All colors	830	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
41	119	_cmsUnlockMutex	call site: 00119	SaveTags
37	597	cmsCreateRGBProfileTHR	call site: 00597	_cmsStageAllocIdentityCurves
29	82	cmsOpenProfileFromMemTHR	call site: 00082	cmsSaveProfileToFile
28	798	cmsMLUdup	call site: 00798	cmsCreateTransformTHR
20	728	cmsCreateExtendedTransform	call site: 00728	_cmsCreateGamutCheckPipeline
17	369	OptimizeByResampling	call site: 00369	PrelinOpt16alloc
13	783	cmsCreateExtendedTransform	call site: 00783	_cmsCompileProfileSequence
10	673	cmsDoTransform	call site: 00673	cmsCloseProfile
9	662	cmsStageAllocToneCurves	call site: 00662	cmsCreateTransformTHR
8	30	_cmsMalloc	call site: 00030	_cmsFree
8	161	cmsGetProfileVersion	call site: 00161	_cmsGetTagTypeHandler
8	182	_cmsSearchTag	call site: 00182	SaveTags

Runtime coverage analysis

Covered functions

349

Functions that are reachable but not covered

60

Reachable functions

250

Percentage of reachable functions covered

76.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
cms_universal_transform_fuzzer.c	1
lcmscmsio0.c	43
lcmscmserr.c	13
lcmscmsplugin.c	15
lcms./lcms2_internal.h	5
lcmscmstypes.c	4
lcmscmswtpnt.c	6
lcmscmsxform.c	15
lcmscmslut.c	42
lcmscmspack.c	4
lcmscmsopt.c	19
lcmscmsmtrx.c	5
lcmscmspcs.c	10
lcmscmsgamma.c	20
lcmscmsintrp.c	5
lcmscmsnamed.c	16
lcmscmsgmt.c	3
lcmscmsvirt.c	4
lcmscmscnvrt.c	2
lcmscmsio1.c	3

Fuzzer: cms_profile_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	44	15.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	0.68%
greenyellow	[30:49]	1	0.34%
lawngreen	50+	245	83.9%
All colors	292	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
6	15	_cmsContextGetClientChunk	call site: 00015	_cmsEnterCriticalSectionPrimitive
6	228	cmsOpenIOhandlerFromMem	call site: 00228	_cmsFree
4	32	cmsOpenIOhandlerFromFile	call site: 00032	_cmsFree
4	235	cmsOpenIOhandlerFromMem	call site: 00235	_cmsFree
3	44	cmsfilelength	call site: 00044	_cmsFree
3	48	cmsOpenIOhandlerFromFile	call site: 00048	_cmsFree
2	37	cmsOpenIOhandlerFromFile	call site: 00037	_cmsFree
2	107	cmsOpenIOhandlerFromNULL	call site: 00107	_cmsFree
2	154	_cmsMalloc	call site: 00154	_cmsFree
2	216	cmsReadTag	call site: 00216	cmsSignalError
2	278	_cmsDeleteTagByPos	call site: 00278	_cmsUnlockMutex
1	6	LLVMFuzzerTestOneInput	call site: 00006	cmsOpenProfileFromFileTHR

Runtime coverage analysis

Covered functions

224

Functions that are reachable but not covered

19

Reachable functions

88

Percentage of reachable functions covered

78.41%

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
cms_profile_fuzzer.c	1
lcmscmsio0.c	33
lcmscmserr.c	11
lcmscmsplugin.c	15
lcms./lcms2_internal.h	2
lcmscmstypes.c	4
lcmscmswtpnt.c	1
lcmscmsio1.c	2
lcmscmsnamed.c	3

Fuzzer: cms_cgats_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	141	33.6%
gold	[1:9]	1	0.23%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	3	0.71%
lawngreen	50+	274	65.3%
All colors	419	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
20	273	InStringSymbol	call site: 00273	InSymbol
12	249	InSymbol	call site: 00249	StringCat
12	334	DataSection	call site: 00334	SkipEOLN
10	363	HeaderSection	call site: 00363	AddToList
8	347	ParseIT8	call site: 00347	InSymbol
6	8	_cmsContextGetClientChunk	call site: 00008	_cmsEnterCriticalSectionPrimitive
6	240	ReadReal	call site: 00240	NextCh
5	142	WriteHeader	call site: 00142	Writef
4	40	cmsstrcasecmp	call site: 00040	SynError
3	117	cmsIT8SaveToFile	call site: 00117	SynError
3	165	WriteData	call site: 00165	WriteStr
3	227	InSymbol	call site: 00227	SynError

Runtime coverage analysis

Covered functions

83

Functions that are reachable but not covered

30

Reachable functions

108

Percentage of reachable functions covered

72.22%

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
cms_cgats_fuzzer.c	1
lcmscmscgats.c	76
lcmscmserr.c	4
lcmscmsplugin.c	3
lcms./lcms2_internal.h	2

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
BlackPreservingKPlaneIntents	/src/lcms/src/cmscnvrt.c	7	['N/A', 'int', 'N/A', 'N/A', 'N/A', 'N/A', 'int']	17	0	439	70	27	319	0	2026	409
Type_Dictionary_Read	/src/lcms/src/cmstypes.c	4	['N/A', 'N/A', 'N/A', 'int']	10	0	441	79	31	42	0	216	131
Type_LUTB2A_Read	/src/lcms/src/cmstypes.c	4	['N/A', 'N/A', 'N/A', 'int']	13	0	333	58	25	76	0	415	109
OptimizeMatrixShaper	/src/lcms/src/cmsopt.c	5	['N/A', 'int', 'N/A', 'N/A', 'N/A']	9	0	354	58	24	87	0	422	108
OptimizeByComputingLinearization	/src/lcms/src/cmsopt.c	5	['N/A', 'int', 'N/A', 'N/A', 'N/A']	10	0	874	141	51	95	0	646	92
Type_LUTA2B_Write	/src/lcms/src/cmstypes.c	4	['N/A', 'N/A', 'N/A', 'int']	6	0	488	73	32	33	0	159	82
cmsCreateDeviceLinkFromCubeFile	/src/lcms/src/cmscgats.c	1	['N/A']	12	0	15	3	2	140	0	684	78
FloatXFORM	/src/lcms/src/cmsxform.c	6	['N/A', 'N/A', 'N/A', 'int', 'int', 'N/A']	7	0	199	21	7	18	0	101	73
Type_ProfileSequenceId_Write	/src/lcms/src/cmstypes.c	4	['N/A', 'N/A', 'N/A', 'int']	10	0	70	8	4	30	0	149	73
Eval15InputsFloat	/src/lcms/src/cmsintrp.c	3	['N/A', 'N/A', 'N/A']	13	0	157	10	4	14	0	72	70

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

Functions statically reachable by fuzzers

689 / 1209

Cyclomatic complexity statically reachable by fuzzers

4353 / 6889

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.

cms_gdb_fuzzer.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=['_cmsContextGetClientChunk', '_cmsMallocZero', 'ToSpherical', 'GetPoint']

cms_md5_fuzzer.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=['cmsOpenProfileFromMemTHR', '_cmsWriteAlignment', '_cmsContextGetClientChunk', 'cmsOpenIOhandlerFromMem', 'cmsSaveProfileToIOhandler', '_cmsMalloc', 'cmsOpenIOhandlerFromNULL', 'SaveTags', 'LLVMFuzzerTestOneInput', '_cmsMallocZero']

cms_dict_fuzzer.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=['cmsCreateContext', 'RegisterTypesPlugin', '_cmsMalloc', '_cmsFree', '_cmsAllocCurvesPluginChunk', '_cmsAllocFormattersPluginChunk']

cms_cie_cam02_fuzzer.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=['cmsCreateContext', 'RegisterTypesPlugin', '_cmsMalloc', '_cmsFree', '_cmsAllocCurvesPluginChunk', '_cmsAllocFormattersPluginChunk']

cmsIT8_load_fuzzer.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=['HeaderSection', 'WriteHeader', '_cmsContextGetClientChunk', 'cmsIT8SaveToFile', 'WriteStr', 'Writef', '_cmsMallocZero', 'cmsSignalError']

cms_transform_fuzzer.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=['_cmsUnlockMutex', 'cmsOpenProfileFromMemTHR', 'cmsMLUdup', 'cmsCreateExtendedTransform', 'OptimizeByResampling', 'cmsDoTransform', 'cmsReverseToneCurveEx', 'cmsD50_xyY', 'cmsStageAllocToneCurves']

cms_virtual_profile_fuzzer.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=['_cmsUnlockMutex', 'cmsOpenProfileFromMemTHR', 'cmsMLUdup', 'cmsCreateExtendedTransform', 'cmsTransform2DeviceLink', 'cmsDoTransform', 'cmsStageAllocToneCurves', 'cmsAllocProfileSequenceDescription', '_cmsMalloc', 'cmsGetProfileVersion']

cms_devicelink_fuzzer.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=['cmsPipelineFree', '_cmsMalloc', 'AllocateToneCurveStruct', 'cmsStageAllocToneCurves', '_cmsContextGetClientChunk', '_cmsGetTagTypeHandler', '_cmsSearchTag', 'cmsStageAllocCLut16bitGranular', '_cmsSetInterpolationRoutine', 'cmsWriteTag']

cms_transform_extended_fuzzer.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=['_cmsUnlockMutex', 'cmsOpenProfileFromMemTHR', '_cmsCompileProfileSequence', 'cmsCreateContext', 'cmsDoTransform', '_cmsMalloc', 'cmsGetProfileVersion', '_cmsSearchTag', 'AllocateToneCurveStruct', 'cmsCreateExtendedTransform']

cms_transform_all_fuzzer.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=['_cmsUnlockMutex', 'cmsOpenProfileFromMemTHR', 'cmsCreateRGBProfileTHR', '_cmsCompileProfileSequence', '_cmsMalloc', 'cmsGetProfileVersion', '_cmsSearchTag', 'AllocateToneCurveStruct', '_cmsContextGetClientChunk', '_cmsLockMutex']

cms_overwrite_transform_fuzzer.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=['_cmsUnlockMutex', 'cmsCreateRGBProfileTHR', 'cmsOpenProfileFromMemTHR', 'cmsMLUdup', 'cmsCreateExtendedTransform', 'OptimizeByResampling', 'cmsDoTransform', 'cmsStageAllocToneCurves', '_cmsMalloc']

cms_postscript_fuzzer.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=['_cmsUnlockMutex', 'cmsOpenProfileFromMemTHR', 'cmsCreateRGBProfileTHR', 'cmsMLUdup', 'cmsCreateContext', 'cmsCreateExtendedTransform', '_MultiplyMatrix', 'cmsOpenIOhandlerFromMem', 'cmsGetProfileVersion', '_cmsSearchTag']

cms_universal_transform_fuzzer.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=['_cmsUnlockMutex', 'cmsCreateRGBProfileTHR', 'cmsOpenProfileFromMemTHR', 'cmsMLUdup', 'cmsCreateExtendedTransform', 'OptimizeByResampling', 'cmsDoTransform', 'cmsStageAllocToneCurves', '_cmsMalloc']

cms_profile_fuzzer.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=['_cmsContextGetClientChunk', 'cmsOpenIOhandlerFromMem', 'cmsOpenIOhandlerFromFile', 'cmsfilelength', 'cmsOpenIOhandlerFromNULL', '_cmsMalloc', 'cmsReadTag']

cms_cgats_fuzzer.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=['InStringSymbol', 'InSymbol', 'DataSection', 'HeaderSection', 'ParseIT8', '_cmsContextGetClientChunk', 'ReadReal', 'WriteHeader', 'cmsstrcasecmp', 'cmsIT8SaveToFile']

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
cmsPluginTHR	58	7	12.06%	['cms_transform_extended_fuzzer', 'cms_postscript_fuzzer', 'cms_dict_fuzzer', 'cms_cie_cam02_fuzzer']
HeaderSection	70	38	54.28%	['cmsIT8_load_fuzzer', 'cms_cgats_fuzzer']
_cmsHandleExtraChannels	67	15	22.38%	['cms_postscript_fuzzer', 'cms_transform_extended_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_all_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_transform_fuzzer']
cmsWriteTag	71	38	53.52%	['cms_postscript_fuzzer', 'cms_transform_extended_fuzzer', 'cms_devicelink_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_all_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_transform_fuzzer']
ComputeAbsoluteIntent	38	9	23.68%	['cms_transform_all_fuzzer', 'cms_postscript_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer']
PrelinEval8	72	34	47.22%	['cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_universal_transform_fuzzer']
ParseFloatNumber	49	13	26.53%	['cms_cgats_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/lcms/src/cmssamp.c	['cms_postscript_fuzzer']	['cms_postscript_fuzzer']
/src/lcms/src/cmsgmt.c	['cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']	['cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_postscript_fuzzer']
/src/lcms/src/cmscam02.c	['cms_cie_cam02_fuzzer']	['cms_cie_cam02_fuzzer']
/src/cms_devicelink_fuzzer.c	['cms_devicelink_fuzzer']	['cms_devicelink_fuzzer']
/src/cms_overwrite_transform_fuzzer.c	['cms_overwrite_transform_fuzzer']	['cms_overwrite_transform_fuzzer']
/src/cms_md5_fuzzer.c	['cms_md5_fuzzer']	['cms_md5_fuzzer']
/src/lcms/src/cmsps2.c	['cms_postscript_fuzzer']	['cms_postscript_fuzzer']
/src/lcms/src/cmslut.c	['cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']	['cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']
/src/lcms/src/cmsnamed.c	['cms_dict_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer']	['cms_dict_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer']
/src/lcms/src/cmsxform.c	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']
/src/lcms/src/cmswtpnt.c	['cms_md5_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer']	['cms_md5_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer']
/src/lcms/src/cmsgamma.c	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']
/src/lcms/src/cmserr.c	['cms_gdb_fuzzer', 'cms_md5_fuzzer', 'cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cmsIT8_load_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer', 'cms_cgats_fuzzer']	['cms_gdb_fuzzer', 'cms_md5_fuzzer', 'cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cmsIT8_load_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer', 'cms_cgats_fuzzer']
/src/lcms/src/cmsalpha.c	[]	[]
/src/cms_profile_fuzzer.c	['cms_profile_fuzzer']	['cms_profile_fuzzer']
/src/lcms/src/cmssm.c	['cms_gdb_fuzzer']	['cms_gdb_fuzzer']
/src/lcms/src/cmsio0.c	['cms_md5_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer']	['cms_md5_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer']
/src/cmsIT8_load_fuzzer.c	['cmsIT8_load_fuzzer']	['cmsIT8_load_fuzzer']
/src/lcms/src/cmspack.c	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']
/src/lcms/src/cmsopt.c	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']
/src/lcms/src/cmstypes.c	['cms_md5_fuzzer', 'cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer']	['cms_md5_fuzzer', 'cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer']
/src/lcms/src/cmsvirt.c	['cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']	['cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']
/src/lcms/src/cmscgats.c	['cmsIT8_load_fuzzer', 'cms_cgats_fuzzer']	['cmsIT8_load_fuzzer', 'cms_cgats_fuzzer']
/src/lcms/src/cmspcs.c	['cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']	['cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']
/src/cms_gdb_fuzzer.c	['cms_gdb_fuzzer']	['cms_gdb_fuzzer']
/src/cms_transform_extended_fuzzer.c	['cms_transform_extended_fuzzer']	['cms_transform_extended_fuzzer']
/src/cms_cgats_fuzzer.c	['cms_cgats_fuzzer']	['cms_cgats_fuzzer']
/src/lcms/src/cmsmd5.c	['cms_md5_fuzzer']	['cms_md5_fuzzer']
/src/lcms/src/./lcms2_internal.h	['cms_gdb_fuzzer', 'cms_md5_fuzzer', 'cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cmsIT8_load_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer', 'cms_cgats_fuzzer']	[]
/src/cms_universal_transform_fuzzer.c	['cms_universal_transform_fuzzer']	['cms_universal_transform_fuzzer']
/src/lcms/src/cmshalf.c	[]	[]
/src/lcms/src/cmscnvrt.c	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']
/src/cms_virtual_profile_fuzzer.c	['cms_virtual_profile_fuzzer']	['cms_virtual_profile_fuzzer']
/src/cms_postscript_fuzzer.c	['cms_postscript_fuzzer']	['cms_postscript_fuzzer']
/src/lcms/src/cmsio1.c	['cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer']	['cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer']
/src/lcms/src/cmsintrp.c	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']	['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']
/src/cms_dict_fuzzer.c	['cms_dict_fuzzer']	['cms_dict_fuzzer']
/src/lcms/src/cmsplugin.c	['cms_gdb_fuzzer', 'cms_md5_fuzzer', 'cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cmsIT8_load_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer', 'cms_cgats_fuzzer']	['cms_gdb_fuzzer', 'cms_md5_fuzzer', 'cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cmsIT8_load_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer', 'cms_profile_fuzzer', 'cms_cgats_fuzzer']
/src/cms_cie_cam02_fuzzer.c	['cms_cie_cam02_fuzzer']	['cms_cie_cam02_fuzzer']
/src/cms_transform_fuzzer.c	['cms_transform_fuzzer']	['cms_transform_fuzzer']
/src/cms_transform_all_fuzzer.c	['cms_transform_all_fuzzer']	['cms_transform_all_fuzzer']
/src/lcms/src/cmsmtrx.c	['cms_gdb_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']	['cms_gdb_fuzzer', 'cms_transform_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_transform_extended_fuzzer', 'cms_transform_all_fuzzer', 'cms_overwrite_transform_fuzzer', 'cms_postscript_fuzzer', 'cms_universal_transform_fuzzer']

Directories in report

Directory
/src/lcms/src/
/src/
/src/lcms/src/./