High level conclusions

Fuzzers reach 88.47% of cyclomatic complexity.

Fuzzers reach 86.68% of all functions.

Fuzzers reach 84.64% code coverage.

Reachability and coverage overview

Functions statically reachable by fuzzers

254 / 293

Cyclomatic complexity statically reachable by fuzzers

1413 / 1597

Runtime code coverage of functions

248 / 293

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

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	28	100.%
All colors	28	100

Runtime coverage analysis

Covered functions

7

Functions that are reachable but not covered

2

Reachable functions

9

Percentage of reachable functions covered

77.78%

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
apps/fuzzers/fuzzerInternalCoordIjk.c	1
h3lib/include/coordijk.h	4
h3lib/include/mathExtensions.h	2

Fuzzer: fuzzerCellToChildPos

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	24	100.%
All colors	24	100

Runtime coverage analysis

Covered functions

11

Functions that are reachable but not covered

1

Reachable functions

12

Percentage of reachable functions covered

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerCellToChildPos.c	1
h3lib/lib/h3Index.c	8
h3lib/lib/baseCells.c	1
h3lib/lib/mathExtensions.c	1

Fuzzer: fuzzerHierarchy

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	1	3.57%
yellow	[10:29]	1	3.57%
greenyellow	[30:49]	2	7.14%
lawngreen	50+	24	85.7%
All colors	28	100

Runtime coverage analysis

Covered functions

18

Functions that are reachable but not covered

1

Reachable functions

19

Percentage of reachable functions covered

94.74%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerHierarchy.c	1
h3lib/lib/h3Index.c	9
h3lib/lib/baseCells.c	1
h3lib/lib/mathExtensions.c	1
h3lib/lib/iterators.c	6

Fuzzer: fuzzerDistances

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	4	36.3%
greenyellow	[30:49]	1	9.09%
lawngreen	50+	6	54.5%
All colors	11	100

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

4

Reachable functions

8

Percentage of reachable functions covered

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerDistances.c	1
h3lib/lib/latLng.c	3

Fuzzer: fuzzerResolutions

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	1	10.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	9	90.0%
All colors	10	100

Runtime coverage analysis

Covered functions

10

Functions that are reachable but not covered

0

Reachable functions

10

Percentage of reachable functions covered

100.0%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerResolutions.c	1
h3lib/lib/latLng.c	5
h3lib/lib/mathExtensions.c	1
h3lib/lib/h3Index.c	2
h3lib/lib/baseCells.c	1

Fuzzer: fuzzerCellProperties

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2	1.17%
gold	[1:9]	1	0.58%
yellow	[10:29]	17	10.0%
greenyellow	[30:49]	2	1.17%
lawngreen	50+	148	87.0%
All colors	170	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1	88	cellToVertex	call site: 00088	_rotate60ccw
1	99	h3NeighborRotations	call site: 00099	_h3Rotate60ccw

Runtime coverage analysis

Covered functions

56

Functions that are reachable but not covered

3

Reachable functions

59

Percentage of reachable functions covered

94.92%

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
apps/fuzzers/fuzzerCellProperties.c	1
h3lib/lib/h3Index.c	22
h3lib/lib/directedEdge.c	2
h3lib/lib/baseCells.c	5
h3lib/lib/vertex.c	5
h3lib/include/coordijk.h	15
h3lib/lib/faceijk.c	4
h3lib/lib/algos.c	2

Fuzzer: fuzzerConstructCell

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	1	20.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	80.0%
All colors	5	100

Runtime coverage analysis

Covered functions

2

Functions that are reachable but not covered

1

Reachable functions

3

Percentage of reachable functions covered

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerConstructCell.c	1
h3lib/lib/h3Index.c	1

Fuzzer: fuzzerCellToLatLng

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	8	5.12%
greenyellow	[30:49]	2	1.28%
lawngreen	50+	146	93.5%
All colors	156	100

Runtime coverage analysis

Covered functions

46

Functions that are reachable but not covered

7

Reachable functions

53

Percentage of reachable functions covered

86.79%

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
apps/fuzzers/fuzzerCellToLatLng.c	1
h3lib/lib/h3Index.c	9
h3lib/lib/baseCells.c	1
h3lib/include/coordijk.h	15
h3lib/lib/faceijk.c	9
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	1
h3lib/include/vec3d.h	7

