High level conclusions

Fuzzers reach 65.45% code coverage.

Fuzzers reach 23.18% of cyclomatic complexity.

Fuzzers reach 14.84% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

122 / 822

Cyclomatic complexity statically reachable by fuzzers

1921 / 8287

Runtime code coverage of functions

538 / 822

Warning: The number of runtime covered functions are larger than the number of reachable functions. This means that Fuzz Introspector found there are more functions covered at runtime than what is considered reachable based on the static analysis. This is a limitation in the analysis as anything covered at runtime is by definition reachable by the fuzzers.
This is likely due to a limitation in the static analysis. In this case, the count of functions covered at runtime is the true value, which means this is what should be considered "achieved" by the fuzzer.

Use the project functions table below to query all functions that were not covered at runtime.

The following table shows data about each function in the project. The functions included in this table correspond to all functions that exist in the executables of the fuzzers. As such, there may be functions that are from third-party libraries.

For further technical details on the meaning of columns in the below table, please see the Glossary .

Func name	Functions filename	Args	Function call depth	Reached by Fuzzers	Runtime reached by Fuzzers	Combined reached by Fuzzers	Fuzzers runtime hit	Func lines hit %	I Count	BB Count	Cyclomatic complexity	Functions reached	Reached by functions	Accumulated cyclomatic complexity	Undiscovered complexity

Fuzzer: FuzzClient

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	49	31.6%
gold	[1:9]	15	9.67%
yellow	[10:29]	6	3.87%
greenyellow	[30:49]	10	6.45%
lawngreen	50+	75	48.3%
All colors	155	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
19	80	json_internal_read_object	call site: 00080	iso8601_to_timespec
9	23	json_internal_read_object	call site: 00023	json_read_array
4	55	json_internal_read_object	call site: 00055	atol
3	47	json_internal_read_object	call site: 00047	json_trace
3	121	gpsd_acquire_reporting_lock	call site: 00121	strerror
3	132	gpsd_release_reporting_lock	call site: 00132	strerror
2	3	json_read_object	call site: 00003	json_internal_read_object
2	51	json_internal_read_object	call site: 00051	atoi
2	128	gpsd_vlog	call site: 00128	syslog
1	18	json_internal_read_object	call site: 00018	json_trace
1	69	safe_atof	call site: 00069	safe_atof

Runtime coverage analysis

Covered functions

16

Functions that are reachable but not covered

33

Reachable functions

49

Percentage of reachable functions covered

32.65%

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
fuzzer/FuzzClient.c	1
gpsd-3.27.6~dev/libgps/shared_json.c	2
gpsd-3.27.6~dev/libgps/json.c	5
gpsd-3.27.6~dev/libgps/gpsutils.c	3
gpsd-3.27.6~dev/libgps/os_compat.c	1
gpsd-3.27.6~dev/libgps/../include/strfuncs.h	1
gpsd-3.27.6~dev/gpsd/net_ntrip.c	1
gpsd-3.27.6~dev/gpsd/libgpsd_core.c	5

Fuzzer: FuzzJson

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	18	5.60%
gold	[1:9]	97	30.2%
yellow	[10:29]	27	8.41%
greenyellow	[30:49]	10	3.11%
lawngreen	50+	169	52.6%
All colors	321	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
13	86	json_internal_read_object	call site: 00086	iso8601_to_timespec
2	9	json_read_object	call site: 00009	json_internal_read_object
2	31	json_read_array	call site: 00031	json_trace
1	64	json_internal_read_object	call site: 00064	atoi

Runtime coverage analysis

Covered functions

31

Functions that are reachable but not covered

22

Reachable functions

53

Percentage of reachable functions covered

