High level conclusions

Fuzzers reach 20.96% of cyclomatic complexity.

Fuzzers reach 20.64% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

308 / 1492

Cyclomatic complexity statically reachable by fuzzers

1968 / 9386

Runtime code coverage of functions

250 / 1492

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: twkb_import_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	51	21.5%
gold	[1:9]	2	0.84%
yellow	[10:29]	1	0.42%
greenyellow	[30:49]	3	1.26%
lawngreen	50+	180	75.9%
All colors	237	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
8	184	lwpoly_free	call site: 00184	lwcircstring_free
8	216	lwcollection_free	call site: 00216	lwnurbscurve_free
7	206	lwmpoly_free	call site: 00206	lwpsurface_free
5	96	ptarray_insert_point	call site: 00096	lwerror
3	65	lwline_from_twkb_state	call site: 00065	lwline_construct_empty
3	131	lwcollection_add_lwgeom	call site: 00131	lwtype_name
2	106	ptarray_set_point4d	call site: 00106	lwtype_name
2	227	lwgeom_from_twkb_state	call site: 00227	lwtype_name
2	232	lwcollection_from_twkb_state	call site: 00232	lwgeom_free
1	82	lwpoly_from_twkb_state	call site: 00082	lwerror
1	87	lwpoly_from_twkb_state	call site: 00087	lwerror
1	90	getPoint4d_p	call site: 00090	lwerror

Runtime coverage analysis

Covered functions

78

Functions that are reachable but not covered

8

Reachable functions

77

Percentage of reachable functions covered

89.61%

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
fuzzers/twkb_import_fuzzer.cpp	1
fuzzers/liblwgeom_fuzzer.hpp	1
liblwgeom/lwin_twkb.c	22
liblwgeom/lwutil.c	6
liblwgeom/varint.c	5
liblwgeom/lwpoint.c	3
liblwgeom/ptarray.c	6
liblwgeom/./lwinline.h	2
liblwgeom/lwgeom.c	6
liblwgeom/lwline.c	3
liblwgeom/lwpoly.c	3
liblwgeom/lwgeom_api.c	2
liblwgeom/lwcollection.c	5
liblwgeom/lwcircstring.c	1
liblwgeom/lwtriangle.c	1
liblwgeom/lwmpoint.c	1
liblwgeom/lwmline.c	1
liblwgeom/lwmpoly.c	1
liblwgeom/lwpsurface.c	1
liblwgeom/lwtin.c	1
liblwgeom/lwnurbscurve.c	1
liblwgeom/gbox.c	1

Fuzzer: wkb_import_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	72	23.8%
gold	[1:9]	13	4.30%
yellow	[10:29]	6	1.98%
greenyellow	[30:49]	3	0.99%
lawngreen	50+	208	68.8%
All colors	302	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
5	264	lwnurbscurve_from_wkb_state	call site: 00264	lwerror
4	72	lwcircstring_construct_empty	call site: 00072	lwtype_name
4	91	lwpoly_free	call site: 00091	lwpoly_free
4	99	ptarray_is_closed_2d	call site: 00099	lwpoly_free
4	117	lwtriangle_from_wkb_state	call site: 00117	lwtriangle_construct_empty
3	106	lwpoly_add_ring	call site: 00106	lwpoly_free
3	255	lwnurbscurve_from_wkb_state	call site: 00255	ptarray_free
3	275	lwnurbscurve_construct	call site: 00275	ptarray_free
3	290	lwcollection_reserve	call site: 00290	lwgeom_free
2	61	lwline_construct_empty	call site: 00061	lwtype_name
2	185	lwnurbscurve_free	call site: 00185	lwtype_name
2	214	lwnurbscurve_from_wkb_state	call site: 00214	ptarray_free

Runtime coverage analysis

Covered functions

81

Functions that are reachable but not covered

2

Reachable functions

73

Percentage of reachable functions covered

97.26%

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
fuzzers/wkb_import_fuzzer.cpp	1
fuzzers/liblwgeom_fuzzer.hpp	1
liblwgeom/lwin_wkb.c	17
liblwgeom/lwutil.c	8
liblwgeom/ptarray.c	7
liblwgeom/./lwinline.h	3
liblwgeom/lwpoint.c	3
liblwgeom/lwline.c	3
liblwgeom/lwcircstring.c	3
liblwgeom/lwpoly.c	3
liblwgeom/lwtriangle.c	3
liblwgeom/lwcurvepoly.c	2
liblwgeom/lwgeom.c	2
liblwgeom/lwmpoint.c	1
liblwgeom/lwmline.c	1
liblwgeom/lwmpoly.c	1
liblwgeom/lwpsurface.c	1
liblwgeom/lwtin.c	1
liblwgeom/lwcollection.c	5
liblwgeom/lwnurbscurve.c	3
liblwgeom/lwgeom_api.c	1