Fuzzer: fuzzerVertexes

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	21	10.0%
gold	[1:9]	1	0.47%
yellow	[10:29]	11	5.23%
greenyellow	[30:49]	1	0.47%
lawngreen	50+	176	83.8%
All colors	210	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
9	138	_faceIjkPentToCellBoundary	call site: 00138	_hex2dToVec3
8	190	_faceIjkToCellBoundary	call site: 00190	_hex2dToVec3
1	73	cellToVertex	call site: 00073	_rotate60ccw
1	84	h3NeighborRotations	call site: 00084	_h3Rotate60ccw
1	154	_hex2dToVec3	call site: 00154	_posAngleRads
1	172	_hex2dToVec3	call site: 00172	vec3ToLatLng

Runtime coverage analysis

Covered functions

63

Functions that are reachable but not covered

9

Reachable functions

72

Percentage of reachable functions covered

87.5%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerVertexes.c	1
h3lib/lib/vertex.c	7
h3lib/lib/h3Index.c	15
h3lib/lib/baseCells.c	5
h3lib/include/coordijk.h	16
h3lib/lib/faceijk.c	8
h3lib/lib/algos.c	2
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	1
h3lib/include/vec3d.h	7

Fuzzer: fuzzerDirectedEdge

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	5	2.16%
gold	[1:9]	3	1.29%
yellow	[10:29]	16	6.92%
greenyellow	[30:49]	6	2.59%
lawngreen	50+	201	87.0%
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
2	38	gridDiskDistances	call site: 00038	getNumCells
1	23	_h3Rotate60cw	call site: 00023	_h3Rotate60ccw
1	44	_gridDiskDistancesInternal	call site: 00044	_gridDiskDistancesInternal
1	183	_hex2dToVec3	call site: 00183	_posAngleRads

Runtime coverage analysis

Covered functions

75

Functions that are reachable but not covered

10

Reachable functions

85

Percentage of reachable functions covered

88.24%

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
apps/fuzzers/fuzzerDirectedEdge.c	1
h3lib/lib/directedEdge.c	9
h3lib/lib/h3Index.c	16
h3lib/lib/baseCells.c	5
h3lib/lib/algos.c	7
h3lib/include/coordijk.h	16
h3lib/lib/latLng.c	2
h3lib/lib/mathExtensions.c	1
h3lib/lib/vertex.c	2
h3lib/lib/faceijk.c	8
h3lib/lib/vec2d.c	3
h3lib/include/vec3d.h	7

Fuzzer: fuzzerGridDisk

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	1	1.28%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	2.56%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	75	96.1%
All colors	78	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1	23	_h3Rotate60cw	call site: 00023	_h3Rotate60ccw

Runtime coverage analysis

Covered functions

27

Functions that are reachable but not covered

2

Reachable functions

29

Percentage of reachable functions covered

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerGridDisk.c	1
h3lib/lib/algos.c	13
h3lib/lib/latLng.c	1
h3lib/lib/mathExtensions.c	1
h3lib/lib/h3Index.c	6
h3lib/lib/baseCells.c	3
h3lib/include/coordijk.h	2

Fuzzer: fuzzerInternalAlgos

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	1	3.33%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	6.66%
greenyellow	[30:49]	5	16.6%
lawngreen	50+	22	73.3%
All colors	30	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1	13	_h3Rotate60cw	call site: 00013	_h3Rotate60ccw

Runtime coverage analysis

Covered functions

14

Functions that are reachable but not covered

1

Reachable functions

15

Percentage of reachable functions covered

93.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
apps/fuzzers/fuzzerInternalAlgos.c	1
h3lib/lib/algos.c	2
h3lib/include/coordijk.h	2
h3lib/lib/h3Index.c	6
h3lib/lib/baseCells.c	3

Fuzzer: fuzzerPolygonToCellsExperimental

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	14	4.10%
gold	[1:9]	3	0.87%
yellow	[10:29]	1	0.29%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	323	94.7%
All colors	341	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
3	178	_faceIjkToH3	call site: 00178	_h3Rotate60cw
2	8	baseCellNumToCell	call site: 00008	iterErrorPolygonCompact
1	11	_iterInitPolygonCompact	call site: 00011	iterErrorPolygonCompact
1	13	_iterInitPolygonCompact	call site: 00013	iterErrorPolygonCompact
1	121	vec3ToLatLng	call site: 00121	iterErrorPolygonCompact
1	189	iterStepPolygonCompact	call site: 00189	iterErrorPolygonCompact
1	252	_faceIjkToCellBoundary	call site: 00252	iterErrorPolygonCompact
1	261	iterStepPolygonCompact	call site: 00261	iterErrorPolygonCompact
1	286	iterStepPolygonCompact	call site: 00286	iterErrorPolygonCompact
1	298	iterStepPolygonCompact	call site: 00298	iterErrorPolygonCompact
1	306	cellToCenterChild	call site: 00306	iterErrorPolygonCompact

