High level conclusions

Fuzzers reach 68.73% code coverage.

Fuzzer HTMLLayoutFuzzer-utf-8 is blocked:

The runtime code coverage of HTMLLayoutFuzzer-utf-8 covers 10.78% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer XMLLayoutFuzzer-utf-8 is blocked:

The runtime code coverage of XMLLayoutFuzzer-utf-8 covers 9.876% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzers reach 29.60% of cyclomatic complexity.

Fuzzers reach 15.43% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

761 / 4929

Cyclomatic complexity statically reachable by fuzzers

7698 / 26001

Runtime code coverage of functions

3388 / 4929

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

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

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

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

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

Fuzzer: XMLLayoutFuzzer-utf-8

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	82	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	82	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
81	0	EP	call site: 00000	__cxa_guard_acquire

Runtime coverage analysis

Covered functions

696

Functions that are reachable but not covered

73

Reachable functions

81

Percentage of reachable functions covered

9.88%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/XMLLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/xmllayout.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	3
/src/logging-log4cxx/src/main/cpp/level.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	4
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	1
/src/logging-log4cxx/src/main/cpp/ndc.cpp	3
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	1
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	2
/src/logging-log4cxx/src/main/cpp/mdc.cpp	3

Fuzzer: JSONLayoutFuzzer-utf-8

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	8	9.09%
gold	[1:9]	2	2.27%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	78	88.6%
All colors	88	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
3	1	LLVMFuzzerTestOneInput	call site: 00001
2	72	log4cxx::Layout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00072	apr_pool_destroy
1	11	log4cxx::helpers::OptionConverter::toBoolean(std::__1::basic_string , std::__1::allocator > const&, bool)	call site: 00011
1	39	log4cxx::helpers::WideLife >::~WideLife()	call site: 00039	__cxa_begin_catch
1	57	LLVMFuzzerTestOneInput	call site: 00057

Runtime coverage analysis

Covered functions

837

Functions that are reachable but not covered

10

Reachable functions

83

Percentage of reachable functions covered

87.95%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/JSONLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/jsonlayout.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	2
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	1
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	1
/src/logging-log4cxx/src/main/cpp/level.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	4
/src/logging-log4cxx/src/main/cpp/ndc.cpp	3
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	2
/src/logging-log4cxx/src/main/cpp/mdc.cpp	3
/src/logging-log4cxx/src/main/cpp/pool.cpp	2

