Fuzz introspector
For issues and ideas: https://github.com/ossf/fuzz-introspector/issues

Fuzzers overview

Fuzzer Fuzzer filename Functions Reached Functions unreached Fuzzer depth Files reached Basic blocks reached Cyclomatic complexity Details
cms_gdb_fuzzer cms_gdb_fuzzer.c 35 1039 8 6 250 126 cms_gdb_fuzzer.c
cms_dict_fuzzer cms_dict_fuzzer.c 90 971 9 12 866 379 cms_dict_fuzzer.c
cms_md5_fuzzer cms_md5_fuzzer.c 72 992 10 8 648 299 cms_md5_fuzzer.c
cms_profile_fuzzer cms_profile_fuzzer.c 87 975 10 9 894 402 cms_profile_fuzzer.c
cms_cie_cam02_fuzzer cms_cie_cam02_fuzzer.c 87 992 9 12 721 322 cms_cie_cam02_fuzzer.c
cms_cgats_fuzzer cms_cgats_fuzzer.c 157 1011 9 12 1790 776 cms_cgats_fuzzer.c
cms_transform_all_fuzzer cms_transform_all_fuzzer.c 250 810 16 20 3247 1456 cms_transform_all_fuzzer.c
cmsIT8_load_fuzzer cmsIT8_load_fuzzer.c 92 1077 9 5 1086 485 cmsIT8_load_fuzzer.c
cms_transform_fuzzer cms_transform_fuzzer.c 252 807 12 20 3273 1467 cms_transform_fuzzer.c
cms_universal_transform_fuzzer cms_universal_transform_fuzzer.c 249 810 15 20 3242 1453 cms_universal_transform_fuzzer.c
cms_devicelink_fuzzer cms_devicelink_fuzzer.c 134 925 9 14 1491 670 cms_devicelink_fuzzer.c
cms_transform_extended_fuzzer cms_transform_extended_fuzzer.c 335 725 12 20 4126 1838 cms_transform_extended_fuzzer.c
cms_virtual_profile_fuzzer cms_virtual_profile_fuzzer.c 273 786 12 20 3599 1608 cms_virtual_profile_fuzzer.c
cms_postscript_fuzzer cms_postscript_fuzzer.c 375 717 16 22 4693 2077 cms_postscript_fuzzer.c
cms_overwrite_transform_fuzzer cms_overwrite_transform_fuzzer.c 249 810 15 20 3242 1453 cms_overwrite_transform_fuzzer.c

Project functions overview

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 details

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_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 107 47.1%
gold [1:9] 2 0.88%
yellow [10:29] 0 0.0%
greenyellow [30:49] 0 0.0%
lawngreen 50+ 118 51.9%
All colors 227 100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked Calltree index Parent function Callsite Largest blocked function
53 27 _cmsFree call site: 00027 cmsDeleteContext
16 143 cmsCreateContext call site: 00143 cmsDeleteContext
5 127 cmsCreateContext call site: 00127 DupPluginOptimizationList
4 6 _cmsMalloc call site: 00006 cmsSignalError
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 174 cmsMLUsetWide call site: 00174 GrowMLUtable
1 25 _cmsCreateSubAllocChunk call site: 00025 _cmsFree

Runtime coverage analysis