Runtime coverage analysis

Covered functions

111

Functions that are reachable but not covered

12

Reachable functions

123

Percentage of reachable functions covered

90.24%

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
apps/fuzzers/fuzzerPolygonToCellsExperimental.c	3
h3lib/lib/polyfill.c	14
h3lib/lib/h3Index.c	19
h3lib/lib/polygon.c	7
h3lib/include/polygonAlgos.h	2
h3lib/lib/bbox.c	9
h3lib/lib/latLng.c	3
h3lib/lib/baseCells.c	4
h3lib/include/coordijk.h	20
h3lib/lib/faceijk.c	13
h3lib/lib/vec2d.c	3
h3lib/include/vec3d.h	9
h3lib/lib/mathExtensions.c	1
h3lib/lib/iterators.c	6

Fuzzer: fuzzerCellsToMultiPolygon

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	19	6.98%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	253	93.0%
All colors	272	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	251	cellsToMultiPolygon	call site: 00251	createGlobeMultiPolygon
3	262	createMultiPolygon	call site: 00262	destroySortableLoopSet
2	245	geoLoopAreaRads2	call site: 00245	destroySortableLoopSet
1	19	createArcSet	call site: 00019	destroyArcSet
1	25	createArcSet	call site: 00025	destroyArcSet
1	33	getDirectedEdgeDestination	call site: 00033	_rotate60ccw
1	45	_h3Rotate60cw	call site: 00045	_h3Rotate60ccw
1	68	cellsToMultiPolygon	call site: 00068	destroyArcSet
1	186	_hex2dToVec3	call site: 00186	_posAngleRads
1	249	createSortableLoopSet	call site: 00249	destroyArcSet
1	259	createMultiPolygon	call site: 00259	destroySortablePolys

Runtime coverage analysis

Covered functions

96

Functions that are reachable but not covered

14

Reachable functions

110

Percentage of reachable functions covered

87.27%

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
apps/fuzzers/fuzzerCellsToMultiPolygon.c	1
h3lib/lib/cellsToMultiPoly.c	18
h3lib/include/cellsToMultiPoly.h	9
h3lib/lib/h3Index.c	16
h3lib/lib/baseCells.c	5
h3lib/lib/directedEdge.c	6
h3lib/lib/algos.c	5
h3lib/include/coordijk.h	16
h3lib/lib/vertex.c	2
h3lib/lib/faceijk.c	8
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	1
h3lib/include/vec3d.h	7
h3lib/lib/area.c	2
h3lib/include/adder.h	1

Fuzzer: fuzzerCellArea

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	1	0.60%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	1.21%
greenyellow	[30:49]	1	0.60%
lawngreen	50+	160	97.5%
All colors	164	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1	102	_hex2dToVec3	call site: 00102	_posAngleRads

Runtime coverage analysis

Covered functions

49

Functions that are reachable but not covered

7

Reachable functions

56

Percentage of reachable functions covered

87.5%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerCellArea.c	1
h3lib/lib/area.c	5
h3lib/lib/h3Index.c	7
h3lib/lib/baseCells.c	1
h3lib/include/coordijk.h	15
h3lib/lib/faceijk.c	8
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	1
h3lib/include/vec3d.h	7
h3lib/include/adder.h	1

Fuzzer: fuzzerCellsToLinkedMultiPolygon

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	21	7.39%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	263	92.6%
All colors	284	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	252	cellsToMultiPolygon	call site: 00252	createGlobeMultiPolygon
3	263	createMultiPolygon	call site: 00263	destroySortableLoopSet
2	246	geoLoopAreaRads2	call site: 00246	destroySortableLoopSet
1	20	createArcSet	call site: 00020	destroyArcSet
1	26	createArcSet	call site: 00026	destroyArcSet
1	34	getDirectedEdgeDestination	call site: 00034	_rotate60ccw
1	46	_h3Rotate60cw	call site: 00046	_h3Rotate60ccw
1	69	cellsToMultiPolygon	call site: 00069	destroyArcSet
1	187	_hex2dToVec3	call site: 00187	_posAngleRads
1	250	createSortableLoopSet	call site: 00250	destroyArcSet
1	260	createMultiPolygon	call site: 00260	destroySortablePolys
1	270	geoMultiPolygonToLinkedGeoPolygon	call site: 00270	destroyLinkedMultiPolygon