Fuzzer: raster_deserialize_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	14	22.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	3.22%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	46	74.1%
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
3	20	rt_raster_deserialize	call site: 00020	rt_band_destroy
3	47	rt_raster_deserialize	call site: 00047	rt_band_destroy
3	52	rt_raster_deserialize	call site: 00052	rt_band_destroy
2	17	rt_raster_deserialize	call site: 00017	rterror
1	15	rt_raster_deserialize	call site: 00015	rterror
1	24	rt_band_destroy	call site: 00024	rtdealloc
1	26	rt_band_destroy	call site: 00026	rt_raster_destroy

Runtime coverage analysis

Covered functions

27

Functions that are reachable but not covered

3

Reachable functions

26

Percentage of reachable functions covered

88.46%

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
fuzzers/raster_deserialize_fuzzer.c	5
raster/rt_core/rt_pixel.c	1
raster/rt_core/rt_context.c	3
raster/rt_core/rt_serialize.c	9
raster/rt_core/rt_band.c	1
raster/rt_core/rt_raster.c	3
raster/rt_core/rt_util.c	1

Fuzzer: geojson_import_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	148	36.0%
gold	[1:9]	7	1.70%
yellow	[10:29]	8	1.95%
greenyellow	[30:49]	2	0.48%
lawngreen	50+	245	59.7%
All colors	410	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
47	318	getPoint2d_cp	call site: 00318	lwcollection_calculate_gbox_geodetic
23	276	lwgeom_force_dims	call site: 00276	lwnurbscurve_force_dims
14	383	lwline_calculate_gbox_cartesian	call site: 00383	lwcircstring_calculate_gbox_cartesian
8	220	lwcollection_free	call site: 00220	lwnurbscurve_free
7	196	lwpoly_free	call site: 00196	lwcircstring_free
7	210	lwmpoly_free	call site: 00210	lwpsurface_free
6	311	lwgeom_add_bbox	call site: 00311	lwgeom_calculate_gbox_geodetic
5	60	ptarray_insert_point	call site: 00060	lwerror
5	376	ptarray_calculate_gbox_cartesian_3d	call site: 00376	ptarray_calculate_gbox_cartesian_4d
4	51	parse_geojson_coord	call site: 00051	getPoint4d_p
3	130	lwcollection_add_lwgeom	call site: 00130	lwtype_name
3	403	lwcollection_calculate_gbox_cartesian	call site: 00403	ptarray_calculate_gbox_cartesian

Runtime coverage analysis

Covered functions

87

Functions that are reachable but not covered

57

Reachable functions

140

Percentage of reachable functions covered

59.29%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzers/geojson_import_fuzzer.cpp	1
liblwgeom/lwin_geojson.c	13
liblwgeom/lwutil.c	6
liblwgeom/ptarray.c	6
liblwgeom/./lwinline.h	13
liblwgeom/lwgeom_api.c	2
liblwgeom/lwpoint.c	4
liblwgeom/lwline.c	4
liblwgeom/lwpoly.c	4
liblwgeom/lwcollection.c	7
liblwgeom/lwgeom.c	10
liblwgeom/lwmpoint.c	2
liblwgeom/lwmline.c	2
liblwgeom/lwmpoly.c	2
liblwgeom/lwcircstring.c	1
liblwgeom/lwtriangle.c	1
liblwgeom/lwpsurface.c	1
liblwgeom/lwtin.c	1
liblwgeom/lwnurbscurve.c	5
liblwgeom/gbox.c	20
liblwgeom/lwgeodetic.c	17
liblwgeom/lwalgorithm.c	3

Fuzzer: wkt_import_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	514	68.0%
gold	[1:9]	17	2.25%
yellow	[10:29]	2	0.26%
greenyellow	[30:49]	3	0.39%
lawngreen	50+	219	29.0%
All colors	755	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
136	554	wkt_parser_point_new	call site: 00554	wkt_parser_nurbscurve_new
42	691	wkt_yyparse	call site: 00691	yydestruct
27	191	wkt_parser_collection_new	call site: 00191	wkt_parser_collection_finalize
26	365	lwcompound_curve_endpoint	call site: 00365	lwgeom_is_closed
24	455	wkt_parser_compound_new	call site: 00455	wkt_parser_collection_finalize
20	54	yy_get_next_buffer	call site: 00054	wkt_yyrestart
20	268	ptarray_is_closed_2d	call site: 00268	lwcompound_is_closed
15	331	ptarray_set_point4d	call site: 00331	lwcompound_is_closed
14	247	wkt_parser_curvepolygon_add_ring	call site: 00247	lwgeom_free
13	29	wkt_yylex	call site: 00029	wkt_yy_create_buffer
13	296	ptarray_construct_empty	call site: 00296	lwnurbscurve_get_or_generate_knots
11	530	wkt_parser_triangle_new	call site: 00530	wkt_parser_collection_finalize