Covered functions
63
Functions that are reachable but not covered
33
Reachable functions
90
Percentage of reachable functions covered
63.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.
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_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 66 30.2%
gold [1:9] 1 0.45%
yellow [10:29] 1 0.45%
greenyellow [30:49] 1 0.45%
lawngreen 50+ 149 68.3%
All colors 218 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 81 cmsOpenProfileFromMemTHR call site: 00081 cmsSaveProfileToFile
12 164 _cmsWriteAlignment call site: 00164 _cmsGetTagTypeHandler
6 10 _cmsContextGetClientChunk call site: 00010 _cmsEnterCriticalSectionPrimitive
4 34 cmsOpenIOhandlerFromMem call site: 00034 _cmsFree
4 183 cmsSaveProfileToIOhandler call site: 00183 _cmsUnlockMutex
3 30 _cmsMalloc call site: 00030 _cmsFree
2 115 cmsOpenIOhandlerFromNULL call site: 00115 _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
1 27 cmsOpenIOhandlerFromMem call site: 00027 cmsSignalError

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_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 42 14.6%
gold [1:9] 0 0.0%
yellow [10:29] 3 1.04%
greenyellow [30:49] 3 1.04%
lawngreen 50+ 239 83.2%
All colors 287 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 223 cmsOpenIOhandlerFromMem call site: 00223 _cmsFree
4 32 cmsOpenIOhandlerFromFile call site: 00032 _cmsFree
4 230 cmsOpenIOhandlerFromMem call site: 00230 _cmsFree
3 44 cmsfilelength call site: 00044 _cmsFree
3 48 cmsOpenIOhandlerFromFile call site: 00048 _cmsFree
2 37 cmsOpenIOhandlerFromFile call site: 00037 _cmsFree
2 106 cmsOpenIOhandlerFromNULL call site: 00106 _cmsFree
2 211 cmsReadTag call site: 00211 cmsSignalError
2 273 _cmsDeleteTagByPos call site: 00273 _cmsUnlockMutex
1 6 LLVMFuzzerTestOneInput call site: 00006 cmsOpenProfileFromFileTHR
1 10 _cmsMallocZero call site: 00010 cmsSignalError

Runtime coverage analysis

Covered functions
223
Functions that are reachable but not covered
19
Reachable functions
87
Percentage of reachable functions covered
78.16%
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 3
lcmscmswtpnt.c 1
lcmscmsio1.c 2
lcmscmsnamed.c 3

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 81 35.2%
gold [1:9] 5 2.17%
yellow [10:29] 130 56.5%
greenyellow [30:49] 2 0.86%
lawngreen 50+ 12 5.21%
All colors 230 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 143 cmsCreateContext call site: 00143 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: 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 231 41.0%
gold [1:9] 1 0.17%
yellow [10:29] 0 0.0%
greenyellow [30:49] 3 0.53%
lawngreen 50+ 328 58.2%
All colors 563 100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked Calltree index Parent function Callsite Largest blocked function
53 27 _cmsFree call site: 00027 cmsDeleteContext
20 417 InStringSymbol call site: 00417 InSymbol
16 143 cmsCreateContext call site: 00143 cmsDeleteContext
12 393 InSymbol call site: 00393 StringCat
12 478 DataSection call site: 00478 SkipEOLN
10 507 HeaderSection call site: 00507 AddToList
8 491 ParseIT8 call site: 00491 InSymbol
6 384 ReadReal call site: 00384 NextCh
5 127 cmsCreateContext call site: 00127 DupPluginOptimizationList
5 286 WriteHeader call site: 00286 Writef
4 96 _cmsAllocCurvesPluginChunk call site: 00096 DupPluginCurvesList
4 103 _cmsAllocFormattersPluginChunk call site: 00103 DupFormatterFactoryList

Runtime coverage analysis

Covered functions
109
Functions that are reachable but not covered
52
Reachable functions
157
Percentage of reachable functions covered
66.88%
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
lcmscmsplugin.c 10
lcmscmserr.c 18
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
lcmscmscgats.c 76

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 262 31.8%
gold [1:9] 9 1.09%
yellow [10:29] 6 0.72%
greenyellow [30:49] 15 1.82%
lawngreen 50+ 531 64.5%
All colors 823 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
29 592 cmsCreateRGBProfileTHR call site: 00592 cmsCloseProfile
25 794 _cmsCompileProfileSequence call site: 00794 cmsCreateTransformTHR
8 31 _cmsMalloc call site: 00031 _cmsFree
8 180 _cmsSearchTag call site: 00180 SaveTags
6 11 _cmsContextGetClientChunk call site: 00011 _cmsEnterCriticalSectionPrimitive
6 112 _cmsLockMutex call site: 00112 cmsOpenIOhandlerFromNULL
6 161 cmsGetProfileVersion call site: 00161 _cmsGetTagTypeHandler
6 427 AllocateToneCurveStruct call site: 00427 _cmsFree
6 564 cmsWriteTag call site: 00564 cmsSignalError
6 750 cmsIsMatrixShaper call site: 00750 cmsCreateExtendedTransform

Runtime coverage analysis

