High level conclusions

Fuzzers reach 11.41% of cyclomatic complexity.

Fuzzers reach 9.915% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

59 / 595

Cyclomatic complexity statically reachable by fuzzers

341 / 2987

Runtime code coverage of functions

55 / 595

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: decode_get_error_injection_types_v1_resp_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	0	0.0%
gold	[1:9]	1	14.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	85.7%
All colors	7	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_get_error_injection_types_v1_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_set_current_error_injection_types_v1_resp_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	0	0.0%
gold	[1:9]	1	14.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	14.2%
lawngreen	50+	5	71.4%
All colors	7	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_set_current_error_injection_types_v1_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_get_fpga_diagnostics_settings_wp_jumper_resp_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	1	14.2%
gold	[1:9]	1	14.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	5	71.4%
All colors	7	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	5	decode_reason_code_and_cc	call site: 00005	__uint16_identity

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	2
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_get_power_supply_status_resp_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	1	14.2%
gold	[1:9]	1	14.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	5	71.4%
All colors	7	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	5	decode_reason_code_and_cc	call site: 00005	__uint16_identity

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_get_power_supply_status_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	2
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_disable_tokens_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	33.3%
lawngreen	50+	2	66.6%
All colors	3	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

0

Reachable functions

4

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
/src/decode_nsm_disable_tokens_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/debug-token.c	1

Fuzzer: decode_get_error_injection_types_v1_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	100.%
All colors	6	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_get_error_injection_types_v1_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/byteswap.h	1

Fuzzer: decode_get_histogram_format_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	2	40.0%
lawngreen	50+	3	60.0%
All colors	5	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

2

Reachable functions

6

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
/src/decode_get_histogram_format_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	2

Fuzzer: decode_get_histogram_data_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	2	40.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	60.0%
All colors	5	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

2

Reachable functions

6

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
/src/decode_get_histogram_data_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	2

Fuzzer: decode_long_running_resp_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	0	0.0%
gold	[1:9]	1	14.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	85.7%
All colors	7	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_long_running_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	3
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_get_error_injection_payload_req_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	0	0.0%
gold	[1:9]	1	14.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	85.7%
All colors	7	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

2

Reachable functions

8

Percentage of reachable functions covered

75.0%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_get_error_injection_payload_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/byteswap.h	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_query_token_status_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	100.%
All colors	3	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

0

Reachable functions

4

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
/src/decode_nsm_query_token_status_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/debug-token.c	1

Fuzzer: decode_get_fpga_diagnostics_settings_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	100.%
All colors	3	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

0

Reachable functions

4

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
/src/decode_get_fpga_diagnostics_settings_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1

Fuzzer: decode_common_resp_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	0	0.0%
gold	[1:9]	1	16.6%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	16.6%
lawngreen	50+	4	66.6%
All colors	6	100

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

1

Reachable functions

6

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
/src/decode_common_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_query_device_identification_resp_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	0	0.0%
gold	[1:9]	1	20.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	80.0%
All colors	5	100

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

1

Reachable functions

6

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
/src/decode_query_device_identification_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_set_current_event_sources_resp_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	100.%
All colors	3	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

0

Reachable functions

4

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
/src/decode_nsm_set_current_event_sources_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-capability-discovery.c	1

Fuzzer: decode_nsm_query_token_parameters_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	100.%
All colors	3	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

0

Reachable functions

4

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
/src/decode_nsm_query_token_parameters_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/debug-token.c	1

Fuzzer: decode_get_histogram_data_resp_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	6	37.5%
gold	[1:9]	1	6.25%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	9	56.2%
All colors	16	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
4	8	decode_get_histogram_data_resp	call site: 00008	__uint16_identity
2	13	letohArrayData	call site: 00013	__uint64_identity

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

3

Reachable functions

10

Percentage of reachable functions covered

70.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
/src/decode_get_histogram_data_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	4
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	3

Fuzzer: decode_nsm_event_with_data_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	5	100.%
All colors	5	100

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

1

Reachable functions

6

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
/src/decode_nsm_event_with_data_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_set_error_injection_payload_resp_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	0	0.0%
gold	[1:9]	1	14.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	14.2%
lawngreen	50+	5	71.4%
All colors	7	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_set_error_injection_payload_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_get_error_injection_mode_v1_resp_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	0	0.0%
gold	[1:9]	2	25.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	75.0%
All colors	8	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

2

Reachable functions

8

Percentage of reachable functions covered

75.0%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_get_error_injection_mode_v1_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	2

Fuzzer: decode_get_fpga_diagnostics_settings_wp_resp_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	1	14.2%
gold	[1:9]	1	14.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	5	71.4%
All colors	7	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	5	decode_reason_code_and_cc	call site: 00005	__uint16_identity

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_get_fpga_diagnostics_settings_wp_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	2
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_get_event_log_record_resp_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	100.%
All colors	6	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

3

Reachable functions

7

Percentage of reachable functions covered

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_nsm_get_event_log_record_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-capability-discovery.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	3

Fuzzer: decode_activate_error_injection_payload_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	100.%
All colors	6	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_activate_error_injection_payload_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/byteswap.h	1

Fuzzer: decode_nsm_event_acknowledgement_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	100.%
All colors	3	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

0

Reachable functions

4

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
/src/decode_nsm_event_acknowledgement_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	1

Fuzzer: decode_nsm_provide_token_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	100.%
All colors	3	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

0

Reachable functions