Runtime coverage analysis

Covered functions

136

Functions that are reachable but not covered

62

Reachable functions

188

Percentage of reachable functions covered

67.02%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
fuzzers/wkt_import_fuzzer.cpp	1
liblwgeom/lwin_wkt.c	30
liblwgeom/lwin_wkt_parse.y	7
liblwgeom/lwin_wkt_lex.l	6
liblwgeom/lwin_wkt_lex.c	19
liblwgeom/lwutil.c	8
liblwgeom/lwin_wkt_parse.c	2
liblwgeom/lwgeom.c	22
liblwgeom/lwcollection.c	8
liblwgeom/./lwinline.h	10
liblwgeom/lwpoint.c	4
liblwgeom/ptarray.c	9
liblwgeom/lwline.c	5
liblwgeom/lwpoly.c	6
liblwgeom/lwcircstring.c	4
liblwgeom/lwtriangle.c	3
liblwgeom/lwmpoint.c	1
liblwgeom/lwmline.c	1
liblwgeom/lwmpoly.c	1
liblwgeom/lwpsurface.c	2
liblwgeom/lwtin.c	2
liblwgeom/lwnurbscurve.c	8
liblwgeom/lwcurvepoly.c	2
liblwgeom/lwcompound.c	6
liblwgeom/lwgeom_api.c	3
fuzzers/liblwgeom_fuzzer.hpp	1

Optimal target analysis

Remaining optimal interesting functions

The following table shows a list of functions that are optimal targets. Optimal targets are identified by finding the functions that in combination, yield a high code coverage.