Covered functions
422
Functions that are reachable but not covered
41
Reachable functions
250
Percentage of reachable functions covered
83.6%
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 3
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: 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.5%
gold [1:9] 10 2.84%
yellow [10:29] 9 2.56%
greenyellow [30:49] 1 0.28%
lawngreen 50+ 273 77.7%
All colors 351 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 264 HeaderSection call site: 00264 AddToList
7 316 WriteHeader call site: 00316 Writef
6 12 _cmsContextGetClientChunk call site: 00012 _cmsEnterCriticalSectionPrimitive
4 252 HeaderSection call site: 00252 InSymbol
3 293 cmsIT8SaveToFile call site: 00293 SynError
2 302 WriteStr call site: 00302 cmsSignalError
2 305 WriteHeader call site: 00305 Writef
2 309 Writef call site: 00309 WriteStr
1 7 _cmsMallocZero call site: 00007 cmsSignalError
1 10 cmsSignalError call site: 00010 __assert_fail
1 23 AllocBigBlock call site: 00023 _cmsFree
1 32 cmsIT8SetSheetType call site: 00032 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 370 44.3%
gold [1:9] 11 1.31%
yellow [10:29] 9 1.07%
greenyellow [30:49] 3 0.35%
lawngreen 50+ 441 52.8%
All colors 834 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 118 _cmsUnlockMutex call site: 00118 SaveTags
29 81 cmsOpenProfileFromMemTHR call site: 00081 cmsSaveProfileToFile
28 800 cmsMLUdup call site: 00800 cmsCreateTransformTHR
20 730 cmsCreateExtendedTransform call site: 00730 _cmsCreateGamutCheckPipeline
17 520 OptimizeByResampling call site: 00520 PrelinOpt16alloc
15 783 cmsCreateExtendedTransform call site: 00783 _cmsCompileProfileSequence
10 677 cmsDoTransform call site: 00677 cmsCloseProfile
9 558 cmsReverseToneCurveEx call site: 00558 cmsBuildTabulatedToneCurve16
9 629 cmsD50_xyY call site: 00629 cmsCreateRGBProfileTHR
9 666 cmsStageAllocToneCurves call site: 00666 cmsCreateTransformTHR
8 30 _cmsMalloc call site: 00030 _cmsFree
8 179 _cmsSearchTag call site: 00179 SaveTags

Runtime coverage analysis

Covered functions
365
Functions that are reachable but not covered
63
Reachable functions
252
Percentage of reachable functions covered
75.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_transform_fuzzer.c 1
lcmscmsio0.c 43
lcmscmserr.c 13
lcmscmsplugin.c 15
lcms./lcms2_internal.h 5
lcmscmstypes.c 3
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_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 374 45.4%
gold [1:9] 7 0.85%
yellow [10:29] 6 0.72%
greenyellow [30:49] 16 1.94%
lawngreen 50+ 419 50.9%
All colors 822 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 118 _cmsUnlockMutex call site: 00118 SaveTags
37 591 cmsCreateRGBProfileTHR call site: 00591 _cmsStageAllocIdentityCurves
29 81 cmsOpenProfileFromMemTHR call site: 00081 cmsSaveProfileToFile
28 790 cmsMLUdup call site: 00790 cmsCreateTransformTHR
20 720 cmsCreateExtendedTransform call site: 00720 _cmsCreateGamutCheckPipeline
17 366 OptimizeByResampling call site: 00366 PrelinOpt16alloc
13 775 cmsCreateExtendedTransform call site: 00775 _cmsCompileProfileSequence
10 667 cmsDoTransform call site: 00667 cmsCloseProfile
9 656 cmsStageAllocToneCurves call site: 00656 cmsCreateTransformTHR
8 30 _cmsMalloc call site: 00030 _cmsFree
8 179 _cmsSearchTag call site: 00179 SaveTags
6 10 _cmsContextGetClientChunk call site: 00010 _cmsEnterCriticalSectionPrimitive

Runtime coverage analysis