4

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
/src/decode_nsm_provide_token_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/debug-token.c	1

Fuzzer: decode_get_histogram_format_resp_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	6	33.3%
gold	[1:9]	1	5.55%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	11	61.1%
All colors	18	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
4	10	decode_get_histogram_format_resp	call site: 00010	__uint16_identity
2	15	letohArrayData	call site: 00015	__uint64_identity

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

3

Reachable functions

10

Percentage of reachable functions covered

70.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
/src/decode_get_histogram_format_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	4
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	3

Fuzzer: decode_get_error_injection_mode_v1_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	100.%
All colors	6	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_get_error_injection_mode_v1_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/byteswap.h	1

Fuzzer: decode_get_error_injection_payload_resp_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	0	0.0%
gold	[1:9]	4	40.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	60.0%
All colors	10	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

2

Reachable functions

8

Percentage of reachable functions covered

75.0%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_get_error_injection_payload_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	2

Fuzzer: decode_set_current_error_injection_types_v1_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	100.%
All colors	6	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_set_current_error_injection_types_v1_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/byteswap.h	1

Fuzzer: decode_common_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	5	100.%
All colors	5	100

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

1

Reachable functions

6

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
/src/decode_common_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/byteswap.h	1

Fuzzer: decode_get_fpga_diagnostics_settings_resp_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	1	16.6%
gold	[1:9]	1	16.6%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	66.6%
All colors	6	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	4	decode_reason_code_and_cc	call site: 00004	__uint16_identity

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

1

Reachable functions

6

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
/src/decode_get_fpga_diagnostics_settings_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_long_running_event_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	0	0.0%
gold	[1:9]	1	20.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	80.0%
All colors	5	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

1

Reachable functions

5

Percentage of reachable functions covered

80.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
/src/decode_long_running_event_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_set_event_subscription_resp_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	100.%
All colors	3	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

0

Reachable functions

4

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
/src/decode_nsm_set_event_subscription_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-capability-discovery.c	1

Fuzzer: decode_nsm_rediscovery_event_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	1	25.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	75.0%
All colors	4	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

1

Reachable functions

5

Percentage of reachable functions covered

80.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
/src/decode_nsm_rediscovery_event_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-capability-discovery.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_set_error_injection_mode_v1_resp_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	0	0.0%
gold	[1:9]	1	14.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	85.7%
All colors	7	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_set_error_injection_mode_v1_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_event_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	100.%
All colors	4	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

1

Reachable functions

5

Percentage of reachable functions covered

80.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
/src/decode_nsm_event_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_query_device_ids_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	33.3%
lawngreen	50+	2	66.6%
All colors	3	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

0

Reachable functions

4

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
/src/decode_nsm_query_device_ids_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/debug-token.c	1

Fuzzer: decode_set_error_injection_payload_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	3	33.3%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	66.6%
All colors	9	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

2

Reachable functions

8

Percentage of reachable functions covered

75.0%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_set_error_injection_payload_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/byteswap.h	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_long_running_resp_with_data_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	1	12.5%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	7	87.5%
All colors	8	100

Runtime coverage analysis

Covered functions

6

Functions that are reachable but not covered

1

Reachable functions

8

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
/src/decode_long_running_resp_with_data_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	4
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_disable_tokens_resp_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	0	0.0%
gold	[1:9]	1	20.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	80.0%
All colors	5	100

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

1

Reachable functions

6

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
/src/decode_nsm_disable_tokens_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/debug-token.c	1
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_set_event_subscription_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	33.3%
lawngreen	50+	2	66.6%
All colors	3	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

0

Reachable functions

4

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
/src/decode_nsm_set_event_subscription_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-capability-discovery.c	1

Fuzzer: decode_activate_error_injection_payload_resp_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	0	0.0%
gold	[1:9]	1	14.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	14.2%
lawngreen	50+	5	71.4%
All colors	7	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_activate_error_injection_payload_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_query_token_status_resp_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	0	0.0%
gold	[1:9]	1	20.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	80.0%
All colors	5	100

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

1

Reachable functions

6

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
/src/decode_nsm_query_token_status_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/debug-token.c	1
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_provide_token_resp_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	0	0.0%
gold	[1:9]	1	20.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	80.0%
All colors	5	100

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

1

Reachable functions

6

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
/src/decode_nsm_provide_token_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/debug-token.c	1
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_set_error_injection_mode_v1_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	100.%
All colors	6	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_set_error_injection_mode_v1_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-configuration.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/byteswap.h	1

Fuzzer: decode_nsm_get_event_subscription_resp_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	0	0.0%
gold	[1:9]	1	12.5%
yellow	[10:29]	1	12.5%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	75.0%
All colors	8	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

2

Reachable functions

8

Percentage of reachable functions covered

75.0%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_nsm_get_event_subscription_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-capability-discovery.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/byteswap.h	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_reason_code_and_cc_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	0	0.0%
gold	[1:9]	1	25.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	75.0%
All colors	4	100

Runtime coverage analysis

Covered functions

3

Functions that are reachable but not covered

1

Reachable functions

5

Percentage of reachable functions covered

80.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
/src/decode_reason_code_and_cc_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_nsm_get_event_subscription_req_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	0	0.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	100.%
All colors	6	100

Runtime coverage analysis

Covered functions

5

Functions that are reachable but not covered

1

Reachable functions

7

Percentage of reachable functions covered