Fuzzer: HTMLLayoutFuzzer-utf-8

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	103	94.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	5.50%
All colors	109	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
57	51	log4cxx::HTMLLayout::setOption(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00051	__cxa_guard_acquire
44	0	EP	call site: 00000	__cxa_guard_acquire
2	46	log4cxx::HTMLLayout::setOption(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00046

Runtime coverage analysis

Covered functions

696

Functions that are reachable but not covered

91

Reachable functions

102

Percentage of reachable functions covered

10.78%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/HTMLLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/htmllayout.cpp	6
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/timezone.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	8
/src/logging-log4cxx/src/main/cpp/simpledateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	4
/src/logging-log4cxx/src/main/cpp/level.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	1
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	1
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	1
/src/logging-log4cxx/src/main/cpp/ndc.cpp	3
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	2
/src/logging-log4cxx/src/main/cpp/mdc.cpp	3

Fuzzer: TranscoderFuzzer-wchar_t

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	13	7.83%
gold	[1:9]	25	15.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	128	77.1%
All colors	166	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
2	6	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00006
2	56	LLVMFuzzerTestOneInput	call site: 00056	fprintf
2	64	log4cxx::helpers::CharsetEncoder::createDefaultEncoder()	call site: 00064
1	13	log4cxx::helpers::WideLife >::~WideLife()	call site: 00013	__cxa_begin_catch
1	16	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00016
1	51	unsigned int decodeCodePoint (std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >::const_iterator&)	call site: 00051
1	72	log4cxx::helpers::CharsetEncoder::getDefaultEncoder()	call site: 00072
1	85	log4cxx::helpers::Transcoder::encode(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00085
1	128	log4cxx::helpers::CharsetEncoder::getEncoder(std::__1::basic_string , std::__1::allocator > const&)	call site: 00128
1	139	LLVMFuzzerTestOneInput	call site: 00139	__cxa_end_catch

Runtime coverage analysis

Covered functions

800

Functions that are reachable but not covered

11

Reachable functions

125

Percentage of reachable functions covered

91.2%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/TranscoderFuzzer.cpp	8
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	19
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	6
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	8
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	10
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/charsetencoder.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetencoder.h	1
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	1

Fuzzer: JSONLayoutFuzzer-wchar_t

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	11	9.73%
gold	[1:9]	14	12.3%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	88	77.8%
All colors	113	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
3	1	LLVMFuzzerTestOneInput	call site: 00001
2	27	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00027
2	97	log4cxx::Layout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00097	apr_pool_destroy
1	11	log4cxx::helpers::OptionConverter::toBoolean(std::__1::basic_string , std::__1::allocator > const&, bool)	call site: 00011
1	34	log4cxx::helpers::WideLife >::~WideLife()	call site: 00034	__cxa_begin_catch
1	37	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00037
1	84	LLVMFuzzerTestOneInput	call site: 00084

Runtime coverage analysis

Covered functions

849

Functions that are reachable but not covered

11

Reachable functions

112

Percentage of reachable functions covered

90.18%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/JSONLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/jsonlayout.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	2
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	1
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	2
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	8
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/level.cpp	1
/src/logging-log4cxx/src/main/cpp/ndc.cpp	3
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	2
/src/logging-log4cxx/src/main/cpp/mdc.cpp	3
/src/logging-log4cxx/src/main/cpp/pool.cpp	2

Fuzzer: /src/logging-log4cxx/src/cmake/LibFuzzerTest.cpp

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+	1	100.%
All colors	1	100

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

0

Reachable functions

1

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/cmake/LibFuzzerTest.cpp	1

Fuzzer: /src/logging-log4cxx/src/fuzzers/cpp/PatternConverterFuzzer.cpp

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	62	70.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	26	29.5%
All colors	88	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
29	58	LLVMFuzzerTestOneInput	call site: 00058
12	21	createOptions(FuzzedDataProvider*)	call site: 00021
11	5	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00005
4	0	EP	call site: 00000
3	40	LLVMFuzzerTestOneInput	call site: 00040
1	46	LLVMFuzzerTestOneInput	call site: 00046
1	50	LLVMFuzzerTestOneInput	call site: 00050
1	54	LLVMFuzzerTestOneInput	call site: 00054

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

33

Reachable functions

80

Percentage of reachable functions covered

58.75%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/PatternConverterFuzzer.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/propertiespatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/loggingeventpatternconverter.h	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/loggerpatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/namepatternconverter.h	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/classnamepatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/fulllocationpatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/linelocationpatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/messagepatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/lineseparatorpatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/methodlocationpatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/levelpatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/relativetimepatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/threadpatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/threadusernamepatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/ndcpatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/throwableinformationpatternconverter.h	2

Fuzzer: /src/logging-log4cxx/src/fuzzers/cpp/TranscoderFuzzer.cpp

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

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

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
10	0	EP	call site: 00000	fprintf
4	27	(anonymous namespace)::exerciseEncoder(std::__1::shared_ptr const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00027	__cxa_begin_catch
3	45	(anonymous namespace)::checkUTF16RoundTrip(unsigned int)	call site: 00045
2	18	(anonymous namespace)::exerciseDecoder(std::__1::shared_ptr const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00018

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

4

Reachable functions

63

Percentage of reachable functions covered

93.65%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/TranscoderFuzzer.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetencoder.h	1

Fuzzer: PatternLayoutFuzzer-wchar_t

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	539	56.6%
gold	[1:9]	321	33.7%
yellow	[10:29]	16	1.68%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	76	7.98%
All colors	952	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
183	483	log4cxx::helpers::WideLife ::operator log4cxx::helpers::ClassRegistration&()	call site: 00483	_ZN7log4cxx7helpers8WideLifeINS0_17ClassRegistrationEEC2IRFRKNS0_5ClassEvEJEQntsr3stdE7same_asINS1_IT_EETL0__EEEOSA_DpOT0_
16	350	log4cxx::helpers::OptionConverter::substVars(std::__1::basic_string , std::__1::allocator > const&, log4cxx::helpers::Properties&)	call site: 00350	__cxa_allocate_exception
14	73	log4cxx::helpers::Transcoder::encode(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00073	__cxa_throw
14	171	log4cxx::helpers::LogLog::getInstance()	call site: 00171	fwide
13	138	log4cxx::helpers::Pool::~Pool()	call site: 00138	apr_filepath_get
13	667	log4cxx::PropertyConfigurator::doConfigure(log4cxx::helpers::Properties&, std::__1::shared_ptr )	call site: 00667
12	267	log4cxx::helpers::FileInputStream::FileInputStreamPrivate::open()	call site: 00267	__cxa_allocate_exception
11	284	log4cxx::helpers::Properties::load(std::__1::shared_ptr )	call site: 00284	__cxa_allocate_exception
10	325	log4cxx::PropertyConfigurator::doConfigure(log4cxx::File const&, std::__1::shared_ptr )	call site: 00325	__cxa_end_catch
9	127	log4cxx::helpers::Transcoder::decode(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00127	__cxa_throw
9	821	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00821	__cxa_guard_acquire
8	91	log4cxx::helpers::Pool::setPool()	call site: 00091	__cxa_allocate_exception

Runtime coverage analysis

Covered functions

1087

Functions that are reachable but not covered

173

Reachable functions

728

Percentage of reachable functions covered

76.24%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/PatternLayoutFuzzer.cpp	2
/src/logging-log4cxx/src/main/cpp/configurator.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/helpers/aprinitializer.h	3
/src/logging-log4cxx/src/main/cpp/aprinitializer.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	75
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/loglog.cpp	13
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	9
/src/logging-log4cxx/src/main/cpp/system.cpp	2
/src/logging-log4cxx/src/main/cpp/exception.cpp	13
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	6
/src/logging-log4cxx/src/main/cpp/charsetencoder.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	14
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetencoder.h	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	6
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/exception.h	4
/src/logging-log4cxx/src/main/cpp/systemerrwriter.cpp	3
/src/logging-log4cxx/src/main/cpp/writer.cpp	2
/src/logging-log4cxx/src/main/cpp/consolewriter.cpp	2
/src/logging-log4cxx/src/main/cpp/loader.cpp	5
/src/logging-log4cxx/src/main/cpp/class.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/singletonholder.h	2
/src/logging-log4cxx/src/main/cpp/properties.cpp	11
/usr/local/bin/../include/c++/v1/sstream	4
/src/logging-log4cxx/src/main/cpp/file.cpp	7
/src/logging-log4cxx/src/main/cpp/propertyconfigurator.cpp	15
/src/logging-log4cxx/src/main/include/log4cxx/defaultloggerfactory.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/loggerfactory.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/configurator.h	1
/src/logging-log4cxx/src/main/cpp/logmanager.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/spi/repositoryselector.h	1
/src/logging-log4cxx/src/main/cpp/fileinputstream.cpp	2
/src/logging-log4cxx/src/main/cpp/inputstream.cpp	2
/src/logging-log4cxx/src/main/cpp/inputstreamreader.cpp	2
/src/logging-log4cxx/src/main/cpp/reader.cpp	3
/src/logging-log4cxx/src/main/cpp/level.cpp	11
/src/logging-log4cxx/src/main/include/log4cxx/level.h	1
/src/logging-log4cxx/src/main/cpp/asyncappender.cpp	2
/src/logging-log4cxx/src/main/cpp/classregistration.cpp	1
/src/logging-log4cxx/src/main/cpp/consoleappender.cpp	1
/src/logging-log4cxx/src/main/cpp/fileappender.cpp	1
/src/logging-log4cxx/src/main/cpp/odbcappender.cpp	1
/src/logging-log4cxx/src/main/cpp/smtpappender.cpp	1
/src/logging-log4cxx/src/main/cpp/jsonlayout.cpp	1
/src/logging-log4cxx/src/main/cpp/htmllayout.cpp	1
/src/logging-log4cxx/src/main/cpp/patternlayout.cpp	1
/src/logging-log4cxx/src/main/cpp/simplelayout.cpp	1
/src/logging-log4cxx/src/main/cpp/xmllayout.cpp	1
/src/logging-log4cxx/src/main/cpp/levelmatchfilter.cpp	1
/src/logging-log4cxx/src/main/cpp/levelrangefilter.cpp	1
/src/logging-log4cxx/src/main/cpp/stringmatchfilter.cpp	1
/src/logging-log4cxx/src/main/cpp/locationinfofilter.cpp	1
/src/logging-log4cxx/src/main/cpp/rollingfileappender.cpp	4
/src/logging-log4cxx/src/main/cpp/sizebasedtriggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/timebasedrollingpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/manualtriggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/fixedwindowrollingpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/filterbasedtriggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/domconfigurator.cpp	1
/src/logging-log4cxx/src/main/cpp/fallbackerrorhandler.cpp	1
/src/logging-log4cxx/src/main/cpp/telnetappender.cpp	1
/src/logging-log4cxx/src/main/cpp/xmlsocketappender.cpp	1
/src/logging-log4cxx/src/main/cpp/syslogappender.cpp	1
/src/logging-log4cxx/src/main/cpp/threadutility.cpp	4
/src/logging-log4cxx/src/main/cpp/stringtokenizer.cpp	4
/src/logging-log4cxx/src/main/cpp/appender.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/appender.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/propertysetter.cpp	5
/src/logging-log4cxx/src/main/cpp/optionhandler.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/config/propertysetter.h	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/rollingfileappender.h	1
/src/logging-log4cxx/src/main/cpp/rollingpolicy.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/rollingpolicy.h	1
/src/logging-log4cxx/src/main/cpp/triggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/triggeringpolicy.h	1
/src/logging-log4cxx/src/main/include/log4cxx/asyncappender.h	1
/src/logging-log4cxx/src/main/cpp/logger.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/helpers/lazyptr.h	3
/src/logging-log4cxx/src/main/cpp/appenderattachableimpl.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/spi/appenderattachable.h	2
/src/logging-log4cxx/src/main/include/log4cxx/logger.h	1
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1

Fuzzer: /src/logging-log4cxx/src/fuzzers/cpp/PatternParserFuzzer.cpp

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+	11	100.%
All colors	11	100

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

1

Reachable functions

16

Percentage of reachable functions covered

93.75%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/PatternParserFuzzer.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1

Fuzzer: DOMConfiguratorFuzzer-wchar_t

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	556	53.0%
gold	[1:9]	192	18.3%
yellow	[10:29]	12	1.14%
greenyellow	[30:49]	3	0.28%
lawngreen	50+	286	27.2%
All colors	1049	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
54	970	log4cxx::helpers::WideLife ::operator log4cxx::AsyncAppender::ClazzAsyncAppender&()	call site: 00970	__dynamic_cast
32	932	log4cxx::helpers::WideLife ::operator log4cxx::spi::AppenderAttachable::ClazzAppenderAttachable&()	call site: 00932	__cxa_guard_abort
17	128	log4cxx::helpers::Pool::setPool()	call site: 00128	__cxa_allocate_exception
16	686	log4cxx::xml::DOMConfigurator::DOMConfiguratorPrivate::parseChildrenOfLoggerElement(apr_xml_elem*, std::__1::shared_ptr , bool)	call site: 00686	__cxa_guard_acquire
16	749	log4cxx::config::PropertySetter::activate()	call site: 00749	__cxa_begin_catch
14	715	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00715	__cxa_guard_acquire
14	888	log4cxx::helpers::WideLife ::operator log4cxx::rolling::FilterBasedTriggeringPolicy::ClazzFilterBasedTriggeringPolicy&()	call site: 00888	__cxa_begin_catch
13	798	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00798
12	777	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00777
10	635	log4cxx::helpers::WideLife ::operator log4cxx::spi::LoggerFactory::ClazzLoggerFactory&()	call site: 00635	__cxa_begin_catch
10	646	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00646
9	817	log4cxx::helpers::WideLife ::operator log4cxx::AppenderSkeleton::ClazzAppenderSkeleton&()	call site: 00817

Runtime coverage analysis

Covered functions

966

Functions that are reachable but not covered

188

Reachable functions

739

Percentage of reachable functions covered

74.56%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/DOMConfiguratorFuzzer.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/xml/domconfigurator.h	1
/src/logging-log4cxx/src/main/cpp/domconfigurator.cpp	26
/src/logging-log4cxx/src/main/cpp/file.cpp	7
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	5
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	20
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	103
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/configurator.cpp	1
/src/logging-log4cxx/src/main/cpp/logmanager.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/aprinitializer.h	2
/src/logging-log4cxx/src/main/cpp/aprinitializer.cpp	7
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/loglog.cpp	14
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	7
/src/logging-log4cxx/src/main/cpp/system.cpp	1
/src/logging-log4cxx/src/main/cpp/exception.cpp	10
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/src/logging-log4cxx/src/main/cpp/charsetencoder.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetencoder.h	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/exception.h	4
/src/logging-log4cxx/src/main/cpp/systemerrwriter.cpp	3
/src/logging-log4cxx/src/main/cpp/writer.cpp	2
/src/logging-log4cxx/src/main/cpp/consolewriter.cpp	2
/src/logging-log4cxx/src/main/cpp/loader.cpp	9
/src/logging-log4cxx/src/main/include/log4cxx/spi/repositoryselector.h	1
/src/logging-log4cxx/src/main/cpp/class.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/private/string_c11.h	1
/src/logging-log4cxx/src/main/cpp/properties.cpp	2
/src/logging-log4cxx/src/main/cpp/level.cpp	11
/src/logging-log4cxx/src/main/include/log4cxx/level.h	1
/src/logging-log4cxx/src/main/cpp/asyncappender.cpp	2
/src/logging-log4cxx/src/main/cpp/classregistration.cpp	1
/src/logging-log4cxx/src/main/cpp/consoleappender.cpp	1
/src/logging-log4cxx/src/main/cpp/fileappender.cpp	1
/src/logging-log4cxx/src/main/cpp/odbcappender.cpp	1
/src/logging-log4cxx/src/main/cpp/smtpappender.cpp	3
/src/logging-log4cxx/src/main/cpp/jsonlayout.cpp	1
/src/logging-log4cxx/src/main/cpp/htmllayout.cpp	1
/src/logging-log4cxx/src/main/cpp/patternlayout.cpp	1
/src/logging-log4cxx/src/main/cpp/simplelayout.cpp	1
/src/logging-log4cxx/src/main/cpp/xmllayout.cpp	1
/src/logging-log4cxx/src/main/cpp/levelmatchfilter.cpp	1
/src/logging-log4cxx/src/main/cpp/levelrangefilter.cpp	1
/src/logging-log4cxx/src/main/cpp/stringmatchfilter.cpp	1
/src/logging-log4cxx/src/main/cpp/locationinfofilter.cpp	1
/src/logging-log4cxx/src/main/cpp/rollingfileappender.cpp	4
/src/logging-log4cxx/src/main/cpp/sizebasedtriggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/timebasedrollingpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/manualtriggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/fixedwindowrollingpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/filterbasedtriggeringpolicy.cpp	3
/src/logging-log4cxx/src/main/cpp/propertyconfigurator.cpp	1
/src/logging-log4cxx/src/main/cpp/fallbackerrorhandler.cpp	2
/src/logging-log4cxx/src/main/cpp/telnetappender.cpp	1
/src/logging-log4cxx/src/main/cpp/xmlsocketappender.cpp	1
/src/logging-log4cxx/src/main/cpp/syslogappender.cpp	1
/src/logging-log4cxx/src/main/cpp/threadutility.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/singletonholder.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/loggerfactory.h	1
/src/logging-log4cxx/src/main/cpp/propertysetter.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	1
/src/logging-log4cxx/src/main/include/log4cxx/config/propertysetter.h	1
/src/logging-log4cxx/src/main/cpp/logger.cpp	4
/src/logging-log4cxx/src/main/cpp/appender.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/appender.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/optionhandler.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/filter.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/errorhandler.h	1
/src/logging-log4cxx/src/main/cpp/appenderskeleton.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/appenderskeleton.h	1
/src/logging-log4cxx/src/main/cpp/rollingpolicy.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/rollingpolicy.h	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/rollingfileappender.h	1
/src/logging-log4cxx/src/main/cpp/triggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/triggeringpolicy.h	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/filterbasedtriggeringpolicy.h	1
/src/logging-log4cxx/src/main/cpp/filter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/net/smtpappender.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/triggeringeventevaluator.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/appenderattachable.h	3
/src/logging-log4cxx/src/main/include/log4cxx/asyncappender.h	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/lazyptr.h	2
/src/logging-log4cxx/src/main/cpp/appenderattachableimpl.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/spi/configurator.h	1

Fuzzer: /src/logging-log4cxx/src/fuzzers/cpp/HTMLLayoutFuzzer.cpp

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	25	92.5%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	2	7.40%
All colors	27	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
15	0	EP	call site: 00000
10	16	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00016

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

2

Reachable functions

32

Percentage of reachable functions covered

93.75%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/HTMLLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1

Fuzzer: PatternConverterFuzzer-utf-8

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	99	29.4%
gold	[1:9]	56	16.6%
yellow	[10:29]	21	6.25%
greenyellow	[30:49]	4	1.19%
lawngreen	50+	156	46.4%
All colors	336	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
30	110	log4cxx::helpers::Pool::setPool()	call site: 00110	__cxa_allocate_exception
15	172	unsigned int decodeCodePoint (std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >::const_iterator&)	call site: 00172	fputws
4	30	LLVMFuzzerTestOneInput	call site: 00030
4	72	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00072	__cxa_throw
4	205	LLVMFuzzerTestOneInput	call site: 00205
3	65	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00065	__cxa_allocate_exception
3	168	isConsoleWide(_IO_FILE*)	call site: 00168
3	320	LLVMFuzzerTestOneInput	call site: 00320
3	332	LLVMFuzzerTestOneInput	call site: 00332
2	162	log4cxx::helpers::LogLog::emit_log(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00162
2	223	log4cxx::pattern::DatePatternConverter::getDateFormat(std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)	call site: 00223	__cxa_end_catch
2	280	LLVMFuzzerTestOneInput	call site: 00280

Runtime coverage analysis

Covered functions

982

Functions that are reachable but not covered

93

Reachable functions

292

Percentage of reachable functions covered

68.15%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/PatternConverterFuzzer.cpp	2
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	7
/src/logging-log4cxx/src/main/cpp/level.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	24
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/cpp/propertiespatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/cpp/loggingeventpatternconverter.cpp	3
/src/logging-log4cxx/src/main/cpp/patternconverter.cpp	3
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/pattern/propertiespatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/loggingeventpatternconverter.h	1
/src/logging-log4cxx/src/main/cpp/loggerpatternconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/namepatternconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/nameabbreviator.cpp	3
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	4
/src/logging-log4cxx/src/main/cpp/loglog.cpp	7
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/system.cpp	1
/src/logging-log4cxx/src/main/cpp/exception.cpp	6
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/src/logging-log4cxx/src/main/cpp/aprinitializer.cpp	6
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/exception.h	2
/src/logging-log4cxx/src/main/cpp/systemerrwriter.cpp	3
/src/logging-log4cxx/src/main/cpp/writer.cpp	2
/src/logging-log4cxx/src/main/cpp/consolewriter.cpp	2
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	5
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/loggerpatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/namepatternconverter.h	1
/src/logging-log4cxx/src/main/cpp/classnamepatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/classnamepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/datepatternconverter.cpp	4
/src/logging-log4cxx/src/main/cpp/cacheddateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/timezone.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/timezone.h	1
/src/logging-log4cxx/src/main/cpp/fulllocationpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/fulllocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/linelocationpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/linelocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/messagepatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/messagepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/lineseparatorpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/lineseparatorpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/methodlocationpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/methodlocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/levelpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/levelpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/relativetimepatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/relativetimepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/threadpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/threadpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/threadusernamepatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/threadusernamepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/ndcpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/ndcpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/throwableinformationpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/throwableinformationpatternconverter.h	2

Fuzzer: TranscoderFuzzer-utf-8

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

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

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
2	23	LLVMFuzzerTestOneInput	call site: 00023	fprintf
1	63	log4cxx::helpers::CharsetEncoder::getEncoder(std::__1::basic_string , std::__1::allocator > const&)	call site: 00063
1	73	LLVMFuzzerTestOneInput	call site: 00073	__cxa_end_catch
1	103	unsigned int decodeCodePoint (std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >::const_iterator&)	call site: 00103

Runtime coverage analysis

Covered functions

788

Functions that are reachable but not covered

4

Reachable functions

87

Percentage of reachable functions covered

95.4%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/TranscoderFuzzer.cpp	7
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	19
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	10
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	2
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/charsetencoder.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetencoder.h	1

Fuzzer: DOMConfiguratorFuzzer-utf-8

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	555	54.9%
gold	[1:9]	154	15.2%
yellow	[10:29]	1	0.09%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	300	29.7%
All colors	1010	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
54	931	log4cxx::helpers::WideLife ::operator log4cxx::AsyncAppender::ClazzAsyncAppender&()	call site: 00931	__dynamic_cast
32	893	log4cxx::helpers::WideLife ::operator log4cxx::spi::AppenderAttachable::ClazzAppenderAttachable&()	call site: 00893	__cxa_guard_abort
16	647	log4cxx::xml::DOMConfigurator::DOMConfiguratorPrivate::parseChildrenOfLoggerElement(apr_xml_elem*, std::__1::shared_ptr , bool)	call site: 00647	__cxa_guard_acquire
16	710	log4cxx::config::PropertySetter::activate()	call site: 00710	__cxa_begin_catch
14	71	log4cxx::helpers::Pool::setPool()	call site: 00071	__cxa_allocate_exception
14	676	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00676	__cxa_guard_acquire
14	849	log4cxx::helpers::WideLife ::operator log4cxx::rolling::FilterBasedTriggeringPolicy::ClazzFilterBasedTriggeringPolicy&()	call site: 00849	__cxa_begin_catch
13	759	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00759
12	738	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00738
10	596	log4cxx::helpers::WideLife ::operator log4cxx::spi::LoggerFactory::ClazzLoggerFactory&()	call site: 00596	__cxa_begin_catch
10	607	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00607
9	131	isConsoleWide(_IO_FILE*)	call site: 00131

Runtime coverage analysis

Covered functions

937

Functions that are reachable but not covered

199

Reachable functions

705

Percentage of reachable functions covered

71.77%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/DOMConfiguratorFuzzer.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/xml/domconfigurator.h	1
/src/logging-log4cxx/src/main/cpp/domconfigurator.cpp	26
/src/logging-log4cxx/src/main/cpp/file.cpp	7
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	20
/src/logging-log4cxx/src/main/cpp/configurator.cpp	1
/src/logging-log4cxx/src/main/cpp/logmanager.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/aprinitializer.h	2
/src/logging-log4cxx/src/main/cpp/aprinitializer.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	95
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/loglog.cpp	14
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	7
/src/logging-log4cxx/src/main/cpp/system.cpp	1
/src/logging-log4cxx/src/main/cpp/exception.cpp	10
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/exception.h	4
/src/logging-log4cxx/src/main/cpp/systemerrwriter.cpp	3
/src/logging-log4cxx/src/main/cpp/writer.cpp	2
/src/logging-log4cxx/src/main/cpp/consolewriter.cpp	2
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	5
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	2
/src/logging-log4cxx/src/main/cpp/loader.cpp	9
/src/logging-log4cxx/src/main/include/log4cxx/spi/repositoryselector.h	1
/src/logging-log4cxx/src/main/cpp/class.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/private/string_c11.h	1
/src/logging-log4cxx/src/main/cpp/properties.cpp	2
/src/logging-log4cxx/src/main/cpp/level.cpp	11
/src/logging-log4cxx/src/main/include/log4cxx/level.h	1
/src/logging-log4cxx/src/main/cpp/asyncappender.cpp	2
/src/logging-log4cxx/src/main/cpp/classregistration.cpp	1
/src/logging-log4cxx/src/main/cpp/consoleappender.cpp	1
/src/logging-log4cxx/src/main/cpp/fileappender.cpp	1
/src/logging-log4cxx/src/main/cpp/odbcappender.cpp	1
/src/logging-log4cxx/src/main/cpp/smtpappender.cpp	3
/src/logging-log4cxx/src/main/cpp/jsonlayout.cpp	1
/src/logging-log4cxx/src/main/cpp/htmllayout.cpp	1
/src/logging-log4cxx/src/main/cpp/patternlayout.cpp	1
/src/logging-log4cxx/src/main/cpp/simplelayout.cpp	1
/src/logging-log4cxx/src/main/cpp/xmllayout.cpp	1
/src/logging-log4cxx/src/main/cpp/levelmatchfilter.cpp	1
/src/logging-log4cxx/src/main/cpp/levelrangefilter.cpp	1
/src/logging-log4cxx/src/main/cpp/stringmatchfilter.cpp	1
/src/logging-log4cxx/src/main/cpp/locationinfofilter.cpp	1
/src/logging-log4cxx/src/main/cpp/rollingfileappender.cpp	4
/src/logging-log4cxx/src/main/cpp/sizebasedtriggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/timebasedrollingpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/manualtriggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/fixedwindowrollingpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/filterbasedtriggeringpolicy.cpp	3
/src/logging-log4cxx/src/main/cpp/propertyconfigurator.cpp	1
/src/logging-log4cxx/src/main/cpp/fallbackerrorhandler.cpp	2
/src/logging-log4cxx/src/main/cpp/telnetappender.cpp	1
/src/logging-log4cxx/src/main/cpp/xmlsocketappender.cpp	1
/src/logging-log4cxx/src/main/cpp/syslogappender.cpp	1
/src/logging-log4cxx/src/main/cpp/threadutility.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/singletonholder.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/loggerfactory.h	1
/src/logging-log4cxx/src/main/cpp/propertysetter.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	1
/src/logging-log4cxx/src/main/include/log4cxx/config/propertysetter.h	1
/src/logging-log4cxx/src/main/cpp/logger.cpp	4
/src/logging-log4cxx/src/main/cpp/appender.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/appender.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/optionhandler.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/filter.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/errorhandler.h	1
/src/logging-log4cxx/src/main/cpp/appenderskeleton.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/appenderskeleton.h	1
/src/logging-log4cxx/src/main/cpp/rollingpolicy.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/rollingpolicy.h	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/rollingfileappender.h	1
/src/logging-log4cxx/src/main/cpp/triggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/triggeringpolicy.h	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/filterbasedtriggeringpolicy.h	1
/src/logging-log4cxx/src/main/cpp/filter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/net/smtpappender.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/triggeringeventevaluator.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/appenderattachable.h	3
/src/logging-log4cxx/src/main/include/log4cxx/asyncappender.h	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/lazyptr.h	2
/src/logging-log4cxx/src/main/cpp/appenderattachableimpl.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/spi/configurator.h	1

Fuzzer: PatternLayoutFuzzer-utf-8

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	536	58.5%
gold	[1:9]	302	32.9%
yellow	[10:29]	16	1.74%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	62	6.76%
All colors	916	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
183	447	log4cxx::helpers::WideLife ::operator log4cxx::helpers::ClassRegistration&()	call site: 00447	_ZN7log4cxx7helpers8WideLifeINS0_17ClassRegistrationEEC2IRFRKNS0_5ClassEvEJEQntsr3stdE7same_asINS1_IT_EETL0__EEEOSA_DpOT0_
17	62	log4cxx::helpers::Pool::setPool()	call site: 00062	__cxa_allocate_exception
17	114	log4cxx::helpers::LogLog::getInstance()	call site: 00114	fwide
16	314	log4cxx::helpers::OptionConverter::substVars(std::__1::basic_string , std::__1::allocator > const&, log4cxx::helpers::Properties&)	call site: 00314	__cxa_allocate_exception
13	81	log4cxx::helpers::Pool::~Pool()	call site: 00081	apr_filepath_get
13	133	log4cxx::helpers::ByteBuffer::increment_position(unsigned long)	call site: 00133	fputws
13	631	log4cxx::PropertyConfigurator::doConfigure(log4cxx::helpers::Properties&, std::__1::shared_ptr )	call site: 00631
11	47	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00047	__cxa_allocate_exception
11	248	log4cxx::helpers::Properties::load(std::__1::shared_ptr )	call site: 00248	__cxa_allocate_exception
10	289	log4cxx::PropertyConfigurator::doConfigure(log4cxx::File const&, std::__1::shared_ptr )	call site: 00289	__cxa_end_catch
9	786	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00786	__cxa_guard_acquire
8	654	log4cxx::PropertyConfigurator::parseLogger(log4cxx::helpers::Properties&, std::__1::shared_ptr &, std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&, bool)	call site: 00654	__cxa_allocate_exception

Runtime coverage analysis

Covered functions

1068

Functions that are reachable but not covered

169

Reachable functions

688

Percentage of reachable functions covered

75.44%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/PatternLayoutFuzzer.cpp	2
/src/logging-log4cxx/src/main/cpp/configurator.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/helpers/aprinitializer.h	3
/src/logging-log4cxx/src/main/cpp/aprinitializer.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	67
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/loglog.cpp	13
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	9
/src/logging-log4cxx/src/main/cpp/system.cpp	2
/src/logging-log4cxx/src/main/cpp/exception.cpp	12
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	7
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	6
/src/logging-log4cxx/src/main/include/log4cxx/helpers/exception.h	3
/src/logging-log4cxx/src/main/cpp/systemerrwriter.cpp	3
/src/logging-log4cxx/src/main/cpp/writer.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	14
/src/logging-log4cxx/src/main/cpp/consolewriter.cpp	2
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	5
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	2
/src/logging-log4cxx/src/main/cpp/loader.cpp	5
/src/logging-log4cxx/src/main/cpp/class.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/singletonholder.h	2
/src/logging-log4cxx/src/main/cpp/properties.cpp	11
/usr/local/bin/../include/c++/v1/sstream	4
/src/logging-log4cxx/src/main/cpp/file.cpp	7
/src/logging-log4cxx/src/main/cpp/propertyconfigurator.cpp	15
/src/logging-log4cxx/src/main/include/log4cxx/defaultloggerfactory.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/loggerfactory.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/configurator.h	1
/src/logging-log4cxx/src/main/cpp/logmanager.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/spi/repositoryselector.h	1
/src/logging-log4cxx/src/main/cpp/fileinputstream.cpp	2
/src/logging-log4cxx/src/main/cpp/inputstream.cpp	2
/src/logging-log4cxx/src/main/cpp/inputstreamreader.cpp	2
/src/logging-log4cxx/src/main/cpp/reader.cpp	3
/src/logging-log4cxx/src/main/cpp/level.cpp	11
/src/logging-log4cxx/src/main/include/log4cxx/level.h	1
/src/logging-log4cxx/src/main/cpp/asyncappender.cpp	2
/src/logging-log4cxx/src/main/cpp/classregistration.cpp	1
/src/logging-log4cxx/src/main/cpp/consoleappender.cpp	1
/src/logging-log4cxx/src/main/cpp/fileappender.cpp	1
/src/logging-log4cxx/src/main/cpp/odbcappender.cpp	1
/src/logging-log4cxx/src/main/cpp/smtpappender.cpp	1
/src/logging-log4cxx/src/main/cpp/jsonlayout.cpp	1
/src/logging-log4cxx/src/main/cpp/htmllayout.cpp	1
/src/logging-log4cxx/src/main/cpp/patternlayout.cpp	1
/src/logging-log4cxx/src/main/cpp/simplelayout.cpp	1
/src/logging-log4cxx/src/main/cpp/xmllayout.cpp	1
/src/logging-log4cxx/src/main/cpp/levelmatchfilter.cpp	1
/src/logging-log4cxx/src/main/cpp/levelrangefilter.cpp	1
/src/logging-log4cxx/src/main/cpp/stringmatchfilter.cpp	1
/src/logging-log4cxx/src/main/cpp/locationinfofilter.cpp	1
/src/logging-log4cxx/src/main/cpp/rollingfileappender.cpp	4
/src/logging-log4cxx/src/main/cpp/sizebasedtriggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/timebasedrollingpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/manualtriggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/fixedwindowrollingpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/filterbasedtriggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/domconfigurator.cpp	1
/src/logging-log4cxx/src/main/cpp/fallbackerrorhandler.cpp	1
/src/logging-log4cxx/src/main/cpp/telnetappender.cpp	1
/src/logging-log4cxx/src/main/cpp/xmlsocketappender.cpp	1
/src/logging-log4cxx/src/main/cpp/syslogappender.cpp	1
/src/logging-log4cxx/src/main/cpp/threadutility.cpp	4
/src/logging-log4cxx/src/main/cpp/stringtokenizer.cpp	4
/src/logging-log4cxx/src/main/cpp/appender.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/appender.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/propertysetter.cpp	5
/src/logging-log4cxx/src/main/cpp/optionhandler.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/config/propertysetter.h	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/rollingfileappender.h	1
/src/logging-log4cxx/src/main/cpp/rollingpolicy.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/rollingpolicy.h	1
/src/logging-log4cxx/src/main/cpp/triggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/triggeringpolicy.h	1
/src/logging-log4cxx/src/main/include/log4cxx/asyncappender.h	1
/src/logging-log4cxx/src/main/cpp/logger.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/helpers/lazyptr.h	3
/src/logging-log4cxx/src/main/cpp/appenderattachableimpl.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/spi/appenderattachable.h	2
/src/logging-log4cxx/src/main/include/log4cxx/logger.h	1
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1

Fuzzer: PatternParserFuzzer-wchar_t

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	61	24.2%
gold	[1:9]	77	30.5%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	114	45.2%
All colors	252	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
17	162	log4cxx::helpers::Pool::setPool()	call site: 00162	__cxa_allocate_exception
13	181	log4cxx::helpers::Pool::~Pool()	call site: 00181	apr_filepath_get
4	52	log4cxx::pattern::PatternParser::parse(std::__1::basic_string , std::__1::allocator > const&, std::__1::map , std::__1::allocator >, std::__1::function (std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)>, std::__1::less , std::__1::allocator > >, std::__1::allocator , std::__1::allocator > const, std::__1::function (std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)> > > > const&)	call site: 00052	__cxa_guard_acquire
4	124	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00124	__cxa_throw
3	88	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00088	__cxa_allocate_exception
2	6	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00006
2	99	log4cxx::helpers::CharsetEncoder::createDefaultEncoder()	call site: 00099
2	120	log4cxx::helpers::Transcoder::encode(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00120
2	216	log4cxx::helpers::LogLog::emit_log(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00216
1	13	log4cxx::helpers::WideLife >::~WideLife()	call site: 00013	__cxa_begin_catch
1	16	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00016
1	47	LLVMFuzzerTestOneInput	call site: 00047

Runtime coverage analysis

Covered functions

967

Functions that are reachable but not covered

42

Reachable functions

248

Percentage of reachable functions covered

83.06%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/PatternParserFuzzer.cpp	2
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	5
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	31
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/level.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	1
/src/logging-log4cxx/src/main/cpp/patternparser.cpp	7
/src/logging-log4cxx/src/main/cpp/formattinginfo.cpp	4
/src/logging-log4cxx/src/main/cpp/literalpatternconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/loglog.cpp	6
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/system.cpp	1
/src/logging-log4cxx/src/main/cpp/exception.cpp	6
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/src/logging-log4cxx/src/main/cpp/charsetencoder.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetencoder.h	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/cpp/aprinitializer.cpp	6
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/exception.h	2
/src/logging-log4cxx/src/main/cpp/systemerrwriter.cpp	3
/src/logging-log4cxx/src/main/cpp/writer.cpp	2
/src/logging-log4cxx/src/main/cpp/consolewriter.cpp	2
/src/logging-log4cxx/src/main/cpp/patternconverter.cpp	1

Fuzzer: /src/logging-log4cxx/src/fuzzers/cpp/TimeBasedRollingPolicyFuzzer.cpp

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	23	88.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	11.5%
All colors	26	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
14	0	EP	call site: 00000
5	20	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00020	remove
4	15	log4cxx::Logger::isDebugEnabledFor(std::__1::shared_ptr const&)	call site: 00015

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

2

Reachable functions

43

Percentage of reachable functions covered

95.35%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/TimeBasedRollingPolicyFuzzer.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/logger.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1

Fuzzer: /src/logging-log4cxx/src/fuzzers/cpp/XMLLayoutFuzzer.cpp

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	20	90.9%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	2	9.09%
All colors	22	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
10	0	EP	call site: 00000
10	11	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00011

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

1

Reachable functions

32

Percentage of reachable functions covered

96.88%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/XMLLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1

Fuzzer: /src/logging-log4cxx/src/cmake/LibFuzzerTest.cpp

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+	1	100.%
All colors	1	100

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

0

Reachable functions

1

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/cmake/LibFuzzerTest.cpp	1

Fuzzer: /src/logging-log4cxx/src/cmake/LibFuzzerTest.cpp

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+	1	100.%
All colors	1	100

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

0

Reachable functions

1

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.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/cmake/LibFuzzerTest.cpp	1

Fuzzer: /src/logging-log4cxx/src/fuzzers/cpp/JSONLayoutFuzzer.cpp

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	28	93.3%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	2	6.66%
All colors	30	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
18	0	EP	call site: 00000
10	19	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00019

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

1

Reachable functions

30

Percentage of reachable functions covered

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/JSONLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1

Fuzzer: XMLLayoutFuzzer-wchar_t

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	10	9.09%
gold	[1:9]	14	12.7%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	86	78.1%
All colors	110	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
3	1	LLVMFuzzerTestOneInput	call site: 00001
2	23	log4cxx::Layout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00023	apr_pool_destroy
2	44	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00044
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	52	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00052
1	83	LLVMFuzzerTestOneInput	call site: 00083

Runtime coverage analysis

Covered functions

802

Functions that are reachable but not covered

11

Reachable functions

110

Percentage of reachable functions covered

90.0%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/XMLLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/xmllayout.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	3
/src/logging-log4cxx/src/main/cpp/level.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	8
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	1
/src/logging-log4cxx/src/main/cpp/ndc.cpp	3
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	2
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	4
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	2
/src/logging-log4cxx/src/main/cpp/mdc.cpp	3

Fuzzer: /src/logging-log4cxx/src/fuzzers/cpp/DOMConfiguratorFuzzer.cpp

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	4	66.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	2	33.3%
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
4	0	EP	call site: 00000	fopen

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

3

Reachable functions

8

Percentage of reachable functions covered

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/DOMConfiguratorFuzzer.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/xml/domconfigurator.h	1

Fuzzer: TimeBasedRollingPolicyFuzzer-wchar_t

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	192	42.5%
gold	[1:9]	69	15.2%
yellow	[10:29]	2	0.44%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	188	41.6%
All colors	451	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
31	379	log4cxx::helpers::WideLife ::operator log4cxx::helpers::Object::ClazzObject&()	call site: 00379	__cxa_guard_abort
30	160	log4cxx::helpers::Pool::setPool()	call site: 00160	__cxa_allocate_exception
14	142	log4cxx::helpers::Transcoder::encode(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00142	__cxa_throw
10	258	log4cxx::WriterAppender::WriterAppenderPriv::close()	call site: 00258	__cxa_end_catch
8	319	log4cxx::FileAppender::setFileInternal(std::__1::basic_string , std::__1::allocator > const&, bool, bool, unsigned long)	call site: 00319
8	354	log4cxx::FileAppender::activateOptionsInternal()	call site: 00354	__cxa_end_catch
7	216	log4cxx::helpers::SystemErrWriter::write(std::__1::basic_string , std::__1::allocator > const&)	call site: 00216	fwide
7	330	log4cxx::File::mkdirs() const	call site: 00330	__cxa_rethrow
6	116	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00116	__cxa_allocate_exception
5	25	LLVMFuzzerTestOneInput	call site: 00025
5	210	log4cxx::helpers::LogLog::getInstance()	call site: 00210
5	347	log4cxx::WriterAppender::WriterAppenderPriv::writeHeader()	call site: 00347	__clang_call_terminate

Runtime coverage analysis

Covered functions

1245

Functions that are reachable but not covered

100

Reachable functions

432

Percentage of reachable functions covered

76.85%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/TimeBasedRollingPolicyFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/patternlayout.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	5
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/optionhandler.cpp	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/cpp/layout.cpp	3
/src/logging-log4cxx/src/main/cpp/rollingfileappender.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/appender.h	2
/src/logging-log4cxx/src/main/cpp/fileappender.cpp	9
/src/logging-log4cxx/src/main/cpp/writerappender.cpp	7
/src/logging-log4cxx/src/main/cpp/appenderskeleton.cpp	1
/src/logging-log4cxx/src/main/cpp/timebasedrollingpolicy.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/rollingpolicy.h	2
/src/logging-log4cxx/src/main/cpp/rollingpolicybase.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/rolling/triggeringpolicy.h	1
/src/logging-log4cxx/src/main/cpp/triggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/logmanager.cpp	5
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	9
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	27
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/aprinitializer.h	2
/src/logging-log4cxx/src/main/cpp/aprinitializer.cpp	7
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/loglog.cpp	11
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/system.cpp	1
/src/logging-log4cxx/src/main/cpp/exception.cpp	6
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/src/logging-log4cxx/src/main/cpp/charsetencoder.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetencoder.h	1
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/exception.h	2
/src/logging-log4cxx/src/main/cpp/systemerrwriter.cpp	3
/src/logging-log4cxx/src/main/cpp/writer.cpp	4
/src/logging-log4cxx/src/main/cpp/consolewriter.cpp	2
/src/logging-log4cxx/src/main/cpp/loader.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/repositoryselector.h	1
/src/logging-log4cxx/src/main/cpp/class.cpp	1
/src/logging-log4cxx/src/main/cpp/rollingpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/rolloverdescription.cpp	4
/src/logging-log4cxx/src/main/cpp/action.cpp	1
/src/logging-log4cxx/src/main/cpp/file.cpp	10
/src/logging-log4cxx/src/main/cpp/outputstream.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/private/writerappender_priv.h	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/singletonholder.h	1
/src/logging-log4cxx/src/main/cpp/threadutility.cpp	11
/src/logging-log4cxx/src/main/include/log4cxx/helpers/threadutility.h	1
/src/logging-log4cxx/src/main/include/log4cxx/logger.h	1
/src/logging-log4cxx/src/main/cpp/logger.cpp	5
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	7
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/lazyptr.h	1
/src/logging-log4cxx/src/main/cpp/appenderattachableimpl.cpp	2
/src/logging-log4cxx/src/main/cpp/appender.cpp	1

Fuzzer: PatternParserFuzzer-utf-8

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	70	32.8%
gold	[1:9]	53	24.8%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	90	42.2%
All colors	213	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
17	105	log4cxx::helpers::Pool::setPool()	call site: 00105	__cxa_allocate_exception
15	169	unsigned int decodeCodePoint (std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >::const_iterator&)	call site: 00169	fputws
13	124	log4cxx::helpers::Pool::~Pool()	call site: 00124	apr_filepath_get
4	24	log4cxx::pattern::PatternParser::parse(std::__1::basic_string , std::__1::allocator > const&, std::__1::map , std::__1::allocator >, std::__1::function (std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)>, std::__1::less , std::__1::allocator > >, std::__1::allocator , std::__1::allocator > const, std::__1::function (std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)> > > > const&)	call site: 00024	__cxa_guard_acquire
4	67	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00067	__cxa_throw
3	60	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00060	__cxa_allocate_exception
3	165	isConsoleWide(_IO_FILE*)	call site: 00165
2	159	log4cxx::helpers::LogLog::emit_log(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00159
1	10	log4cxx::helpers::WideLife >::~WideLife()	call site: 00010	__cxa_begin_catch
1	19	LLVMFuzzerTestOneInput	call site: 00019
1	29	log4cxx::helpers::WideLife >::~WideLife()	call site: 00029	__cxa_guard_release
1	32	log4cxx::helpers::WideLife >::operator std::__1::shared_ptr &()	call site: 00032	__cxa_guard_abort

Runtime coverage analysis

Covered functions

936

Functions that are reachable but not covered

62

Reachable functions

214

Percentage of reachable functions covered

71.03%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/PatternParserFuzzer.cpp	2
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	7
/src/logging-log4cxx/src/main/cpp/level.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	23
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/cpp/patternparser.cpp	7
/src/logging-log4cxx/src/main/cpp/formattinginfo.cpp	4
/src/logging-log4cxx/src/main/cpp/literalpatternconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/loglog.cpp	6
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/system.cpp	1
/src/logging-log4cxx/src/main/cpp/exception.cpp	6
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/cpp/aprinitializer.cpp	6
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/exception.h	2
/src/logging-log4cxx/src/main/cpp/systemerrwriter.cpp	3
/src/logging-log4cxx/src/main/cpp/writer.cpp	2
/src/logging-log4cxx/src/main/cpp/consolewriter.cpp	2
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	5
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	1
/src/logging-log4cxx/src/main/cpp/patternconverter.cpp	1

Fuzzer: HTMLLayoutFuzzer-wchar_t

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	11	8.02%
gold	[1:9]	15	10.9%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	111	81.0%
All colors	137	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
3	1	LLVMFuzzerTestOneInput	call site: 00001
2	35	log4cxx::Layout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00035	apr_pool_destroy
2	57	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00057
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	47	log4cxx::helpers::OptionConverter::toBoolean(std::__1::basic_string , std::__1::allocator > const&, bool)	call site: 00047
1	65	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00065
1	111	LLVMFuzzerTestOneInput	call site: 00111

Runtime coverage analysis

Covered functions

851

Functions that are reachable but not covered

11

Reachable functions

131

Percentage of reachable functions covered

91.6%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/HTMLLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/htmllayout.cpp	6
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/timezone.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	12
/src/logging-log4cxx/src/main/cpp/simpledateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	4
/src/logging-log4cxx/src/main/cpp/level.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	1
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	1
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	2
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	4
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/ndc.cpp	3
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	2
/src/logging-log4cxx/src/main/cpp/mdc.cpp	3

Fuzzer: PatternConverterFuzzer-wchar_t

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	90	24.0%
gold	[1:9]	85	22.6%
yellow	[10:29]	18	4.8%
greenyellow	[30:49]	28	7.46%
lawngreen	50+	154	41.0%
All colors	375	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
30	167	log4cxx::helpers::Pool::setPool()	call site: 00167	__cxa_allocate_exception
4	58	LLVMFuzzerTestOneInput	call site: 00058
4	129	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00129	__cxa_throw
4	244	LLVMFuzzerTestOneInput	call site: 00244
3	93	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00093	__cxa_allocate_exception
3	359	LLVMFuzzerTestOneInput	call site: 00359
3	371	LLVMFuzzerTestOneInput	call site: 00371
2	6	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00006
2	104	log4cxx::helpers::CharsetEncoder::createDefaultEncoder()	call site: 00104
2	125	log4cxx::helpers::Transcoder::encode(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00125
2	219	log4cxx::helpers::LogLog::emit_log(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00219
2	262	log4cxx::pattern::DatePatternConverter::getDateFormat(std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)	call site: 00262	__cxa_end_catch

Runtime coverage analysis

Covered functions

1015

Functions that are reachable but not covered

73

Reachable functions

326

Percentage of reachable functions covered

77.61%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/PatternConverterFuzzer.cpp	2
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	5
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	32
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/level.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/cpp/propertiespatternconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/loggingeventpatternconverter.cpp	3
/src/logging-log4cxx/src/main/cpp/patternconverter.cpp	3
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/pattern/propertiespatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/loggingeventpatternconverter.h	1
/src/logging-log4cxx/src/main/cpp/loggerpatternconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/namepatternconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/nameabbreviator.cpp	3
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	4
/src/logging-log4cxx/src/main/cpp/loglog.cpp	7
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/system.cpp	1
/src/logging-log4cxx/src/main/cpp/exception.cpp	6
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/src/logging-log4cxx/src/main/cpp/charsetencoder.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetencoder.h	1
/src/logging-log4cxx/src/main/cpp/aprinitializer.cpp	6
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/exception.h	2
/src/logging-log4cxx/src/main/cpp/systemerrwriter.cpp	3
/src/logging-log4cxx/src/main/cpp/writer.cpp	2
/src/logging-log4cxx/src/main/cpp/consolewriter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/loggerpatternconverter.h	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/namepatternconverter.h	1
/src/logging-log4cxx/src/main/cpp/classnamepatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/classnamepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/datepatternconverter.cpp	4
/src/logging-log4cxx/src/main/cpp/cacheddateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/timezone.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/timezone.h	1
/src/logging-log4cxx/src/main/cpp/fulllocationpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/fulllocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/linelocationpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/linelocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/messagepatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/messagepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/lineseparatorpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/lineseparatorpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/methodlocationpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/methodlocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/levelpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/levelpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/relativetimepatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/relativetimepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/threadpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/threadpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/threadusernamepatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/threadusernamepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/ndcpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/ndcpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/throwableinformationpatternconverter.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/throwableinformationpatternconverter.h	2

Fuzzer: /src/logging-log4cxx/src/fuzzers/cpp/PatternLayoutFuzzer.cpp

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	10	50.0%
gold	[1:9]	7	35.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	15.0%
All colors	20	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	11	log4cxx::Logger::isInfoEnabledFor(std::__1::shared_ptr const&)	call site: 00011
3	16	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00016
2	8	init()	call site: 00008
1	0	EP	call site: 00000

Runtime coverage analysis

Covered functions

1886

Functions that are reachable but not covered

3

Reachable functions

36

Percentage of reachable functions covered

91.67%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/PatternLayoutFuzzer.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/logger.h	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1

Fuzzer: TimeBasedRollingPolicyFuzzer-utf-8

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	178	43.8%
gold	[1:9]	70	17.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	158	38.9%
All colors	406	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
31	335	log4cxx::helpers::WideLife ::operator log4cxx::helpers::Object::ClazzObject&()	call site: 00335	__cxa_guard_abort
30	103	log4cxx::helpers::Pool::setPool()	call site: 00103	__cxa_allocate_exception
9	161	isConsoleWide(_IO_FILE*)	call site: 00161
8	172	log4cxx::helpers::ByteBuffer::increment_position(unsigned long)	call site: 00172	fputws
8	275	log4cxx::FileAppender::setFileInternal(std::__1::basic_string , std::__1::allocator > const&, bool, bool, unsigned long)	call site: 00275
8	310	log4cxx::FileAppender::activateOptionsInternal()	call site: 00310	__cxa_end_catch
7	286	log4cxx::File::mkdirs() const	call site: 00286	__cxa_rethrow
5	25	LLVMFuzzerTestOneInput	call site: 00025
5	88	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00088	__cxa_allocate_exception
5	303	log4cxx::WriterAppender::WriterAppenderPriv::writeHeader()	call site: 00303	__clang_call_terminate
4	95	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00095	__cxa_throw
4	219	log4cxx::WriterAppender::WriterAppenderPriv::close()	call site: 00219

Runtime coverage analysis

Covered functions

1234

Functions that are reachable but not covered

95

Reachable functions

392

Percentage of reachable functions covered

75.77%

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

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/TimeBasedRollingPolicyFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/patternlayout.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	5
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/optionhandler.cpp	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/cpp/layout.cpp	3
/src/logging-log4cxx/src/main/cpp/rollingfileappender.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/appender.h	2
/src/logging-log4cxx/src/main/cpp/fileappender.cpp	9
/src/logging-log4cxx/src/main/cpp/writerappender.cpp	7
/src/logging-log4cxx/src/main/cpp/appenderskeleton.cpp	1
/src/logging-log4cxx/src/main/cpp/timebasedrollingpolicy.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/rolling/rollingpolicy.h	2
/src/logging-log4cxx/src/main/cpp/rollingpolicybase.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/rolling/triggeringpolicy.h	1
/src/logging-log4cxx/src/main/cpp/triggeringpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/logmanager.cpp	5
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/helpers/aprinitializer.h	2
/src/logging-log4cxx/src/main/cpp/aprinitializer.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	19
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/loglog.cpp	11
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/system.cpp	1
/src/logging-log4cxx/src/main/cpp/exception.cpp	6
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/exception.h	2
/src/logging-log4cxx/src/main/cpp/systemerrwriter.cpp	3
/src/logging-log4cxx/src/main/cpp/writer.cpp	4
/src/logging-log4cxx/src/main/cpp/consolewriter.cpp	2
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	5
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	1
/src/logging-log4cxx/src/main/cpp/loader.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/repositoryselector.h	1
/src/logging-log4cxx/src/main/cpp/class.cpp	1
/src/logging-log4cxx/src/main/cpp/rollingpolicy.cpp	1
/src/logging-log4cxx/src/main/cpp/rolloverdescription.cpp	4
/src/logging-log4cxx/src/main/cpp/action.cpp	1
/src/logging-log4cxx/src/main/cpp/file.cpp	10
/src/logging-log4cxx/src/main/cpp/outputstream.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/private/writerappender_priv.h	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/singletonholder.h	1
/src/logging-log4cxx/src/main/cpp/threadutility.cpp	11
/src/logging-log4cxx/src/main/include/log4cxx/helpers/threadutility.h	1
/src/logging-log4cxx/src/main/include/log4cxx/logger.h	1
/src/logging-log4cxx/src/main/cpp/logger.cpp	5
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	7
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/helpers/lazyptr.h	1
/src/logging-log4cxx/src/main/cpp/appenderattachableimpl.cpp	2
/src/logging-log4cxx/src/main/cpp/appender.cpp	1