Covered functions
348
Functions that are reachable but not covered
60
Reachable functions
249
Percentage of reachable functions covered
75.9%
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 3
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_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 189 51.2%
gold [1:9] 3 0.81%
yellow [10:29] 0 0.0%
greenyellow [30:49] 68 18.4%
lawngreen 50+ 109 29.5%
All colors 369 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 258 cmsPipelineFree call site: 00258 cmsCloseProfile
22 339 _cmsMalloc call site: 00339 SaveTags
8 123 AllocateToneCurveStruct call site: 00123 cmsFreeToneCurve
7 96 cmsStageAllocToneCurves call site: 00096 cmsEvalToneCurveFloat
6 8 _cmsContextGetClientChunk call site: 00008 _cmsEnterCriticalSectionPrimitive
6 215 _cmsGetTagTypeHandler call site: 00215 cmsSignalError
5 192 _cmsSearchTag call site: 00192 _cmsDeleteTagByPos
4 46 cmsStageAllocCLut16bitGranular call site: 00046 FromFloatTo16
4 64 _cmsSetInterpolationRoutine call site: 00064 _cmsFree
4 208 cmsWriteTag call site: 00208 cmsSignalError
4 240 cmsMLUsetASCII call site: 00240 AddMLUBlock
2 1 LLVMFuzzerTestOneInput call site: 00001 cmsCreateInkLimitingDeviceLinkTHR

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 388 33.8%
gold [1:9] 22 1.92%
yellow [10:29] 9 0.78%
greenyellow [30:49] 8 0.69%
lawngreen 50+ 718 62.7%
All colors 1145 100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked Calltree index Parent function Callsite Largest blocked function
53 663 _cmsCreateSubAllocChunk call site: 00663 cmsDeleteContext
41 119 _cmsUnlockMutex call site: 00119 SaveTags
29 82 cmsOpenProfileFromMemTHR call site: 00082 cmsSaveProfileToFile
25 1111 _cmsCompileProfileSequence call site: 01111 cmsCreateTransformTHR
15 779 cmsCreateContext call site: 00779 cmsDeleteContext
10 1001 cmsDoTransform call site: 01001 cmsCloseProfile
8 31 _cmsMalloc call site: 00031 _cmsFree
8 180 _cmsSearchTag call site: 00180 SaveTags
8 991 cmsCreateExtendedTransform call site: 00991 cmsDetectRGBProfileGamma
7 363 AllocateToneCurveStruct call site: 00363 cmsFreeToneCurve
7 583 run_test call site: 00583 cmsCreateBCHSWabstractProfileTHR
6 112 _cmsLockMutex call site: 00112 cmsOpenIOhandlerFromNULL

Runtime coverage analysis

Covered functions
475
Functions that are reachable but not covered
66
Reachable functions
335
Percentage of reachable functions covered
80.3%
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 12
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_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 346 35.8%
gold [1:9] 13 1.34%
yellow [10:29] 20 2.07%
greenyellow [30:49] 7 0.72%
lawngreen 50+ 579 60.0%
All colors 965 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 118 _cmsUnlockMutex call site: 00118 SaveTags
29 81 cmsOpenProfileFromMemTHR call site: 00081 cmsSaveProfileToFile
28 800 cmsMLUdup call site: 00800 cmsCreateTransformTHR
20 730 cmsCreateExtendedTransform call site: 00730 _cmsCreateGamutCheckPipeline
12 880 cmsTransform2DeviceLink call site: 00880 IsPCS
10 677 cmsDoTransform call site: 00677 cmsCloseProfile
9 666 cmsStageAllocToneCurves call site: 00666 cmsCreateTransformTHR
9 789 cmsAllocProfileSequenceDescription call site: 00789 GetMLUFromProfile
8 30 _cmsMalloc call site: 00030 _cmsFree
8 179 _cmsSearchTag call site: 00179 SaveTags
8 629 cmsD50_xyY call site: 00629 cmsCreateRGBProfileTHR
6 10 _cmsContextGetClientChunk call site: 00010 _cmsEnterCriticalSectionPrimitive

Runtime coverage analysis

Covered functions
411
Functions that are reachable but not covered
52
Reachable functions
273
Percentage of reachable functions covered
80.95%
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 3
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_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 394 27.4%
gold [1:9] 22 1.53%
yellow [10:29] 19 1.32%
greenyellow [30:49] 16 1.11%
lawngreen 50+ 983 68.5%
All colors 1434 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 263 _cmsUnlockMutex call site: 00263 SaveTags
29 226 cmsOpenProfileFromMemTHR call site: 00226 cmsSaveProfileToFile
29 430 cmsCreateRGBProfileTHR call site: 00430 cmsCloseProfile
28 940 cmsMLUdup call site: 00940 cmsCreateTransformTHR
16 143 cmsCreateContext call site: 00143 cmsDeleteContext
13 925 cmsCreateExtendedTransform call site: 00925 _cmsCompileProfileSequence
9 602 _MultiplyMatrix call site: 00602 _RemoveElement
8 175 cmsOpenIOhandlerFromMem call site: 00175 _cmsFree
8 324 _cmsSearchTag call site: 00324 SaveTags
7 513 AllocateToneCurveStruct call site: 00513 cmsFreeToneCurve
6 39 RegisterTypesPlugin call site: 00039 _cmsPluginMalloc
6 305 cmsGetProfileVersion call site: 00305 _cmsGetTagTypeHandler