Runtime coverage analysis

Covered functions

103

Functions that are reachable but not covered

14

Reachable functions

117

Percentage of reachable functions covered

88.03%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerCellsToLinkedMultiPolygon.c	1
h3lib/lib/algos.c	6
h3lib/lib/cellsToMultiPoly.c	18
h3lib/include/cellsToMultiPoly.h	9
h3lib/lib/h3Index.c	16
h3lib/lib/baseCells.c	5
h3lib/lib/directedEdge.c	6
h3lib/include/coordijk.h	16
h3lib/lib/vertex.c	2
h3lib/lib/faceijk.c	8
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	1
h3lib/include/vec3d.h	7
h3lib/lib/area.c	2
h3lib/include/adder.h	1
h3lib/lib/linkedGeo.c	6

Fuzzer: fuzzerIndexIO

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	4	80.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	1	20.0%
All colors	5	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

2

Reachable functions

5

Percentage of reachable functions covered

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerIndexIO.c	1
h3lib/lib/h3Index.c	2

Fuzzer: fuzzerEdgeLength

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	1	0.57%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	1.14%
greenyellow	[30:49]	7	4.02%
lawngreen	50+	164	94.2%
All colors	174	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1	116	_hex2dToVec3	call site: 00116	_posAngleRads

Runtime coverage analysis

Covered functions

54

Functions that are reachable but not covered

7

Reachable functions

61

Percentage of reachable functions covered

88.52%

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
apps/fuzzers/fuzzerEdgeLength.c	1
h3lib/lib/latLng.c	5
h3lib/lib/directedEdge.c	2
h3lib/lib/vertex.c	2
h3lib/lib/h3Index.c	7
h3lib/lib/baseCells.c	4
h3lib/include/coordijk.h	15
h3lib/lib/faceijk.c	8
h3lib/lib/vec2d.c	3
h3lib/include/vec3d.h	7

Fuzzer: fuzzerLatLngToCell

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	3	3.57%
greenyellow	[30:49]	2	2.38%
lawngreen	50+	79	94.0%
All colors	84	100

Runtime coverage analysis

Covered functions

40

Functions that are reachable but not covered

8

Reachable functions

48

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.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerLatLngToCell.c	1
h3lib/lib/h3Index.c	8
h3lib/include/vec3d.h	8
h3lib/lib/faceijk.c	5
h3lib/lib/latLng.c	1
h3lib/include/coordijk.h	13
h3lib/lib/baseCells.c	4

Fuzzer: fuzzerPolygonToCells

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	26	8.84%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	268	91.1%
All colors	294	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
22	145	_faceIjkPentToCellBoundary	call site: 00145	_faceIjkToCellBoundary
2	278	gridDiskDistances	call site: 00278	getNumCells
1	266	h3NeighborRotations	call site: 00266	_h3Rotate60ccw
1	284	_gridDiskDistancesInternal	call site: 00284	_gridDiskDistancesInternal

Runtime coverage analysis

Covered functions

89

Functions that are reachable but not covered

15

Reachable functions

104

Percentage of reachable functions covered

85.58%

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
apps/fuzzers/fuzzerPolygonToCells.c	3
h3lib/lib/algos.c	9
h3lib/lib/polygon.c	3
h3lib/include/polygonAlgos.h	2
h3lib/lib/bbox.c	5
h3lib/lib/h3Index.c	16
h3lib/lib/baseCells.c	5
h3lib/include/coordijk.h	20
h3lib/lib/faceijk.c	13
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	4
h3lib/include/vec3d.h	9
h3lib/include/mathExtensions.h	1
h3lib/lib/mathExtensions.c	1