58.49%

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
fuzzer/FuzzJson.c	1
gpsd-3.27.6~dev/libgps/libgps_json.c	13
gpsd-3.27.6~dev/libgps/../include/strfuncs.h	1
gpsd-3.27.6~dev/libgps/json.c	5
gpsd-3.27.6~dev/libgps/gpsutils.c	3
gpsd-3.27.6~dev/libgps/os_compat.c	1
gpsd-3.27.6~dev/libgps/shared_json.c	2
gpsd-3.27.6~dev/libgps/rtcm2_json.c	1
gpsd-3.27.6~dev/libgps/rtcm3_json.c	1
gpsd-3.27.6~dev/libgps/ais_json.c	2
gpsd-3.27.6~dev/libgps/hex.c	2

Fuzzer: FuzzPacket

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	88	25.1%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	262	74.8%
All colors	350	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
42	291	packet_get	call site: 00291	packet_get1_chunked
17	9	isgps_decode	call site: 00009	gpsd_vlog
5	129	nextstate	call site: 00129	gpsd_log
3	42	nextstate	call site: 00042	gpsd_log
3	335	packet_get1	call site: 00335	gpsd_log
2	97	nextstate	call site: 00097	rtcm2_decode
2	122	nextstate	call site: 00122	gps_hexdump
2	183	nextstate	call site: 00183	gpsd_log
2	258	packet_parse	call site: 00258	gpsd_log
2	344	packet_get1	call site: 00344	packet_discard
1	32	isgps_decode	call site: 00032	gpsd_log
1	120	nextstate	call site: 00120	character_pushback

Runtime coverage analysis

Covered functions

28

Functions that are reachable but not covered

30

Reachable functions

58

Percentage of reachable functions covered

48.28%

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
fuzzer/FuzzPacket.c	1
gpsd-3.27.6~dev/gpsd/packet.c	18
gpsd-3.27.6~dev/gpsd/isgps.c	3
gpsd-3.27.6~dev/drivers/driver_rtcm2.c	3
gpsd-3.27.6~dev/gpsd/libgpsd_core.c	4
gpsd-3.27.6~dev/libgps/hex.c	2
gpsd-3.27.6~dev/gpsd/../include/strfuncs.h	1
gpsd-3.27.6~dev/drivers/driver_greis_checksum.c	2
gpsd-3.27.6~dev/gpsd/crc24q.c	2

Fuzzer: FuzzDrivers

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	142	26.1%
gold	[1:9]	3	0.55%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	398	73.2%
All colors	543	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
39	39	gpsd_poll	call site: 00039	packet_get1_chunked
35	411	gpsd_poll	call site: 00411	gpsd_set_speed
8	448	gpsd_get_speed	call site: 00448	gpsd_serial_isatty
6	529	earth_distance_and_bearings	call site: 00529	sin
5	185	nextstate	call site: 00185	gpsd_log
4	342	packet_unstash	call site: 00342	gpsd_log
3	23	gpsd_acquire_reporting_lock	call site: 00023	strerror
3	34	gpsd_release_reporting_lock	call site: 00034	strerror
3	98	nextstate	call site: 00098	gpsd_log
3	364	gpsd_poll	call site: 00364	gpsd_log
3	386	strlcpy	call site: 00386	gmtime_r
2	30	gpsd_vlog	call site: 00030	syslog

Runtime coverage analysis

Covered functions

406

Functions that are reachable but not covered

55

Reachable functions

120

Percentage of reachable functions covered

54.17%

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
fuzzer/FuzzDrivers.c	1
gpsd-3.27.6~dev/gpsd/libgpsd_core.c	11
gpsd-3.27.6~dev/gpsd/packet.c	17
gpsd-3.27.6~dev/gpsd/isgps.c	3
gpsd-3.27.6~dev/libgps/gpsutils.c	10
gpsd-3.27.6~dev/gpsd/../include/strfuncs.h	2
gpsd-3.27.6~dev/libgps/hex.c	2
gpsd-3.27.6~dev/drivers/driver_rtcm2.c	3
gpsd-3.27.6~dev/drivers/driver_greis_checksum.c	2
gpsd-3.27.6~dev/gpsd/crc24q.c	2
gpsd-3.27.6~dev/gpsd/../include/timespec.h	1
gpsd-3.27.6~dev/libgps/timespec_str.c	1
gpsd-3.27.6~dev/gpsd/timebase.c	2
gpsd-3.27.6~dev/libgps/os_compat.c	3
gpsd-3.27.6~dev/gpsd/serial.c	8
gpsd-3.27.6~dev/libgps/gps_maskdump.c	1
gpsd-3.27.6~dev/gpsd/matrix.c	1
gpsd-3.27.6~dev/gpsd/geoid.c	4