Func name	Functions filename	Arg count	Args	Function depth	hitcount	instr count	bb count	cyclomatic complexity	Reachable functions	Incoming references	total cyclomatic complexity	Unreached complexity
rt_raster_fully_within_distance	/src/postgis/raster/rt_core/rt_spatial_relationship.c	6	['N/A', 'int', 'N/A', 'int', 'double', 'N/A']	13	0	216	42	17	452	0	2594	1689
lwgeom_mindistance3d	/src/postgis/liblwgeom/measures3d.c	2	['N/A', 'N/A']	19	0	18	3	2	334	0	2146	555
gserialized_cmp	/src/postgis/liblwgeom/gserialized.c	2	['N/A', 'N/A']	11	0	359	50	22	146	0	819	371
lwgeom_to_ewkt	/src/postgis/liblwgeom/lwgeom.c	1	['N/A']	13	0	34	6	3	77	0	370	324
rt_raster_gdal_rasterize	/src/postgis/raster/rt_core/rt_raster.c	20	['N/A', 'int', 'N/A', 'int', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']	9	0	2429	379	147	137	0	822	308
lwgeom_distance_spheroid	/src/postgis/liblwgeom/lwgeodetic.c	4	['N/A', 'N/A', 'N/A', 'double']	10	0	833	135	49	75	1	509	293
lwgeom_subdivide_recursive	/src/postgis/liblwgeom/lwgeom.c	6	['N/A', 'char', 'int', 'int', 'N/A', 'double']	12	0	716	105	39	207	3	1269	234
rt_raster_gdal_contour	/src/postgis/raster/rt_core/rt_gdal.c	11	['N/A', 'int', 'int', 'N/A', 'double', 'double', 'int', 'N/A', 'int', 'N/A', 'N/A']	10	0	412	44	18	307	0	1590	205
rt_raster_intersects	/src/postgis/raster/rt_core/rt_spatial_relationship.c	5	['N/A', 'int', 'N/A', 'int', 'N/A']	10	0	933	162	61	225	0	1374	157
lwgeom_covers_lwgeom_sphere	/src/postgis/liblwgeom/lwgeodetic.c	2	['N/A', 'N/A']	12	0	393	77	28	87	1	518	127

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

Functions statically reachable by fuzzers

837 / 1492

Cyclomatic complexity statically reachable by fuzzers

5915 / 9386

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.

fuzzers/twkb_import_fuzzer.cpp

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=['lwpoly_free', 'lwcollection_free', 'lwmpoly_free', 'ptarray_insert_point', 'lwline_from_twkb_state', 'lwcollection_add_lwgeom', 'ptarray_set_point4d', 'lwgeom_from_twkb_state', 'lwcollection_from_twkb_state', 'lwpoly_from_twkb_state']

fuzzers/wkb_import_fuzzer.cpp

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=['lwnurbscurve_from_wkb_state', 'lwcircstring_construct_empty', 'lwpoly_free', 'ptarray_is_closed_2d', 'lwtriangle_from_wkb_state', 'lwpoly_add_ring', 'lwnurbscurve_construct', 'lwcollection_reserve', 'lwline_construct_empty']

fuzzers/raster_deserialize_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=['rt_raster_deserialize', 'rt_band_destroy']

fuzzers/geojson_import_fuzzer.cpp

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=['getPoint2d_cp', 'lwgeom_force_dims', 'lwline_calculate_gbox_cartesian', 'lwcollection_free', 'lwpoly_free', 'lwmpoly_free', 'lwgeom_add_bbox', 'ptarray_insert_point', 'ptarray_calculate_gbox_cartesian_3d', 'parse_geojson_coord']

fuzzers/wkt_import_fuzzer.cpp

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=['wkt_parser_point_new', 'wkt_yyparse', 'wkt_parser_collection_new', 'lwcompound_curve_endpoint', 'wkt_parser_compound_new', 'yy_get_next_buffer', 'ptarray_is_closed_2d', 'ptarray_set_point4d', 'wkt_parser_curvepolygon_add_ring', 'wkt_yylex']

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
ptarray_insert_point	43	20	46.51%	['wkt_import_fuzzer', 'geojson_import_fuzzer', 'twkb_import_fuzzer']
lwpoly_from_wkb_state	50	24	48.0%	['wkb_import_fuzzer']
lwgeom_startpoint	36	10	27.77%	['wkt_import_fuzzer']
wkt_parser_polygon_add_ring	38	15	39.47%	['wkt_import_fuzzer']
wkt_parser_curvepolygon_add_ring	68	16	23.52%	['wkt_import_fuzzer']
yy_get_next_buffer	89	18	20.22%	['wkt_import_fuzzer']
yydestruct	229	78	34.06%	['wkt_import_fuzzer']

This section shows which files and directories are considered in this report. The main reason for showing this is fuzz introspector may include more code in the reasoning than is desired. This section helps identify if too many files/directories are included, e.g. third party code, which may be irrelevant for the threat model. In the event too much is included, fuzz introspector supports a configuration file that can exclude data from the report. See the following link for more information on how to create a config file: link

Files in report

Source file	Reached by	Covered by
	[]	[]
/src/postgis/fuzzers/liblwgeom_fuzzer.hpp	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwutil.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwhomogenize.c	[]	[]
/src/postgis/liblwgeom/lwgeom_geos.c	[]	[]
/src/postgis/fuzzers/raster_deserialize_fuzzer.c	['raster_deserialize_fuzzer']	['raster_deserialize_fuzzer']
/src/postgis/raster/rt_core/../../liblwgeom/stringbuffer.h	[]	[]
/src/postgis/fuzzers/geos_stub.h	[]	[]
/src/postgis/liblwgeom/varint.c	['twkb_import_fuzzer']	['twkb_import_fuzzer']
/src/postgis/liblwgeom/ptarray.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwin_geojson.c	['geojson_import_fuzzer']	['geojson_import_fuzzer']
/src/postgis/liblwgeom/lwstroke.c	[]	[]
/src/postgis/raster/rt_core/rt_serialize.c	['raster_deserialize_fuzzer']	['raster_deserialize_fuzzer']
/src/postgis/liblwgeom/lwin_twkb.c	['twkb_import_fuzzer']	['twkb_import_fuzzer']
/src/postgis/liblwgeom/lwmline.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwtriangle.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['wkb_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwspheroid.c	[]	[]
/src/postgis/liblwgeom/lwline.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwnurbscurve.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['wkb_import_fuzzer']
/src/postgis/fuzzers/geojson_import_fuzzer.cpp	['geojson_import_fuzzer']	['geojson_import_fuzzer']
/src/postgis/raster/rt_core/rt_util.c	['raster_deserialize_fuzzer']	['raster_deserialize_fuzzer']
/src/postgis/liblwgeom/lwpoly.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwgeom_geos_node.c	[]	[]
/src/postgis/fuzzers/proj_stub.h	[]	[]
/src/postgis/liblwgeom/lwcurvepoly.c	['wkb_import_fuzzer', 'wkt_import_fuzzer']	['wkb_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwcircstring.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['wkb_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwtin.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['wkb_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwin_wkt_lex.l	['wkt_import_fuzzer']	['wkt_import_fuzzer']
/src/postgis/liblwgeom/lwgeom.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/fuzzers/twkb_import_fuzzer.cpp	['twkb_import_fuzzer']	['twkb_import_fuzzer']
/src/postgis/liblwgeom/lwiterator.c	[]	[]
/src/postgis/liblwgeom/gserialized2.c	[]	[]
/src/postgis/liblwgeom/optionlist.c	[]	[]
/src/postgis/deps/ryu/d2s.c	[]	[]
/src/postgis/liblwgeom/lwlinearreferencing.c	[]	[]
/src/postgis/raster/rt_core/rt_gdal.c	[]	[]
/src/postgis/liblwgeom/measures3d.c	[]	[]
/src/postgis/fuzzers/wkb_import_fuzzer.cpp	['wkb_import_fuzzer']	['wkb_import_fuzzer']
/src/postgis/liblwgeom/measures.c	[]	[]
/src/postgis/liblwgeom/lwpoint.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwgeom_api.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwprint.c	[]	[]
/src/postgis/liblwgeom/gserialized.c	[]	[]
/src/postgis/liblwgeom/lwin_wkb.c	['wkb_import_fuzzer']	['wkb_import_fuzzer']
/src/postgis/liblwgeom/./stringbuffer.h	[]	[]
/src/postgis/liblwgeom/gserialized1.c	[]	[]
/src/postgis/liblwgeom/./lwinline.h	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	[]
/src/postgis/deps/ryu/./../ryu/common.h	[]	[]
/src/postgis/liblwgeom/lwgeom_geos_clean.c	[]	[]
/src/postgis/raster/rt_core/rt_pixel.c	['raster_deserialize_fuzzer']	['raster_deserialize_fuzzer']
/src/postgis/liblwgeom/lookup3.c	[]	[]
/src/postgis/liblwgeom/lwcollection.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwpsurface.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['wkb_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/lwmpoly.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/liblwgeom/gbox.c	['twkb_import_fuzzer', 'geojson_import_fuzzer']	['twkb_import_fuzzer', 'geojson_import_fuzzer']
/src/postgis/liblwgeom/lwalgorithm.c	['geojson_import_fuzzer']	[]
/src/postgis/liblwgeom/lwmpoint.c	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']	['twkb_import_fuzzer', 'wkb_import_fuzzer', 'geojson_import_fuzzer', 'wkt_import_fuzzer']
/src/postgis/deps/ryu/./../ryu/d2s_intrinsics.h	[]	[]
/src/postgis/raster/rt_core/rt_spatial_relationship.c	[]	[]
/src/postgis/fuzzers/wkt_import_fuzzer.cpp	['wkt_import_fuzzer']	['wkt_import_fuzzer']
/src/postgis/liblwgeom/lwin_wkt_parse.y	['wkt_import_fuzzer']	['wkt_import_fuzzer']
/src/postgis/liblwgeom/lwin_wkt_parse.c	['wkt_import_fuzzer']	['wkt_import_fuzzer']
/src/postgis/liblwgeom/lwin_wkt_lex.c	['wkt_import_fuzzer']	['wkt_import_fuzzer']
/src/postgis/liblwgeom/lwout_wkt.c	[]	[]
/src/postgis/liblwgeom/lwrandom.c	[]	[]
/src/postgis/liblwgeom/stringbuffer.c	[]	[]
/src/postgis/liblwgeom/lwgeom_geos_split.c	[]	[]
/src/postgis/raster/rt_core/rt_context.c	['raster_deserialize_fuzzer']	['raster_deserialize_fuzzer']
/src/postgis/liblwgeom/lwgeodetic.c	['geojson_import_fuzzer']	[]
/src/postgis/raster/rt_core/rt_geometry.c	[]	[]
/src/postgis/liblwgeom/lwcompound.c	['wkt_import_fuzzer']	['wkt_import_fuzzer']
/src/postgis/liblwgeom/lwin_wkt.c	['wkt_import_fuzzer']	['wkt_import_fuzzer']
/src/postgis/raster/rt_core/rt_raster.c	['raster_deserialize_fuzzer']	['raster_deserialize_fuzzer']
/src/postgis/raster/rt_core/rt_band.c	['raster_deserialize_fuzzer']	['raster_deserialize_fuzzer']

Directories in report

Directory
/src/postgis/liblwgeom/
/src/postgis/deps/ryu/./../ryu/
/src/postgis/fuzzers/
/src/postgis/raster/rt_core/../../liblwgeom/
/src/postgis/deps/ryu/
/src/postgis/liblwgeom/./
/src/postgis/raster/rt_core/