Fuzzer: fuzzerPolygonToCellsExperimentalNoHoles

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	14	4.15%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	0.29%
lawngreen	50+	322	95.5%
All colors	337	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
2	277	cellBoundaryCrossesGeoLoop	call site: 00277	cellBoundaryCrossesGeoLoop
1	8	_iterInitPolygonCompact	call site: 00008	iterErrorPolygonCompact
1	10	_iterInitPolygonCompact	call site: 00010	iterErrorPolygonCompact
1	13	bboxesFromGeoPolygon	call site: 00013	bboxFromGeoLoop
1	118	vec3ToLatLng	call site: 00118	iterErrorPolygonCompact
1	124	pointInsideGeoLoop	call site: 00124	pointInsideGeoLoop
1	186	iterStepPolygonCompact	call site: 00186	iterErrorPolygonCompact
1	249	_faceIjkToCellBoundary	call site: 00249	iterErrorPolygonCompact
1	258	iterStepPolygonCompact	call site: 00258	iterErrorPolygonCompact
1	281	cellBoundaryCrossesPolygon	call site: 00281	cellBoundaryCrossesGeoLoop
1	283	iterStepPolygonCompact	call site: 00283	iterErrorPolygonCompact
1	295	iterStepPolygonCompact	call site: 00295	iterErrorPolygonCompact

Runtime coverage analysis

Covered functions

112

Functions that are reachable but not covered

10

Reachable functions

122

Percentage of reachable functions covered

91.8%

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
apps/fuzzers/fuzzerPolygonToCellsExperimentalNoHoles.c	2
h3lib/lib/polyfill.c	14
h3lib/lib/h3Index.c	19
h3lib/lib/polygon.c	7
h3lib/include/polygonAlgos.h	2
h3lib/lib/bbox.c	9
h3lib/lib/latLng.c	3
h3lib/lib/baseCells.c	4
h3lib/include/coordijk.h	20
h3lib/lib/faceijk.c	13
h3lib/lib/vec2d.c	3
h3lib/include/vec3d.h	9
h3lib/lib/mathExtensions.c	1
h3lib/lib/iterators.c	6

Fuzzer: fuzzerPolygonToCellsNoHoles

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	30	10.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	260	89.6%
All colors	290	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
22	142	_faceIjkPentToCellBoundary	call site: 00142	_faceIjkToCellBoundary
2	275	gridDiskDistances	call site: 00275	getNumCells
1	172	bboxHexEstimate	call site: 00172	ADD_INT64S_OVERFLOWS
1	179	bboxesFromGeoPolygon	call site: 00179	bboxFromGeoLoop
1	247	vec3ToCell	call site: 00247	_getEdgeHexagons
1	263	h3NeighborRotations	call site: 00263	_h3Rotate60ccw
1	281	_gridDiskDistancesInternal	call site: 00281	_gridDiskDistancesInternal
1	288	pointInsideGeoLoop	call site: 00288	pointInsideGeoLoop

Runtime coverage analysis

Covered functions

88

Functions that are reachable but not covered

15

Reachable functions

103

Percentage of reachable functions covered

85.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
apps/fuzzers/fuzzerPolygonToCellsNoHoles.c	2
h3lib/lib/algos.c	9
h3lib/lib/polygon.c	3
h3lib/include/polygonAlgos.h	2
h3lib/lib/bbox.c	5
h3lib/lib/h3Index.c	16
h3lib/lib/baseCells.c	5
h3lib/include/coordijk.h	20
h3lib/lib/faceijk.c	13
h3lib/lib/vec2d.c	3
h3lib/lib/latLng.c	4
h3lib/include/vec3d.h	9
h3lib/include/mathExtensions.h	1
h3lib/lib/mathExtensions.c	1

Fuzzer: fuzzerCompact

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	36	100.%
All colors	36	100

Runtime coverage analysis

Covered functions

19

Functions that are reachable but not covered

2

Reachable functions

21

Percentage of reachable functions covered

90.48%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
apps/fuzzers/fuzzerCompact.c	1
h3lib/lib/h3Index.c	9
h3lib/lib/baseCells.c	1
h3lib/lib/mathExtensions.c	1
h3lib/include/mathExtensions.h	1
h3lib/lib/iterators.c	6

Fuzzer: fuzzerLocalIj

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	163	100.%
All colors	163	100

Runtime coverage analysis

Covered functions

44

Functions that are reachable but not covered

3

Reachable functions

47

Percentage of reachable functions covered

93.62%

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
apps/fuzzers/fuzzerLocalIj.c	2
h3lib/lib/localij.c	9
h3lib/lib/baseCells.c	4
h3lib/lib/h3Index.c	7
h3lib/include/coordijk.h	20
h3lib/include/mathExtensions.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
normalizeMultiPolygon	/src/h3/src/h3lib/lib/linkedGeo.c	1	['N/A']	6	0	215	30	9	15	0	100	84

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

Functions statically reachable by fuzzers

265 / 293