Runtime coverage analysis

Covered functions
465
Functions that are reachable but not covered
63
Reachable functions
375
Percentage of reachable functions covered
83.2%
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 12
lcmscmspack.c 8
lcmscmscnvrt.c 5
lcmscmsgamma.c 23
lcmscmsopt.c 22
lcmscmsxform.c 21
lcmscmsio0.c 45
lcmscmswtpnt.c 6
lcmscmsps2.c 31
lcmscmsvirt.c 6
lcmscmspcs.c 14
lcmscmsnamed.c 24
lcmscmsmtrx.c 5
lcmscmslut.c 53
lcmscmsgmt.c 3
lcmscmsio1.c 11
lcmscmssamp.c 4

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 374 45.4%
gold [1:9] 8 0.97%
yellow [10:29] 8 0.97%
greenyellow [30:49] 13 1.58%
lawngreen 50+ 419 50.9%
All colors 822 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 118 _cmsUnlockMutex call site: 00118 SaveTags
37 591 cmsCreateRGBProfileTHR call site: 00591 _cmsStageAllocIdentityCurves
29 81 cmsOpenProfileFromMemTHR call site: 00081 cmsSaveProfileToFile
28 790 cmsMLUdup call site: 00790 cmsCreateTransformTHR
20 720 cmsCreateExtendedTransform call site: 00720 _cmsCreateGamutCheckPipeline
17 366 OptimizeByResampling call site: 00366 PrelinOpt16alloc
13 775 cmsCreateExtendedTransform call site: 00775 _cmsCompileProfileSequence
10 667 cmsDoTransform call site: 00667 cmsCloseProfile
9 656 cmsStageAllocToneCurves call site: 00656 cmsCreateTransformTHR
8 30 _cmsMalloc call site: 00030 _cmsFree
8 179 _cmsSearchTag call site: 00179 SaveTags
6 10 _cmsContextGetClientChunk call site: 00010 _cmsEnterCriticalSectionPrimitive

Runtime coverage analysis

Covered functions
348
Functions that are reachable but not covered
60
Reachable functions
249
Percentage of reachable functions covered
75.9%
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 3
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

Analyses and suggestions

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 427 69 27 317 0 1972 408
Type_Dictionary_Read /src/lcms/src/cmstypes.c 4 ['N/A', 'N/A', 'N/A', 'int'] 10 0 379 67 27 42 0 212 127
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 868 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'] 14 0 15 3 2 140 0 678 74
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
56.9%
686 / 1198
Cyclomatic complexity statically reachable by fuzzers
63.0%
4247 / 6753

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

Fuzz engine guidance

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

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', 'LLVMFuzzerTestOneInput', '_cmsMallocZero', 'cmsSignalError']

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', 'cmsReadTag', '_cmsDeleteTagByPos']

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

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=['_cmsFree', 'InStringSymbol', 'cmsCreateContext', 'InSymbol', 'DataSection', 'HeaderSection', 'ParseIT8', 'ReadReal', 'WriteHeader']

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', '_cmsSearchTag', '_cmsContextGetClientChunk', '_cmsLockMutex', 'cmsGetProfileVersion', 'AllocateToneCurveStruct']

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

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

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', '_cmsSearchTag', 'AllocateToneCurveStruct']

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