Fuzzer: FuzzDriversStructured

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	142	25.0%
gold	[1:9]	1	0.17%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	0.17%
lawngreen	50+	422	74.5%
All colors	566	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
39	62	gpsd_poll	call site: 00062	packet_get1_chunked
35	434	gpsd_poll	call site: 00434	gpsd_set_speed
8	471	gpsd_get_speed	call site: 00471	gpsd_serial_isatty
6	552	earth_distance_and_bearings	call site: 00552	sin
5	208	nextstate	call site: 00208	gpsd_log
4	365	packet_unstash	call site: 00365	gpsd_log
3	46	gpsd_acquire_reporting_lock	call site: 00046	strerror
3	57	gpsd_release_reporting_lock	call site: 00057	strerror
3	121	nextstate	call site: 00121	gpsd_log
3	387	gpsd_poll	call site: 00387	gpsd_log
3	409	strlcpy	call site: 00409	gmtime_r
2	53	gpsd_vlog	call site: 00053	syslog

Runtime coverage analysis

Covered functions

496

Functions that are reachable but not covered

55

Reachable functions

138

Percentage of reachable functions covered

60.14%

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
fuzzer/FuzzDriversStructured.c	20
gpsd-3.27.6~dev/gpsd/libgpsd_core.c	12
gpsd-3.27.6~dev/gpsd/packet.c	17
gpsd-3.27.6~dev/gpsd/isgps.c	3
gpsd-3.27.6~dev/libgps/gpsutils.c	10
gpsd-3.27.6~dev/gpsd/../include/strfuncs.h	2
gpsd-3.27.6~dev/libgps/hex.c	2
gpsd-3.27.6~dev/drivers/driver_rtcm2.c	3
gpsd-3.27.6~dev/drivers/driver_greis_checksum.c	2
gpsd-3.27.6~dev/gpsd/crc24q.c	2
gpsd-3.27.6~dev/gpsd/../include/timespec.h	1
gpsd-3.27.6~dev/libgps/timespec_str.c	1
gpsd-3.27.6~dev/gpsd/timebase.c	2
gpsd-3.27.6~dev/libgps/os_compat.c	3
gpsd-3.27.6~dev/gpsd/serial.c	8
gpsd-3.27.6~dev/libgps/gps_maskdump.c	1
gpsd-3.27.6~dev/gpsd/matrix.c	1
gpsd-3.27.6~dev/gpsd/geoid.c	4

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
ubx_parse	/src/gpsd/gpsd-3.27.6~dev/drivers/driver_ubx.c	3	['N/A', 'N/A', 'size_t']	7	0	2144	404	121	120	0	1122	993
gpsd_multipoll	/src/gpsd/gpsd-3.27.6~dev/gpsd/libgpsd_core.c	4	['bool', 'N/A', 'N/A', 'float']	7	0	424	86	36	186	0	1963	554
tsip_parse_input	/src/gpsd/gpsd-3.27.6~dev/drivers/driver_tsip.c	1	['N/A']	8	0	759	164	53	101	0	671	537
sirfbin_parse_input	/src/gpsd/gpsd-3.27.6~dev/drivers/driver_sirf.c	1	['N/A']	9	0	38	8	4	87	0	808	414
skybin_parse_input	/src/gpsd/gpsd-3.27.6~dev/drivers/driver_skytraq.c	1	['N/A']	7	0	299	60	5	75	0	484	233
aivdm_analyze	/src/gpsd/gpsd-3.27.6~dev/drivers/drivers.c	1	['N/A']	6	0	48	10	5	45	0	416	229
rtcm104v3_analyze	/src/gpsd/gpsd-3.27.6~dev/drivers/drivers.c	1	['N/A']	6	0	43	6	3	22	0	252	194
gps_mainloop	/src/gpsd/gpsd-3.27.6~dev/libgps/libgps_core.c	3	['N/A', 'int', 'N/A']	11	0	120	29	12	75	0	831	142
oncore_parse_input	/src/gpsd/gpsd-3.27.6~dev/drivers/driver_oncore.c	1	['N/A']	7	0	38	8	4	46	0	313	134
navcom_parse_input	/src/gpsd/gpsd-3.27.6~dev/drivers/driver_navcom.c	1	['N/A']	7	0	38	8	4	48	0	297	109

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