Cyclomatic complexity statically reachable by fuzzers

1497 / 1597

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.

apps/fuzzers/fuzzerInternalCoordIjk.c

Dictionary

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

apps/fuzzers/fuzzerCellToChildPos.c

Dictionary

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

apps/fuzzers/fuzzerHierarchy.c

Dictionary

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

apps/fuzzers/fuzzerDistances.c

Dictionary

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

apps/fuzzers/fuzzerResolutions.c

Dictionary

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

apps/fuzzers/fuzzerCellProperties.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=['cellToVertex', 'h3NeighborRotations']

apps/fuzzers/fuzzerConstructCell.c

Dictionary

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

apps/fuzzers/fuzzerCellToLatLng.c

Dictionary

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

apps/fuzzers/fuzzerVertexes.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=['_faceIjkPentToCellBoundary', '_faceIjkToCellBoundary', 'cellToVertex', 'h3NeighborRotations', '_hex2dToVec3']

apps/fuzzers/fuzzerDirectedEdge.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=['gridDiskDistances', '_h3Rotate60cw', '_gridDiskDistancesInternal', '_hex2dToVec3']

apps/fuzzers/fuzzerGridDisk.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=['_h3Rotate60cw']

apps/fuzzers/fuzzerInternalAlgos.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=['_h3Rotate60cw']

apps/fuzzers/fuzzerPolygonToCellsExperimental.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=['_faceIjkToH3', 'baseCellNumToCell', '_iterInitPolygonCompact', 'vec3ToLatLng', 'iterStepPolygonCompact', '_faceIjkToCellBoundary']

apps/fuzzers/fuzzerCellsToMultiPolygon.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=['cellsToMultiPolygon', 'createMultiPolygon', 'geoLoopAreaRads2', 'createArcSet', 'getDirectedEdgeDestination', '_h3Rotate60cw', '_hex2dToVec3', 'createSortableLoopSet']

apps/fuzzers/fuzzerCellArea.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=['_hex2dToVec3']

apps/fuzzers/fuzzerCellsToLinkedMultiPolygon.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=['cellsToMultiPolygon', 'createMultiPolygon', 'geoLoopAreaRads2', 'createArcSet', 'getDirectedEdgeDestination', '_h3Rotate60cw', '_hex2dToVec3', 'createSortableLoopSet']

apps/fuzzers/fuzzerIndexIO.c

Dictionary

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

apps/fuzzers/fuzzerEdgeLength.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=['_hex2dToVec3']

apps/fuzzers/fuzzerLatLngToCell.c

Dictionary

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

apps/fuzzers/fuzzerPolygonToCells.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=['_faceIjkPentToCellBoundary', 'gridDiskDistances', 'h3NeighborRotations', '_gridDiskDistancesInternal']

apps/fuzzers/fuzzerPolygonToCellsExperimentalNoHoles.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=['cellBoundaryCrossesGeoLoop', '_iterInitPolygonCompact', 'bboxesFromGeoPolygon', 'vec3ToLatLng', 'pointInsideGeoLoop', 'iterStepPolygonCompact', '_faceIjkToCellBoundary', 'cellBoundaryCrossesPolygon']

apps/fuzzers/fuzzerPolygonToCellsNoHoles.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=['_faceIjkPentToCellBoundary', 'gridDiskDistances', 'bboxHexEstimate', 'bboxesFromGeoPolygon', 'vec3ToCell', 'h3NeighborRotations', '_gridDiskDistancesInternal', 'pointInsideGeoLoop']

apps/fuzzers/fuzzerCompact.c

Dictionary

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

apps/fuzzers/fuzzerLocalIj.c