Files and Directories in report

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/cmsio0.c ['cms_md5_fuzzer', 'cms_profile_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_md5_fuzzer', 'cms_profile_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/cms_universal_transform_fuzzer.c ['cms_universal_transform_fuzzer'] ['cms_universal_transform_fuzzer']
/src/cms_transform_fuzzer.c ['cms_transform_fuzzer'] ['cms_transform_fuzzer']
/src/cms_postscript_fuzzer.c ['cms_postscript_fuzzer'] ['cms_postscript_fuzzer']
/src/lcms/src/cmsgamma.c ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/cms_md5_fuzzer.c ['cms_md5_fuzzer'] ['cms_md5_fuzzer']
/src/cms_overwrite_transform_fuzzer.c ['cms_overwrite_transform_fuzzer'] ['cms_overwrite_transform_fuzzer']
/src/lcms/src/cmsmtrx.c ['cms_gdb_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_gdb_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/lcms/src/cmsps2.c ['cms_postscript_fuzzer'] ['cms_postscript_fuzzer']
/src/lcms/src/cmswtpnt.c ['cms_md5_fuzzer', 'cms_profile_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_md5_fuzzer', 'cms_profile_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/lcms/src/cmsintrp.c ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/lcms/src/cmsmd5.c ['cms_md5_fuzzer'] ['cms_md5_fuzzer']
/src/lcms/src/cmspcs.c ['cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/cms_gdb_fuzzer.c ['cms_gdb_fuzzer'] ['cms_gdb_fuzzer']
/src/lcms/src/cmsopt.c ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/lcms/src/cmslut.c ['cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/lcms/src/cmshalf.c [] []
/src/cms_profile_fuzzer.c ['cms_profile_fuzzer'] ['cms_profile_fuzzer']
/src/cms_cie_cam02_fuzzer.c ['cms_cie_cam02_fuzzer'] ['cms_cie_cam02_fuzzer']
/src/lcms/src/cmsxform.c ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/lcms/src/cmstypes.c ['cms_dict_fuzzer', 'cms_md5_fuzzer', 'cms_profile_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_dict_fuzzer', 'cms_md5_fuzzer', 'cms_profile_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/lcms/src/cmsvirt.c ['cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/lcms/src/cmssm.c ['cms_gdb_fuzzer'] ['cms_gdb_fuzzer']
/src/cms_cgats_fuzzer.c ['cms_cgats_fuzzer'] ['cms_cgats_fuzzer']
/src/cms_virtual_profile_fuzzer.c ['cms_virtual_profile_fuzzer'] ['cms_virtual_profile_fuzzer']
/src/lcms/src/cmsnamed.c ['cms_dict_fuzzer', 'cms_profile_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_dict_fuzzer', 'cms_profile_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/cms_transform_all_fuzzer.c ['cms_transform_all_fuzzer'] ['cms_transform_all_fuzzer']
/src/lcms/src/cmsalpha.c [] []
/src/cms_dict_fuzzer.c ['cms_dict_fuzzer'] ['cms_dict_fuzzer']
/src/lcms/src/cmspack.c ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/lcms/src/cmscam02.c ['cms_cie_cam02_fuzzer'] ['cms_cie_cam02_fuzzer']
/src/lcms/src/cmsplugin.c ['cms_gdb_fuzzer', 'cms_dict_fuzzer', 'cms_md5_fuzzer', 'cms_profile_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cmsIT8_load_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_gdb_fuzzer', 'cms_dict_fuzzer', 'cms_md5_fuzzer', 'cms_profile_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cmsIT8_load_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/lcms/src/./lcms2_internal.h ['cms_gdb_fuzzer', 'cms_dict_fuzzer', 'cms_md5_fuzzer', 'cms_profile_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cmsIT8_load_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] []
/src/lcms/src/cmscnvrt.c ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_dict_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/cmsIT8_load_fuzzer.c ['cmsIT8_load_fuzzer'] ['cmsIT8_load_fuzzer']
/src/lcms/src/cmserr.c ['cms_gdb_fuzzer', 'cms_dict_fuzzer', 'cms_md5_fuzzer', 'cms_profile_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cmsIT8_load_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_gdb_fuzzer', 'cms_dict_fuzzer', 'cms_md5_fuzzer', 'cms_profile_fuzzer', 'cms_cie_cam02_fuzzer', 'cms_cgats_fuzzer', 'cms_transform_all_fuzzer', 'cmsIT8_load_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']
/src/cms_devicelink_fuzzer.c ['cms_devicelink_fuzzer'] ['cms_devicelink_fuzzer']
/src/lcms/src/cmsgmt.c ['cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_transform_all_fuzzer', 'cms_transform_extended_fuzzer', 'cms_postscript_fuzzer']
/src/lcms/src/cmscgats.c ['cms_cgats_fuzzer', 'cmsIT8_load_fuzzer'] ['cms_cgats_fuzzer', 'cmsIT8_load_fuzzer']
/src/cms_transform_extended_fuzzer.c ['cms_transform_extended_fuzzer'] ['cms_transform_extended_fuzzer']
/src/lcms/src/cmssamp.c ['cms_postscript_fuzzer'] ['cms_postscript_fuzzer']
/src/lcms/src/cmsio1.c ['cms_profile_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer'] ['cms_profile_fuzzer', 'cms_transform_all_fuzzer', 'cms_transform_fuzzer', 'cms_universal_transform_fuzzer', 'cms_devicelink_fuzzer', 'cms_transform_extended_fuzzer', 'cms_virtual_profile_fuzzer', 'cms_postscript_fuzzer', 'cms_overwrite_transform_fuzzer']

Directories in report

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

Metadata section

This sections shows the raw data that is used to produce this report. This is mainly used for further processing and developer debugging.

Fuzzer Calltree file Program data file Coverage file
cms_gdb_fuzzer fuzzerLogFile-0-mS9Vq4wVE9.data fuzzerLogFile-0-mS9Vq4wVE9.data.yaml cms_gdb_fuzzer.covreport
cms_dict_fuzzer fuzzerLogFile-0-3KJJHs9NQD.data fuzzerLogFile-0-3KJJHs9NQD.data.yaml cms_dict_fuzzer.covreport
cms_md5_fuzzer fuzzerLogFile-0-u6hoXhPAvE.data fuzzerLogFile-0-u6hoXhPAvE.data.yaml cms_md5_fuzzer.covreport
cms_profile_fuzzer fuzzerLogFile-0-3qMGr7O2td.data fuzzerLogFile-0-3qMGr7O2td.data.yaml cms_profile_fuzzer.covreport
cms_cie_cam02_fuzzer fuzzerLogFile-0-sEaKr4EUm7.data fuzzerLogFile-0-sEaKr4EUm7.data.yaml cms_cie_cam02_fuzzer.covreport
cms_cgats_fuzzer fuzzerLogFile-0-iKexjopOVQ.data fuzzerLogFile-0-iKexjopOVQ.data.yaml cms_cgats_fuzzer.covreport
cms_transform_all_fuzzer fuzzerLogFile-0-jjqVLTpMVy.data fuzzerLogFile-0-jjqVLTpMVy.data.yaml cms_transform_all_fuzzer.covreport
cmsIT8_load_fuzzer fuzzerLogFile-0-ghvij1WvtL.data fuzzerLogFile-0-ghvij1WvtL.data.yaml cmsIT8_load_fuzzer.covreport
cms_transform_fuzzer fuzzerLogFile-0-fJSHGJO85C.data fuzzerLogFile-0-fJSHGJO85C.data.yaml cms_transform_fuzzer.covreport
cms_universal_transform_fuzzer fuzzerLogFile-0-SV8oHqPLwc.data fuzzerLogFile-0-SV8oHqPLwc.data.yaml cms_universal_transform_fuzzer.covreport
cms_devicelink_fuzzer fuzzerLogFile-0-Lf2Kmfv4kU.data fuzzerLogFile-0-Lf2Kmfv4kU.data.yaml cms_devicelink_fuzzer.covreport
cms_transform_extended_fuzzer fuzzerLogFile-0-cHKPRPtlcD.data fuzzerLogFile-0-cHKPRPtlcD.data.yaml cms_transform_extended_fuzzer.covreport
cms_virtual_profile_fuzzer fuzzerLogFile-0-C51jLFQhkY.data fuzzerLogFile-0-C51jLFQhkY.data.yaml cms_virtual_profile_fuzzer.covreport
cms_postscript_fuzzer fuzzerLogFile-0-3TYFxG4TFU.data fuzzerLogFile-0-3TYFxG4TFU.data.yaml cms_postscript_fuzzer.covreport
cms_overwrite_transform_fuzzer fuzzerLogFile-0-rHIqFCjIo1.data fuzzerLogFile-0-rHIqFCjIo1.data.yaml cms_overwrite_transform_fuzzer.covreport