85.71%

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/decode_nsm_get_event_subscription_req_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/device-capability-discovery.c	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/byteswap.h	1

Fuzzer: decode_nsm_query_token_parameters_resp_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	0	0.0%
gold	[1:9]	1	20.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	80.0%
All colors	5	100

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

1

Reachable functions

6

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
/src/decode_nsm_query_token_parameters_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/debug-token.c	1
/src/nsmd/libnsm/base.c	1
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	1

Fuzzer: decode_ping_resp_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	0	0.0%
gold	[1:9]	1	20.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	80.0%
All colors	5	100

Runtime coverage analysis

Covered functions

4

Functions that are reachable but not covered

1

Reachable functions

6

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
/src/decode_ping_resp_fuzzer.cc	1
/src/fuzzer_helpers.h	1
/src/nsmd/libnsm/base.c	2
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	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
decode_nsm_query_get_erot_state_parameters_resp	/src/nsmd/libnsm/firmware-utils.c	5	['N/A', 'size_t', 'N/A', 'N/A', 'N/A']	3	0	206	27	11	14	0	99	85

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

Functions statically reachable by fuzzers

69 / 595

Cyclomatic complexity statically reachable by fuzzers

424 / 2987

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.

/src/decode_get_error_injection_types_v1_resp_fuzzer.cc

Dictionary

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

/src/decode_set_current_error_injection_types_v1_resp_fuzzer.cc

Dictionary

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

/src/decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer.cc

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=['decode_reason_code_and_cc']

/src/decode_get_power_supply_status_resp_fuzzer.cc

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=['decode_reason_code_and_cc']

/src/decode_nsm_disable_tokens_req_fuzzer.cc

Dictionary

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

/src/decode_get_error_injection_types_v1_req_fuzzer.cc

Dictionary

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

/src/decode_get_histogram_format_req_fuzzer.cc

Dictionary

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

/src/decode_get_histogram_data_req_fuzzer.cc

Dictionary

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

/src/decode_long_running_resp_fuzzer.cc

Dictionary

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

/src/decode_get_error_injection_payload_req_fuzzer.cc

Dictionary

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

/src/decode_nsm_query_token_status_req_fuzzer.cc

Dictionary

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

/src/decode_get_fpga_diagnostics_settings_req_fuzzer.cc

Dictionary

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

/src/decode_common_resp_fuzzer.cc

Dictionary

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

/src/decode_query_device_identification_resp_fuzzer.cc

Dictionary

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

/src/decode_nsm_set_current_event_sources_resp_fuzzer.cc

Dictionary

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

/src/decode_nsm_query_token_parameters_req_fuzzer.cc

Dictionary

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

/src/decode_get_histogram_data_resp_fuzzer.cc

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=['decode_get_histogram_data_resp', 'letohArrayData']

/src/decode_nsm_event_with_data_fuzzer.cc

Dictionary

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

/src/decode_set_error_injection_payload_resp_fuzzer.cc

Dictionary

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

/src/decode_get_error_injection_mode_v1_resp_fuzzer.cc

Dictionary

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

/src/decode_get_fpga_diagnostics_settings_wp_resp_fuzzer.cc

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=['decode_reason_code_and_cc']

/src/decode_nsm_get_event_log_record_resp_fuzzer.cc

Dictionary

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

/src/decode_activate_error_injection_payload_req_fuzzer.cc

Dictionary

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

/src/decode_nsm_event_acknowledgement_fuzzer.cc

Dictionary

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

/src/decode_nsm_provide_token_req_fuzzer.cc

Dictionary

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

/src/decode_get_histogram_format_resp_fuzzer.cc

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=['decode_get_histogram_format_resp', 'letohArrayData']

/src/decode_get_error_injection_mode_v1_req_fuzzer.cc

Dictionary

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

/src/decode_get_error_injection_payload_resp_fuzzer.cc

Dictionary

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

/src/decode_set_current_error_injection_types_v1_req_fuzzer.cc

Dictionary

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

/src/decode_common_req_fuzzer.cc

Dictionary

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

/src/decode_get_fpga_diagnostics_settings_resp_fuzzer.cc

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=['decode_reason_code_and_cc']

/src/decode_long_running_event_fuzzer.cc

Dictionary

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

/src/decode_nsm_set_event_subscription_resp_fuzzer.cc

Dictionary

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

/src/decode_nsm_rediscovery_event_fuzzer.cc

Dictionary

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

/src/decode_set_error_injection_mode_v1_resp_fuzzer.cc

Dictionary

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

/src/decode_nsm_event_fuzzer.cc

Dictionary

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

/src/decode_nsm_query_device_ids_req_fuzzer.cc

Dictionary

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

/src/decode_set_error_injection_payload_req_fuzzer.cc

Dictionary

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

/src/decode_long_running_resp_with_data_fuzzer.cc

Dictionary

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

/src/decode_nsm_disable_tokens_resp_fuzzer.cc

Dictionary

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

/src/decode_nsm_set_event_subscription_req_fuzzer.cc

Dictionary

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

/src/decode_activate_error_injection_payload_resp_fuzzer.cc

Dictionary

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

/src/decode_nsm_query_token_status_resp_fuzzer.cc

Dictionary

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

/src/decode_nsm_provide_token_resp_fuzzer.cc

Dictionary

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

/src/decode_set_error_injection_mode_v1_req_fuzzer.cc

Dictionary

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

/src/decode_nsm_get_event_subscription_resp_fuzzer.cc