Dictionary

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

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

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/h3/src/apps/fuzzers/fuzzerCompact.c	['fuzzerCompact']	['fuzzerCompact']
/src/h3/src/apps/fuzzers/fuzzerDirectedEdge.c	['fuzzerDirectedEdge']	['fuzzerDirectedEdge']
/src/h3/src/apps/fuzzers/fuzzerLocalIj.c	['fuzzerLocalIj']	['fuzzerLocalIj']
/src/h3/src/h3lib/include/coordijk.h	['fuzzerInternalCoordIjk', 'fuzzerCellProperties', 'fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerGridDisk', 'fuzzerInternalAlgos', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLocalIj']	['fuzzerInternalCoordIjk', 'fuzzerCellProperties', 'fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerGridDisk', 'fuzzerInternalAlgos', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles', 'fuzzerLocalIj']
/src/h3/src/apps/fuzzers/fuzzerDistances.c	['fuzzerDistances']	['fuzzerDistances']
/src/h3/src/apps/fuzzers/fuzzerCellToLatLng.c	['fuzzerCellToLatLng']	['fuzzerCellToLatLng']
/src/h3/src/h3lib/lib/area.c	['fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon']	['fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon']
/src/h3/src/apps/fuzzers/fuzzerIndexIO.c	['fuzzerIndexIO']	['fuzzerIndexIO']
/src/h3/src/apps/fuzzers/fuzzerHierarchy.c	['fuzzerHierarchy']	['fuzzerHierarchy']
/src/h3/src/apps/fuzzers/fuzzerCellsToMultiPolygon.c	['fuzzerCellsToMultiPolygon']	['fuzzerCellsToMultiPolygon']
/src/h3/src/h3lib/lib/vertex.c	['fuzzerCellProperties', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerCellsToMultiPolygon', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength']	['fuzzerCellProperties', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerCellsToMultiPolygon', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength']
/src/h3/src/h3lib/lib/h3Index.c	['fuzzerCellToChildPos', 'fuzzerHierarchy', 'fuzzerResolutions', 'fuzzerCellProperties', 'fuzzerConstructCell', 'fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerGridDisk', 'fuzzerInternalAlgos', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerIndexIO', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles', 'fuzzerCompact', 'fuzzerLocalIj']	['fuzzerCellToChildPos', 'fuzzerHierarchy', 'fuzzerResolutions', 'fuzzerCellProperties', 'fuzzerConstructCell', 'fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerGridDisk', 'fuzzerInternalAlgos', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerIndexIO', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles', 'fuzzerCompact', 'fuzzerLocalIj']
/src/h3/src/h3lib/lib/polyfill.c	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/h3lib/lib/latLng.c	['fuzzerDistances', 'fuzzerResolutions', 'fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerGridDisk', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']	['fuzzerDistances', 'fuzzerResolutions', 'fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerGridDisk', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']
/src/h3/src/apps/fuzzers/fuzzerInternalCoordIjk.c	['fuzzerInternalCoordIjk']	['fuzzerInternalCoordIjk']
/src/h3/src/h3lib/lib/directedEdge.c	['fuzzerCellProperties', 'fuzzerDirectedEdge', 'fuzzerCellsToMultiPolygon', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength']	['fuzzerCellProperties', 'fuzzerDirectedEdge', 'fuzzerCellsToMultiPolygon', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength']
/src/h3/src/h3lib/lib/mathExtensions.c	['fuzzerCellToChildPos', 'fuzzerHierarchy', 'fuzzerResolutions', 'fuzzerDirectedEdge', 'fuzzerGridDisk', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles', 'fuzzerCompact']	['fuzzerCellToChildPos', 'fuzzerHierarchy', 'fuzzerResolutions', 'fuzzerGridDisk', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerCompact']
/src/h3/src/apps/fuzzers/fuzzerPolygonToCellsExperimental.c	['fuzzerPolygonToCellsExperimental']	['fuzzerPolygonToCellsExperimental']
/src/h3/src/h3lib/include/cellsToMultiPoly.h	['fuzzerCellsToMultiPolygon', 'fuzzerCellsToLinkedMultiPolygon']	['fuzzerCellsToMultiPolygon', 'fuzzerCellsToLinkedMultiPolygon']
/src/h3/src/h3lib/lib/algos.c	['fuzzerCellProperties', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerGridDisk', 'fuzzerInternalAlgos', 'fuzzerCellsToMultiPolygon', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles']	['fuzzerCellProperties', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerGridDisk', 'fuzzerInternalAlgos', 'fuzzerCellsToMultiPolygon', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles']
/src/h3/src/h3lib/lib/bbox.c	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']
/src/h3/src/h3lib/lib/cellsToMultiPoly.c	['fuzzerCellsToMultiPolygon', 'fuzzerCellsToLinkedMultiPolygon']	['fuzzerCellsToMultiPolygon', 'fuzzerCellsToLinkedMultiPolygon']
/src/h3/src/apps/fuzzers/fuzzerCellArea.c	['fuzzerCellArea']	['fuzzerCellArea']
/src/h3/src/apps/fuzzers/fuzzerConstructCell.c	['fuzzerConstructCell']	['fuzzerConstructCell']
/src/h3/src/h3lib/include/mathExtensions.h	['fuzzerInternalCoordIjk', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerCompact', 'fuzzerLocalIj']	['fuzzerInternalCoordIjk', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsNoHoles', 'fuzzerCompact', 'fuzzerLocalIj']
/src/h3/src/apps/fuzzers/fuzzerGridDisk.c	['fuzzerGridDisk']	['fuzzerGridDisk']
/src/h3/src/apps/fuzzers/fuzzerVertexes.c	['fuzzerVertexes']	['fuzzerVertexes']
/src/h3/src/apps/fuzzers/fuzzerInternalAlgos.c	['fuzzerInternalAlgos']	['fuzzerInternalAlgos']
/src/h3/src/h3lib/lib/baseCells.c	['fuzzerCellToChildPos', 'fuzzerHierarchy', 'fuzzerResolutions', 'fuzzerCellProperties', 'fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerGridDisk', 'fuzzerInternalAlgos', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles', 'fuzzerCompact', 'fuzzerLocalIj']	['fuzzerCellToChildPos', 'fuzzerHierarchy', 'fuzzerResolutions', 'fuzzerCellProperties', 'fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerGridDisk', 'fuzzerInternalAlgos', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles', 'fuzzerCompact', 'fuzzerLocalIj']
/src/h3/src/h3lib/include/vec3d.h	['fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']	['fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']
/src/h3/src/h3lib/lib/faceijk.c	['fuzzerCellProperties', 'fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']	['fuzzerCellProperties', 'fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerLatLngToCell', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']
/src/h3/src/h3lib/lib/vec2d.c	['fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']	['fuzzerCellToLatLng', 'fuzzerVertexes', 'fuzzerDirectedEdge', 'fuzzerPolygonToCellsExperimental', 'fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon', 'fuzzerEdgeLength', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']
/src/h3/src/h3lib/lib/linkedGeo.c	['fuzzerCellsToLinkedMultiPolygon']	['fuzzerCellsToLinkedMultiPolygon']
/src/h3/src/h3lib/include/polygonAlgos.h	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']
/src/h3/src/apps/fuzzers/fuzzerCellProperties.c	['fuzzerCellProperties']	['fuzzerCellProperties']
/src/h3/src/apps/fuzzers/fuzzerEdgeLength.c	['fuzzerEdgeLength']	['fuzzerEdgeLength']
/src/h3/src/apps/fuzzers/fuzzerPolygonToCellsExperimentalNoHoles.c	['fuzzerPolygonToCellsExperimentalNoHoles']	['fuzzerPolygonToCellsExperimentalNoHoles']
/src/h3/src/h3lib/lib/polygon.c	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']	['fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCells', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerPolygonToCellsNoHoles']
/src/h3/src/apps/fuzzers/fuzzerCellToChildPos.c	['fuzzerCellToChildPos']	['fuzzerCellToChildPos']
/src/h3/src/apps/fuzzers/fuzzerLatLngToCell.c	['fuzzerLatLngToCell']	['fuzzerLatLngToCell']
/src/h3/src/h3lib/lib/localij.c	['fuzzerLocalIj']	['fuzzerLocalIj']
/src/h3/src/apps/fuzzers/fuzzerPolygonToCells.c	['fuzzerPolygonToCells']	['fuzzerPolygonToCells']
/src/h3/src/apps/fuzzers/fuzzerPolygonToCellsNoHoles.c	['fuzzerPolygonToCellsNoHoles']	['fuzzerPolygonToCellsNoHoles']
/src/h3/src/h3lib/lib/iterators.c	['fuzzerHierarchy', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerCompact']	['fuzzerHierarchy', 'fuzzerPolygonToCellsExperimental', 'fuzzerPolygonToCellsExperimentalNoHoles', 'fuzzerCompact']
/src/h3/src/h3lib/include/adder.h	['fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon']	['fuzzerCellsToMultiPolygon', 'fuzzerCellArea', 'fuzzerCellsToLinkedMultiPolygon']
/src/h3/src/apps/fuzzers/fuzzerCellsToLinkedMultiPolygon.c	['fuzzerCellsToLinkedMultiPolygon']	['fuzzerCellsToLinkedMultiPolygon']
/src/h3/src/apps/fuzzers/fuzzerResolutions.c	['fuzzerResolutions']	['fuzzerResolutions']

Directories in report

Directory
/src/h3/src/h3lib/lib/
/src/h3/src/h3lib/include/
/src/h3/src/apps/fuzzers/