Functions statically reachable by fuzzers

430 / 822

Cyclomatic complexity statically reachable by fuzzers

5406 / 8287

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.

fuzzer/FuzzClient.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=['json_internal_read_object', 'gpsd_acquire_reporting_lock', 'gpsd_release_reporting_lock', 'json_read_object', 'gpsd_vlog']

fuzzer/FuzzJson.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=['json_internal_read_object', 'json_read_object', 'json_read_array']

fuzzer/FuzzPacket.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=['packet_get', 'isgps_decode', 'nextstate', 'packet_get1', 'packet_parse']

fuzzer/FuzzDrivers.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=['gpsd_poll', 'gpsd_get_speed', 'earth_distance_and_bearings', 'nextstate', 'packet_unstash', 'gpsd_acquire_reporting_lock', 'gpsd_release_reporting_lock']

fuzzer/FuzzDriversStructured.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=['gpsd_poll', 'gpsd_get_speed', 'earth_distance_and_bearings', 'nextstate', 'packet_unstash', 'gpsd_acquire_reporting_lock', 'gpsd_release_reporting_lock']

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
gpsd_vlog	76	31	40.78%	['FuzzDriversStructured', 'FuzzPacket', 'FuzzClient', 'FuzzDrivers']
json_read_array	206	93	45.14%	['FuzzJson', 'FuzzClient']
garmintxt_parse	172	66	38.37%	['FuzzDriversStructured', 'FuzzDrivers']
sirf_msg_navnot	61	28	45.90%	['FuzzDriversStructured', 'FuzzDrivers']
superstar2_msg_svinfo	36	5	13.88%	['FuzzDriversStructured', 'FuzzDrivers']
superstar2_msg_navsol_lla	80	15	18.75%	['FuzzDriversStructured', 'FuzzDrivers']
json_pass_packet	32	9	28.12%	['FuzzDriversStructured', 'FuzzDrivers']
processINFO	45	22	48.88%	['FuzzDriversStructured']
decode_xa2_00	80	22	27.50%	['FuzzDriversStructured']
subframe_bds	243	11	4.526%	['FuzzDriversStructured']
subframe_bds6	33	10	30.30%	['FuzzDriversStructured']

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/gpsd/gpsd-3.27.6~dev/drivers/driver_greis.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/../include/strfuncs.h	['FuzzClient', 'FuzzJson']	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_rtcm2.c	['FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']	['FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/gpsd/bsd_base64.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_geostar.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_oncore.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_sirf.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/hex.c	['FuzzJson', 'FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']	['FuzzJson', 'FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_italk.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_ais.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/netlib.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/gpsd/ppsthread.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/gps_maskdump.c	['FuzzDrivers', 'FuzzDriversStructured']	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/libgps_sock.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_nmea2000.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/gpsd/../include/strfuncs.h	['FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']	[]
/src/gpsd/gpsd-3.27.6~dev/gpsd/matrix.c	['FuzzDrivers', 'FuzzDriversStructured']	['FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/gpsd/net_dgpsip.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/shared_json.c	['FuzzClient', 'FuzzJson']	['FuzzClient', 'FuzzJson']
/src/gpsd/gpsd-3.27.6~dev/libgps/json.c	['FuzzClient', 'FuzzJson']	['FuzzClient', 'FuzzJson']
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_skytraq.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_casic.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/bits.c	[]	[]
/src/gpsd/fuzzer/FuzzClient.c	['FuzzClient']	['FuzzClient']
/src/gpsd/gpsd-3.27.6~dev/libgps/rtcm2_json.c	['FuzzJson']	['FuzzJson']
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_superstar2.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/libgps_shm.c	[]	[]
/src/gpsd/fuzzer/FuzzDriversStructured.c	['FuzzDriversStructured']	['FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_nmea0183.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/gpsd/net_ntrip.c	['FuzzClient']	['FuzzClient']
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_evermore.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/libgps_json.c	['FuzzJson']	['FuzzJson']
/src/gpsd/gpsd-3.27.6~dev/libgps/ais_json.c	['FuzzJson']	['FuzzJson']
/src/gpsd/fuzzer/FuzzDrivers.c	['FuzzDrivers']	['FuzzDrivers']
/src/gpsd/gpsd-3.27.6~dev/libgps/rtcm3_json.c	['FuzzJson']	['FuzzJson']
/src/gpsd/gpsd-3.27.6~dev/gpsd/subframe.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/timespec_str.c	['FuzzDrivers', 'FuzzDriversStructured']	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/libgps_core.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_spartn.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/gpsd/crc24q.c	['FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']	['FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/libgps/../include/timespec.h	[]	[]
/src/gpsd/gpsd-3.27.6~dev/gpsd/net_gnss_dispatch.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/gpsd/pseudonmea.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/gpsd/timebase.c	['FuzzDrivers', 'FuzzDriversStructured']	['FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/gpsd/serial.c	['FuzzDrivers', 'FuzzDriversStructured']	['FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_ubx.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_rtcm3.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/../include/compiler.h	[]	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_garmin.c	[]	[]
/src/gpsd/fuzzer/FuzzPacket.c	['FuzzPacket']	['FuzzPacket']
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_garmin_txt.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/gpsd/pseudoais.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_tsip.c	[]	[]
/src/gpsd/fuzzer/FuzzJson.c	['FuzzJson']	['FuzzJson']
/src/gpsd/gpsd-3.27.6~dev/gpsd/libgpsd_core.c	['FuzzClient', 'FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']	['FuzzClient', 'FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_allystar.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/drivers/drivers.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/os_compat.c	['FuzzClient', 'FuzzJson', 'FuzzDrivers', 'FuzzDriversStructured']	['FuzzClient', 'FuzzJson', 'FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_greis_checksum.c	['FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']	['FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/gpsd/isgps.c	['FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']	['FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_navcom.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/gpsd/packet.c	['FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']	['FuzzPacket', 'FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/drivers/driver_zodiac.c	[]	[]
/src/gpsd/gpsd-3.27.6~dev/libgps/gpsutils.c	['FuzzClient', 'FuzzJson', 'FuzzDrivers', 'FuzzDriversStructured']	['FuzzClient', 'FuzzJson', 'FuzzDrivers', 'FuzzDriversStructured']
/src/gpsd/gpsd-3.27.6~dev/gpsd/geoid.c	['FuzzDrivers', 'FuzzDriversStructured']	['FuzzDrivers', 'FuzzDriversStructured']

Directories in report

Directory
/src/gpsd/gpsd-3.27.6~dev/libgps/../include/
/src/gpsd/gpsd-3.27.6~dev/gpsd/../include/
/src/gpsd/gpsd-3.27.6~dev/gpsd/
/src/gpsd/gpsd-3.27.6~dev/libgps/
/src/gpsd/gpsd-3.27.6~dev/drivers/
/src/gpsd/fuzzer/