Dictionary

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

/src/decode_reason_code_and_cc_fuzzer.cc

Dictionary

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

/src/decode_nsm_get_event_subscription_req_fuzzer.cc

Dictionary

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

/src/decode_nsm_query_token_parameters_resp_fuzzer.cc

Dictionary

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

/src/decode_ping_resp_fuzzer.cc

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
letohArrayData	77	41	53.24%	['decode_get_histogram_data_resp_fuzzer', 'decode_get_histogram_format_resp_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/decode_nsm_disable_tokens_req_fuzzer.cc	['decode_nsm_disable_tokens_req_fuzzer']	['decode_nsm_disable_tokens_req_fuzzer']
/src/decode_get_error_injection_mode_v1_req_fuzzer.cc	['decode_get_error_injection_mode_v1_req_fuzzer']	['decode_get_error_injection_mode_v1_req_fuzzer']
/src/decode_nsm_query_token_status_resp_fuzzer.cc	['decode_nsm_query_token_status_resp_fuzzer']	['decode_nsm_query_token_status_resp_fuzzer']
/src/decode_get_power_supply_status_resp_fuzzer.cc	['decode_get_power_supply_status_resp_fuzzer']	['decode_get_power_supply_status_resp_fuzzer']
/src/decode_nsm_set_event_subscription_req_fuzzer.cc	['decode_nsm_set_event_subscription_req_fuzzer']	['decode_nsm_set_event_subscription_req_fuzzer']
/src/decode_common_resp_fuzzer.cc	['decode_common_resp_fuzzer']	['decode_common_resp_fuzzer']
/src/decode_nsm_query_token_parameters_req_fuzzer.cc	['decode_nsm_query_token_parameters_req_fuzzer']	['decode_nsm_query_token_parameters_req_fuzzer']
/src/nsmd/libnsm/debug-token.c	['decode_nsm_disable_tokens_req_fuzzer', 'decode_nsm_query_token_status_req_fuzzer', 'decode_nsm_query_token_parameters_req_fuzzer', 'decode_nsm_provide_token_req_fuzzer', 'decode_nsm_query_device_ids_req_fuzzer', 'decode_nsm_disable_tokens_resp_fuzzer', 'decode_nsm_query_token_status_resp_fuzzer', 'decode_nsm_provide_token_resp_fuzzer', 'decode_nsm_query_token_parameters_resp_fuzzer']	['decode_nsm_disable_tokens_req_fuzzer', 'decode_nsm_query_token_status_req_fuzzer', 'decode_nsm_query_token_parameters_req_fuzzer', 'decode_nsm_provide_token_req_fuzzer', 'decode_nsm_query_device_ids_req_fuzzer', 'decode_nsm_disable_tokens_resp_fuzzer', 'decode_nsm_query_token_status_resp_fuzzer', 'decode_nsm_provide_token_resp_fuzzer', 'decode_nsm_query_token_parameters_resp_fuzzer']
/src/decode_get_histogram_format_resp_fuzzer.cc	['decode_get_histogram_format_resp_fuzzer']	['decode_get_histogram_format_resp_fuzzer']
/src/decode_nsm_event_with_data_fuzzer.cc	['decode_nsm_event_with_data_fuzzer']	['decode_nsm_event_with_data_fuzzer']
/src/nsmd/libnsm/diagnostics.c	[]	[]
/src/decode_ping_resp_fuzzer.cc	['decode_ping_resp_fuzzer']	['decode_ping_resp_fuzzer']
/src/decode_nsm_disable_tokens_resp_fuzzer.cc	['decode_nsm_disable_tokens_resp_fuzzer']	['decode_nsm_disable_tokens_resp_fuzzer']
/src/decode_set_current_error_injection_types_v1_req_fuzzer.cc	['decode_set_current_error_injection_types_v1_req_fuzzer']	['decode_set_current_error_injection_types_v1_req_fuzzer']
/src/decode_get_error_injection_types_v1_resp_fuzzer.cc	['decode_get_error_injection_types_v1_resp_fuzzer']	['decode_get_error_injection_types_v1_resp_fuzzer']
/src/decode_nsm_rediscovery_event_fuzzer.cc	['decode_nsm_rediscovery_event_fuzzer']	['decode_nsm_rediscovery_event_fuzzer']
/src/decode_get_histogram_format_req_fuzzer.cc	['decode_get_histogram_format_req_fuzzer']	['decode_get_histogram_format_req_fuzzer']
/src/nsmd/libnsm/pci-links.c	[]	[]
/src/fuzzer_helpers.h	['decode_get_error_injection_types_v1_resp_fuzzer', 'decode_set_current_error_injection_types_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer', 'decode_get_power_supply_status_resp_fuzzer', 'decode_nsm_disable_tokens_req_fuzzer', 'decode_get_error_injection_types_v1_req_fuzzer', 'decode_get_histogram_format_req_fuzzer', 'decode_get_histogram_data_req_fuzzer', 'decode_long_running_resp_fuzzer', 'decode_get_error_injection_payload_req_fuzzer', 'decode_nsm_query_token_status_req_fuzzer', 'decode_get_fpga_diagnostics_settings_req_fuzzer', 'decode_common_resp_fuzzer', 'decode_query_device_identification_resp_fuzzer', 'decode_nsm_set_current_event_sources_resp_fuzzer', 'decode_nsm_query_token_parameters_req_fuzzer', 'decode_get_histogram_data_resp_fuzzer', 'decode_nsm_event_with_data_fuzzer', 'decode_set_error_injection_payload_resp_fuzzer', 'decode_get_error_injection_mode_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_resp_fuzzer', 'decode_nsm_get_event_log_record_resp_fuzzer', 'decode_activate_error_injection_payload_req_fuzzer', 'decode_nsm_event_acknowledgement_fuzzer', 'decode_nsm_provide_token_req_fuzzer', 'decode_get_histogram_format_resp_fuzzer', 'decode_get_error_injection_mode_v1_req_fuzzer', 'decode_get_error_injection_payload_resp_fuzzer', 'decode_set_current_error_injection_types_v1_req_fuzzer', 'decode_common_req_fuzzer', 'decode_get_fpga_diagnostics_settings_resp_fuzzer', 'decode_long_running_event_fuzzer', 'decode_nsm_set_event_subscription_resp_fuzzer', 'decode_nsm_rediscovery_event_fuzzer', 'decode_set_error_injection_mode_v1_resp_fuzzer', 'decode_nsm_event_fuzzer', 'decode_nsm_query_device_ids_req_fuzzer', 'decode_set_error_injection_payload_req_fuzzer', 'decode_long_running_resp_with_data_fuzzer', 'decode_nsm_disable_tokens_resp_fuzzer', 'decode_nsm_set_event_subscription_req_fuzzer', 'decode_activate_error_injection_payload_resp_fuzzer', 'decode_nsm_query_token_status_resp_fuzzer', 'decode_nsm_provide_token_resp_fuzzer', 'decode_set_error_injection_mode_v1_req_fuzzer', 'decode_nsm_get_event_subscription_resp_fuzzer', 'decode_reason_code_and_cc_fuzzer', 'decode_nsm_get_event_subscription_req_fuzzer', 'decode_nsm_query_token_parameters_resp_fuzzer', 'decode_ping_resp_fuzzer']	['decode_get_error_injection_types_v1_resp_fuzzer', 'decode_set_current_error_injection_types_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer', 'decode_get_power_supply_status_resp_fuzzer', 'decode_nsm_disable_tokens_req_fuzzer', 'decode_get_error_injection_types_v1_req_fuzzer', 'decode_get_histogram_format_req_fuzzer', 'decode_get_histogram_data_req_fuzzer', 'decode_long_running_resp_fuzzer', 'decode_get_error_injection_payload_req_fuzzer', 'decode_nsm_query_token_status_req_fuzzer', 'decode_get_fpga_diagnostics_settings_req_fuzzer', 'decode_common_resp_fuzzer', 'decode_query_device_identification_resp_fuzzer', 'decode_nsm_set_current_event_sources_resp_fuzzer', 'decode_nsm_query_token_parameters_req_fuzzer', 'decode_get_histogram_data_resp_fuzzer', 'decode_nsm_event_with_data_fuzzer', 'decode_set_error_injection_payload_resp_fuzzer', 'decode_get_error_injection_mode_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_resp_fuzzer', 'decode_nsm_get_event_log_record_resp_fuzzer', 'decode_activate_error_injection_payload_req_fuzzer', 'decode_nsm_event_acknowledgement_fuzzer', 'decode_nsm_provide_token_req_fuzzer', 'decode_get_histogram_format_resp_fuzzer', 'decode_get_error_injection_mode_v1_req_fuzzer', 'decode_get_error_injection_payload_resp_fuzzer', 'decode_set_current_error_injection_types_v1_req_fuzzer', 'decode_common_req_fuzzer', 'decode_get_fpga_diagnostics_settings_resp_fuzzer', 'decode_long_running_event_fuzzer', 'decode_nsm_set_event_subscription_resp_fuzzer', 'decode_nsm_rediscovery_event_fuzzer', 'decode_set_error_injection_mode_v1_resp_fuzzer', 'decode_nsm_event_fuzzer', 'decode_nsm_query_device_ids_req_fuzzer', 'decode_set_error_injection_payload_req_fuzzer', 'decode_long_running_resp_with_data_fuzzer', 'decode_nsm_disable_tokens_resp_fuzzer', 'decode_nsm_set_event_subscription_req_fuzzer', 'decode_activate_error_injection_payload_resp_fuzzer', 'decode_nsm_query_token_status_resp_fuzzer', 'decode_nsm_provide_token_resp_fuzzer', 'decode_set_error_injection_mode_v1_req_fuzzer', 'decode_nsm_get_event_subscription_resp_fuzzer', 'decode_reason_code_and_cc_fuzzer', 'decode_nsm_get_event_subscription_req_fuzzer', 'decode_nsm_query_token_parameters_resp_fuzzer', 'decode_ping_resp_fuzzer']
/src/nsmd/libnsm/base.c	['decode_get_error_injection_types_v1_resp_fuzzer', 'decode_set_current_error_injection_types_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer', 'decode_get_power_supply_status_resp_fuzzer', 'decode_get_error_injection_types_v1_req_fuzzer', 'decode_get_histogram_format_req_fuzzer', 'decode_get_histogram_data_req_fuzzer', 'decode_long_running_resp_fuzzer', 'decode_get_error_injection_payload_req_fuzzer', 'decode_common_resp_fuzzer', 'decode_query_device_identification_resp_fuzzer', 'decode_get_histogram_data_resp_fuzzer', 'decode_nsm_event_with_data_fuzzer', 'decode_set_error_injection_payload_resp_fuzzer', 'decode_get_error_injection_mode_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_resp_fuzzer', 'decode_activate_error_injection_payload_req_fuzzer', 'decode_nsm_event_acknowledgement_fuzzer', 'decode_get_histogram_format_resp_fuzzer', 'decode_get_error_injection_mode_v1_req_fuzzer', 'decode_get_error_injection_payload_resp_fuzzer', 'decode_set_current_error_injection_types_v1_req_fuzzer', 'decode_common_req_fuzzer', 'decode_get_fpga_diagnostics_settings_resp_fuzzer', 'decode_long_running_event_fuzzer', 'decode_set_error_injection_mode_v1_resp_fuzzer', 'decode_nsm_event_fuzzer', 'decode_set_error_injection_payload_req_fuzzer', 'decode_long_running_resp_with_data_fuzzer', 'decode_nsm_disable_tokens_resp_fuzzer', 'decode_activate_error_injection_payload_resp_fuzzer', 'decode_nsm_query_token_status_resp_fuzzer', 'decode_nsm_provide_token_resp_fuzzer', 'decode_set_error_injection_mode_v1_req_fuzzer', 'decode_nsm_get_event_subscription_resp_fuzzer', 'decode_reason_code_and_cc_fuzzer', 'decode_nsm_get_event_subscription_req_fuzzer', 'decode_nsm_query_token_parameters_resp_fuzzer', 'decode_ping_resp_fuzzer']	['decode_get_error_injection_types_v1_resp_fuzzer', 'decode_set_current_error_injection_types_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer', 'decode_get_power_supply_status_resp_fuzzer', 'decode_get_error_injection_types_v1_req_fuzzer', 'decode_get_histogram_format_req_fuzzer', 'decode_get_histogram_data_req_fuzzer', 'decode_long_running_resp_fuzzer', 'decode_get_error_injection_payload_req_fuzzer', 'decode_common_resp_fuzzer', 'decode_query_device_identification_resp_fuzzer', 'decode_get_histogram_data_resp_fuzzer', 'decode_nsm_event_with_data_fuzzer', 'decode_set_error_injection_payload_resp_fuzzer', 'decode_get_error_injection_mode_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_resp_fuzzer', 'decode_activate_error_injection_payload_req_fuzzer', 'decode_nsm_event_acknowledgement_fuzzer', 'decode_get_histogram_format_resp_fuzzer', 'decode_get_error_injection_mode_v1_req_fuzzer', 'decode_get_error_injection_payload_resp_fuzzer', 'decode_set_current_error_injection_types_v1_req_fuzzer', 'decode_common_req_fuzzer', 'decode_get_fpga_diagnostics_settings_resp_fuzzer', 'decode_long_running_event_fuzzer', 'decode_set_error_injection_mode_v1_resp_fuzzer', 'decode_nsm_event_fuzzer', 'decode_set_error_injection_payload_req_fuzzer', 'decode_long_running_resp_with_data_fuzzer', 'decode_nsm_disable_tokens_resp_fuzzer', 'decode_activate_error_injection_payload_resp_fuzzer', 'decode_nsm_query_token_status_resp_fuzzer', 'decode_nsm_provide_token_resp_fuzzer', 'decode_set_error_injection_mode_v1_req_fuzzer', 'decode_nsm_get_event_subscription_resp_fuzzer', 'decode_reason_code_and_cc_fuzzer', 'decode_nsm_get_event_subscription_req_fuzzer', 'decode_nsm_query_token_parameters_resp_fuzzer', 'decode_ping_resp_fuzzer']
/usr/local/bin/../include/c++/v1/stdexcept	[]	[]
/usr/include/x86_64-linux-gnu/bits/uintn-identity.h	['decode_get_error_injection_types_v1_resp_fuzzer', 'decode_set_current_error_injection_types_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer', 'decode_get_power_supply_status_resp_fuzzer', 'decode_get_histogram_format_req_fuzzer', 'decode_get_histogram_data_req_fuzzer', 'decode_long_running_resp_fuzzer', 'decode_get_error_injection_payload_req_fuzzer', 'decode_common_resp_fuzzer', 'decode_query_device_identification_resp_fuzzer', 'decode_get_histogram_data_resp_fuzzer', 'decode_nsm_event_with_data_fuzzer', 'decode_set_error_injection_payload_resp_fuzzer', 'decode_get_error_injection_mode_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_resp_fuzzer', 'decode_nsm_get_event_log_record_resp_fuzzer', 'decode_get_histogram_format_resp_fuzzer', 'decode_get_error_injection_payload_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_resp_fuzzer', 'decode_long_running_event_fuzzer', 'decode_nsm_rediscovery_event_fuzzer', 'decode_set_error_injection_mode_v1_resp_fuzzer', 'decode_nsm_event_fuzzer', 'decode_set_error_injection_payload_req_fuzzer', 'decode_long_running_resp_with_data_fuzzer', 'decode_nsm_disable_tokens_resp_fuzzer', 'decode_activate_error_injection_payload_resp_fuzzer', 'decode_nsm_query_token_status_resp_fuzzer', 'decode_nsm_provide_token_resp_fuzzer', 'decode_nsm_get_event_subscription_resp_fuzzer', 'decode_reason_code_and_cc_fuzzer', 'decode_nsm_query_token_parameters_resp_fuzzer', 'decode_ping_resp_fuzzer']	[]
/src/nsmd/libnsm/device-capability-discovery.c	['decode_nsm_set_current_event_sources_resp_fuzzer', 'decode_nsm_get_event_log_record_resp_fuzzer', 'decode_nsm_set_event_subscription_resp_fuzzer', 'decode_nsm_rediscovery_event_fuzzer', 'decode_nsm_set_event_subscription_req_fuzzer', 'decode_nsm_get_event_subscription_resp_fuzzer', 'decode_nsm_get_event_subscription_req_fuzzer']	['decode_nsm_set_current_event_sources_resp_fuzzer', 'decode_nsm_get_event_log_record_resp_fuzzer', 'decode_nsm_set_event_subscription_resp_fuzzer', 'decode_nsm_rediscovery_event_fuzzer', 'decode_nsm_set_event_subscription_req_fuzzer', 'decode_nsm_get_event_subscription_resp_fuzzer', 'decode_nsm_get_event_subscription_req_fuzzer']
/src/decode_get_fpga_diagnostics_settings_req_fuzzer.cc	['decode_get_fpga_diagnostics_settings_req_fuzzer']	['decode_get_fpga_diagnostics_settings_req_fuzzer']
/src/decode_nsm_query_token_status_req_fuzzer.cc	['decode_nsm_query_token_status_req_fuzzer']	['decode_nsm_query_token_status_req_fuzzer']
/src/decode_get_fpga_diagnostics_settings_wp_resp_fuzzer.cc	['decode_get_fpga_diagnostics_settings_wp_resp_fuzzer']	['decode_get_fpga_diagnostics_settings_wp_resp_fuzzer']
/src/decode_reason_code_and_cc_fuzzer.cc	['decode_reason_code_and_cc_fuzzer']	['decode_reason_code_and_cc_fuzzer']
/src/decode_nsm_get_event_log_record_resp_fuzzer.cc	['decode_nsm_get_event_log_record_resp_fuzzer']	['decode_nsm_get_event_log_record_resp_fuzzer']
/src/decode_set_error_injection_mode_v1_req_fuzzer.cc	['decode_set_error_injection_mode_v1_req_fuzzer']	['decode_set_error_injection_mode_v1_req_fuzzer']
/src/decode_set_error_injection_payload_req_fuzzer.cc	['decode_set_error_injection_payload_req_fuzzer']	['decode_set_error_injection_payload_req_fuzzer']
/src/nsmd/libnsm/device-configuration.c	['decode_get_error_injection_types_v1_resp_fuzzer', 'decode_set_current_error_injection_types_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer', 'decode_get_power_supply_status_resp_fuzzer', 'decode_get_error_injection_types_v1_req_fuzzer', 'decode_get_error_injection_payload_req_fuzzer', 'decode_get_fpga_diagnostics_settings_req_fuzzer', 'decode_set_error_injection_payload_resp_fuzzer', 'decode_get_error_injection_mode_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_resp_fuzzer', 'decode_activate_error_injection_payload_req_fuzzer', 'decode_get_error_injection_mode_v1_req_fuzzer', 'decode_get_error_injection_payload_resp_fuzzer', 'decode_set_current_error_injection_types_v1_req_fuzzer', 'decode_get_fpga_diagnostics_settings_resp_fuzzer', 'decode_set_error_injection_mode_v1_resp_fuzzer', 'decode_set_error_injection_payload_req_fuzzer', 'decode_activate_error_injection_payload_resp_fuzzer', 'decode_set_error_injection_mode_v1_req_fuzzer']	['decode_get_error_injection_types_v1_resp_fuzzer', 'decode_set_current_error_injection_types_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer', 'decode_get_power_supply_status_resp_fuzzer', 'decode_get_error_injection_types_v1_req_fuzzer', 'decode_get_error_injection_payload_req_fuzzer', 'decode_get_fpga_diagnostics_settings_req_fuzzer', 'decode_set_error_injection_payload_resp_fuzzer', 'decode_get_error_injection_mode_v1_resp_fuzzer', 'decode_get_fpga_diagnostics_settings_wp_resp_fuzzer', 'decode_activate_error_injection_payload_req_fuzzer', 'decode_get_error_injection_mode_v1_req_fuzzer', 'decode_get_error_injection_payload_resp_fuzzer', 'decode_set_current_error_injection_types_v1_req_fuzzer', 'decode_get_fpga_diagnostics_settings_resp_fuzzer', 'decode_set_error_injection_mode_v1_resp_fuzzer', 'decode_set_error_injection_payload_req_fuzzer', 'decode_activate_error_injection_payload_resp_fuzzer', 'decode_set_error_injection_mode_v1_req_fuzzer']
/src/decode_get_error_injection_payload_resp_fuzzer.cc	['decode_get_error_injection_payload_resp_fuzzer']	['decode_get_error_injection_payload_resp_fuzzer']
/src/decode_set_error_injection_mode_v1_resp_fuzzer.cc	['decode_set_error_injection_mode_v1_resp_fuzzer']	['decode_set_error_injection_mode_v1_resp_fuzzer']
/src/decode_get_error_injection_types_v1_req_fuzzer.cc	['decode_get_error_injection_types_v1_req_fuzzer']	['decode_get_error_injection_types_v1_req_fuzzer']
/usr/include/x86_64-linux-gnu/bits/byteswap.h	['decode_get_error_injection_types_v1_req_fuzzer', 'decode_get_error_injection_payload_req_fuzzer', 'decode_activate_error_injection_payload_req_fuzzer', 'decode_get_error_injection_mode_v1_req_fuzzer', 'decode_set_current_error_injection_types_v1_req_fuzzer', 'decode_common_req_fuzzer', 'decode_set_error_injection_payload_req_fuzzer', 'decode_set_error_injection_mode_v1_req_fuzzer', 'decode_nsm_get_event_subscription_resp_fuzzer', 'decode_nsm_get_event_subscription_req_fuzzer']	[]
/src/decode_common_req_fuzzer.cc	['decode_common_req_fuzzer']	['decode_common_req_fuzzer']
/src/decode_activate_error_injection_payload_resp_fuzzer.cc	['decode_activate_error_injection_payload_resp_fuzzer']	['decode_activate_error_injection_payload_resp_fuzzer']
/src/decode_nsm_provide_token_resp_fuzzer.cc	['decode_nsm_provide_token_resp_fuzzer']	['decode_nsm_provide_token_resp_fuzzer']
/src/decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer.cc	['decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer']	['decode_get_fpga_diagnostics_settings_wp_jumper_resp_fuzzer']
/src/decode_get_histogram_data_req_fuzzer.cc	['decode_get_histogram_data_req_fuzzer']	['decode_get_histogram_data_req_fuzzer']
/src/decode_nsm_set_current_event_sources_resp_fuzzer.cc	['decode_nsm_set_current_event_sources_resp_fuzzer']	['decode_nsm_set_current_event_sources_resp_fuzzer']
/src/decode_set_current_error_injection_types_v1_resp_fuzzer.cc	['decode_set_current_error_injection_types_v1_resp_fuzzer']	['decode_set_current_error_injection_types_v1_resp_fuzzer']
/src/decode_get_error_injection_payload_req_fuzzer.cc	['decode_get_error_injection_payload_req_fuzzer']	['decode_get_error_injection_payload_req_fuzzer']
/src/decode_nsm_event_acknowledgement_fuzzer.cc	['decode_nsm_event_acknowledgement_fuzzer']	['decode_nsm_event_acknowledgement_fuzzer']
/src/decode_nsm_set_event_subscription_resp_fuzzer.cc	['decode_nsm_set_event_subscription_resp_fuzzer']	['decode_nsm_set_event_subscription_resp_fuzzer']
/src/decode_set_error_injection_payload_resp_fuzzer.cc	['decode_set_error_injection_payload_resp_fuzzer']	['decode_set_error_injection_payload_resp_fuzzer']
/src/decode_nsm_event_fuzzer.cc	['decode_nsm_event_fuzzer']	['decode_nsm_event_fuzzer']
/src/decode_nsm_get_event_subscription_resp_fuzzer.cc	['decode_nsm_get_event_subscription_resp_fuzzer']	['decode_nsm_get_event_subscription_resp_fuzzer']
/src/decode_long_running_resp_fuzzer.cc	['decode_long_running_resp_fuzzer']	['decode_long_running_resp_fuzzer']
/src/decode_long_running_event_fuzzer.cc	['decode_long_running_event_fuzzer']	['decode_long_running_event_fuzzer']
/src/decode_nsm_query_device_ids_req_fuzzer.cc	['decode_nsm_query_device_ids_req_fuzzer']	['decode_nsm_query_device_ids_req_fuzzer']
/src/decode_nsm_get_event_subscription_req_fuzzer.cc	['decode_nsm_get_event_subscription_req_fuzzer']	['decode_nsm_get_event_subscription_req_fuzzer']
/src/decode_get_error_injection_mode_v1_resp_fuzzer.cc	['decode_get_error_injection_mode_v1_resp_fuzzer']	['decode_get_error_injection_mode_v1_resp_fuzzer']
/src/nsmd/libnsm/platform-environmental.c	[]	[]
/src/decode_query_device_identification_resp_fuzzer.cc	['decode_query_device_identification_resp_fuzzer']	['decode_query_device_identification_resp_fuzzer']
/src/decode_get_histogram_data_resp_fuzzer.cc	['decode_get_histogram_data_resp_fuzzer']	['decode_get_histogram_data_resp_fuzzer']
/src/decode_long_running_resp_with_data_fuzzer.cc	['decode_long_running_resp_with_data_fuzzer']	['decode_long_running_resp_with_data_fuzzer']
/src/decode_nsm_query_token_parameters_resp_fuzzer.cc	['decode_nsm_query_token_parameters_resp_fuzzer']	['decode_nsm_query_token_parameters_resp_fuzzer']
/src/nsmd/libnsm/firmware-utils.c	[]	[]
/src/decode_activate_error_injection_payload_req_fuzzer.cc	['decode_activate_error_injection_payload_req_fuzzer']	['decode_activate_error_injection_payload_req_fuzzer']
/src/decode_nsm_provide_token_req_fuzzer.cc	['decode_nsm_provide_token_req_fuzzer']	['decode_nsm_provide_token_req_fuzzer']
/src/decode_get_fpga_diagnostics_settings_resp_fuzzer.cc	['decode_get_fpga_diagnostics_settings_resp_fuzzer']	['decode_get_fpga_diagnostics_settings_resp_fuzzer']
/src/nsmd/libnsm/network-ports.c	[]	[]

Directories in report

Directory
/usr/include/x86_64-linux-gnu/bits/
/usr/local/bin/../include/c++/v1/
/src/
/src/nsmd/libnsm/