High level conclusions

Fuzzers reach 68.18% code coverage.

Fuzzer TimeBasedRollingPolicyFuzzer-wchar_t is blocked:

The runtime code coverage of TimeBasedRollingPolicyFuzzer-wchar_t covers 10.71% 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 33.93% of cyclomatic complexity.

Fuzzers reach 17.55% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

854 / 4866

Cyclomatic complexity statically reachable by fuzzers

8654 / 25503

Runtime code coverage of functions

3318 / 4866

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: 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	56	28.2%
gold	[1:9]	53	26.7%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	89	44.9%
All colors	198	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
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
4	165	isConsoleWide(_IO_FILE*)	call site: 00165	fputws
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
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
1	64	log4cxx::helpers::RuntimeException::RuntimeException(std::__1::basic_string , std::__1::allocator > const&)	call site: 00064

Runtime coverage analysis

Covered functions

934

Functions that are reachable but not covered

47

Reachable functions

198

Percentage of reachable functions covered

76.26%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/PatternParserFuzzer.cpp	2
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	5
/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/patternconverter.cpp	1

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	105	23.8%
gold	[1:9]	92	20.9%
yellow	[10:29]	15	3.40%
greenyellow	[30:49]	15	3.40%
lawngreen	50+	213	48.4%
All colors	440	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	173	log4cxx::helpers::Pool::setPool()	call site: 00173	__cxa_allocate_exception
13	192	log4cxx::helpers::Pool::~Pool()	call site: 00192	apr_filepath_get
8	360	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00360
4	66	LLVMFuzzerTestOneInput	call site: 00066
4	135	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00135	__cxa_throw
4	255	LLVMFuzzerTestOneInput	call site: 00255
3	101	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00101	__cxa_allocate_exception
3	411	LLVMFuzzerTestOneInput	call site: 00411
3	417	log4cxx::pattern::NDCPatternConverter::format(std::__1::shared_ptr const&, std::__1::basic_string , std::__1::allocator >&, log4cxx::helpers::Pool&) const	call site: 00417
3	425	log4cxx::NDC::get(std::__1::basic_string , std::__1::allocator >&)	call site: 00425
3	435	LLVMFuzzerTestOneInput	call site: 00435
2	6	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00006

Runtime coverage analysis

Covered functions

1011

Functions that are reachable but not covered

94

Reachable functions

437

Percentage of reachable functions covered

78.49%

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

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	2
/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	2
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	5
/src/logging-log4cxx/src/main/cpp/propertiespatternconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/loggingeventpatternconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/patternconverter.cpp	5
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	12
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	6
/src/logging-log4cxx/src/main/cpp/mdc.cpp	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/cpp/loggerpatternconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/namepatternconverter.cpp	3
/src/logging-log4cxx/src/main/cpp/nameabbreviator.cpp	3
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	5
/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	7
/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	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/classnamepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/datepatternconverter.cpp	5
/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/dateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/fulllocationpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/fulllocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/linelocationpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/linelocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/messagepatternconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/cpp/formattinginfo.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/messagepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/lineseparatorpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/lineseparatorpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/methodlocationpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/methodlocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/levelpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/levelpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/relativetimepatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/relativetimepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/threadpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/threadpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/threadusernamepatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/threadusernamepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/ndcpatternconverter.cpp	2
/usr/local/bin/../include/c++/v1/optional	2
/src/logging-log4cxx/src/main/cpp/ndc.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/ndcpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/throwableinformationpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/throwableinformationpatternconverter.h	2

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	24	12.8%
gold	[1:9]	14	7.48%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	149	79.6%
All colors	187	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
8	98	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00098
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	143	log4cxx::JSONLayout::appendSerializedNDC(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00143
2	27	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00027
2	111	log4cxx::helpers::DateFormat::format(std::__1::basic_string , std::__1::allocator >&, long) const	call site: 00111	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	83	LLVMFuzzerTestOneInput	call site: 00083
1	139	log4cxx::MDC::get(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00139
1	150	log4cxx::NDC::get(std::__1::basic_string , std::__1::allocator >&)	call site: 00150

Runtime coverage analysis

Covered functions

847

Functions that are reachable but not covered

30

Reachable functions

190

Percentage of reachable functions covered

84.21%

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	14
/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	1
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	3
/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	2
/src/logging-log4cxx/src/main/cpp/ndc.cpp	5
/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	5
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	12
/src/logging-log4cxx/src/main/cpp/mdc.cpp	4
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	1
/src/logging-log4cxx/src/main/cpp/dateformat.cpp	1
/usr/local/bin/../include/c++/v1/optional	2

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	21	12.8%
gold	[1:9]	2	1.22%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	140	85.8%
All colors	163	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
8	74	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00074
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	119	log4cxx::JSONLayout::appendSerializedNDC(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00119
2	87	log4cxx::helpers::DateFormat::format(std::__1::basic_string , std::__1::allocator >&, long) const	call site: 00087	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
1	115	log4cxx::MDC::get(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00115
1	126	log4cxx::NDC::get(std::__1::basic_string , std::__1::allocator >&)	call site: 00126

Runtime coverage analysis

Covered functions

828

Functions that are reachable but not covered

29

Reachable functions

163

Percentage of reachable functions covered

82.21%

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	14
/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	1
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.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/cpp/ndc.cpp	5
/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	5
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	12
/src/logging-log4cxx/src/main/cpp/mdc.cpp	4
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	1
/src/logging-log4cxx/src/main/cpp/dateformat.cpp	1
/usr/local/bin/../include/c++/v1/optional	2

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	431	97.5%
gold	[1:9]	7	1.58%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	0.90%
All colors	442	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
133	233	log4cxx::helpers::WideLife ::operator log4cxx::spi::RepositorySelector::ClazzRepositorySelector&()	call site: 00233	__cxa_guard_abort
79	0	EP	call site: 00000	apr_pool_destroy
67	374	log4cxx::helpers::WideLife ::operator log4cxx::helpers::Object::ClazzObject&()	call site: 00374	__cxa_guard_abort
61	113	log4cxx::helpers::WideLife ::WideLife()	call site: 00113	__cxa_allocate_exception
46	179	log4cxx::helpers::System::getProperty(std::__1::basic_string , std::__1::allocator > const&)	call site: 00179	apr_uid_current
21	91	log4cxx::helpers::WideLife ::WideLife()	call site: 00091	apr_pool_create_ex
10	80	log4cxx::helpers::WideLife<(anonymous namespace)::apr_environment>::WideLife()	call site: 00080	apr_initialize
6	226	log4cxx::helpers::WideLife ::WideLife()	call site: 00226	__cxa_atexit
6	367	log4cxx::helpers::WideLife ::WideLife()	call site: 00367	__cxa_atexit
2	175	log4cxx::helpers::System::getProperty(std::__1::basic_string , std::__1::allocator > const&)	call site: 00175	apr_filepath_get

Runtime coverage analysis

Covered functions

696

Functions that are reachable but not covered

375

Reachable functions

420

Percentage of reachable functions covered

10.71%

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

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	5
/src/logging-log4cxx/src/main/include/log4cxx/appender.h	2
/src/logging-log4cxx/src/main/cpp/fileappender.cpp	8
/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	6
/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	10
/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	3
/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/cpp/appenderattachableimpl.cpp	2
/src/logging-log4cxx/src/main/cpp/appender.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

1801

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/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	25	89.2%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	10.7%
All colors	28	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
6	21	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00021	remove
4	16	log4cxx::Logger::isDebugEnabledFor(std::__1::shared_ptr const&)	call site: 00016

Runtime coverage analysis

Covered functions

1801

Functions that are reachable but not covered

2

Reachable functions

47

Percentage of reachable functions covered

95.74%

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

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	22	91.6%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	2	8.33%
All colors	24	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
11	0	EP	call site: 00000
11	12	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00012

Runtime coverage analysis

Covered functions

1801

Functions that are reachable but not covered

1

Reachable functions

36

Percentage of reachable functions covered

97.22%

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

1801

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	76	84.4%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	14	15.5%
All colors	90	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
38	51	LLVMFuzzerTestOneInput	call site: 00051
23	25	LLVMFuzzerTestOneInput	call site: 00025
10	6	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00006
5	0	EP	call site: 00000

Runtime coverage analysis

Covered functions

1801

Functions that are reachable but not covered

33

Reachable functions

112

Percentage of reachable functions covered

70.54%

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: 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.9%
gold	[1:9]	312	32.9%
yellow	[10:29]	16	1.69%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	79	8.35%
All colors	946	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
176	493	log4cxx::helpers::WideLife ::operator log4cxx::helpers::ClassRegistration&()	call site: 00493	_ZN7log4cxx7helpers8WideLifeINS0_17ClassRegistrationEEC2IRFRKNS0_5ClassEvEJEQntsr3stdE7same_asINS1_IT_EETL0__EEEOSA_DpOT0_
17	142	log4cxx::helpers::Pool::setPool()	call site: 00142	__cxa_allocate_exception
16	360	log4cxx::helpers::OptionConverter::substVars(std::__1::basic_string , std::__1::allocator > const&, log4cxx::helpers::Properties&)	call site: 00360	__cxa_allocate_exception
14	194	log4cxx::helpers::LogLog::getInstance()	call site: 00194	fwide
13	161	log4cxx::helpers::Pool::~Pool()	call site: 00161	apr_filepath_get
13	275	log4cxx::helpers::FileInputStream::FileInputStreamPrivate::open()	call site: 00275	__cxa_allocate_exception
13	670	log4cxx::PropertyConfigurator::doConfigure(log4cxx::helpers::Properties&, std::__1::shared_ptr )	call site: 00670
12	126	log4cxx::helpers::Transcoder::encode(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00126	__cxa_throw
11	293	log4cxx::helpers::Properties::load(std::__1::shared_ptr )	call site: 00293	__cxa_allocate_exception
10	334	log4cxx::PropertyConfigurator::doConfigure(log4cxx::File const&, std::__1::shared_ptr )	call site: 00334	__cxa_end_catch
9	823	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00823	__cxa_guard_acquire
7	693	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: 00693	__cxa_allocate_exception

Runtime coverage analysis

Covered functions

1082

Functions that are reachable but not covered

173

Reachable functions

719

Percentage of reachable functions covered

75.94%

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	4
/src/logging-log4cxx/src/main/cpp/file.cpp	7
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	2
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	14
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	75
/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/propertyconfigurator.cpp	15
/src/logging-log4cxx/src/main/cpp/configurator.cpp	3
/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/helpers/aprinitializer.h	3
/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	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/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	6
/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/include/log4cxx/spi/repositoryselector.h	1
/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/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/cpp/appenderattachableimpl.cpp	4
/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/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	30	93.7%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	2	6.25%
All colors	32	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
12	19	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00019

Runtime coverage analysis

Covered functions

1801

Functions that are reachable but not covered

1

Reachable functions

34

Percentage of reachable functions covered

97.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/JSONLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	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

1801

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

Runtime coverage analysis

Covered functions

1801

Functions that are reachable but not covered

1

Reachable functions

36

Percentage of reachable functions covered

97.22%

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

1801

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: 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	24	15.1%
gold	[1:9]	2	1.26%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	132	83.5%
All colors	158	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
8	72	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00072
4	86	(anonymous namespace)::appendValidCharacters(std::__1::basic_string , std::__1::allocator >&, std::__1::basic_string , std::__1::allocator > const&, std::__1::function , std::__1::allocator >&, int)>, bool)	call site: 00086
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	108	log4cxx::xml::XMLLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00108
2	23	log4cxx::Layout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00023	apr_pool_destroy
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	56	LLVMFuzzerTestOneInput	call site: 00056
1	94	log4cxx::helpers::Transform::appendCharacterReference(std::__1::basic_string , std::__1::allocator >&, unsigned int)	call site: 00094
1	137	log4cxx::MDC::get(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00137

Runtime coverage analysis

Covered functions

782

Functions that are reachable but not covered

29

Reachable functions

163

Percentage of reachable functions covered

82.21%

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	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/layout.cpp	3
/src/logging-log4cxx/src/main/cpp/level.cpp	3
/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	5
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	2
/src/logging-log4cxx/src/main/cpp/ndc.cpp	5
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	2
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	14
/src/logging-log4cxx/src/main/cpp/mdc.cpp	4
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/cpp/transform.cpp	5
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/usr/local/bin/../include/c++/v1/optional	2

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	30	15.8%
gold	[1:9]	14	7.40%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	145	76.7%
All colors	189	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
8	99	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00099
7	112	(anonymous namespace)::appendValidCharacters(std::__1::basic_string , std::__1::allocator >&, std::__1::basic_string , std::__1::allocator > const&, std::__1::function , std::__1::allocator >&, int)>, bool)	call site: 00112
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	139	log4cxx::xml::XMLLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00139
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	45	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00045
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	53	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00053
1	83	LLVMFuzzerTestOneInput	call site: 00083
1	121	log4cxx::helpers::Transform::appendCharacterReference(std::__1::basic_string , std::__1::allocator >&, unsigned int)	call site: 00121
1	168	log4cxx::MDC::get(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00168

Runtime coverage analysis

Covered functions

801

Functions that are reachable but not covered

30

Reachable functions

190

Percentage of reachable functions covered

84.21%

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	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/layout.cpp	3
/src/logging-log4cxx/src/main/cpp/level.cpp	3
/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	5
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	2
/src/logging-log4cxx/src/main/cpp/ndc.cpp	5
/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	14
/src/logging-log4cxx/src/main/cpp/mdc.cpp	4
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/cpp/transform.cpp	5
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/usr/local/bin/../include/c++/v1/optional	2

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	59	23.6%
gold	[1:9]	77	30.9%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	113	45.3%
All colors	249	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	159	log4cxx::helpers::Pool::setPool()	call site: 00159	__cxa_allocate_exception
13	178	log4cxx::helpers::Pool::~Pool()	call site: 00178	apr_filepath_get
4	51	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: 00051	__cxa_guard_acquire
4	121	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00121	__cxa_throw
3	87	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00087	__cxa_allocate_exception
2	6	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00006
2	98	log4cxx::helpers::CharsetEncoder::createDefaultEncoder()	call site: 00098
2	213	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: 00213
1	13	log4cxx::helpers::WideLife >::~WideLife()	call site: 00013	__cxa_begin_catch
1	16	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00016
1	46	LLVMFuzzerTestOneInput	call site: 00046
1	56	log4cxx::helpers::WideLife >::~WideLife()	call site: 00056	__cxa_guard_release

Runtime coverage analysis

Covered functions

965

Functions that are reachable but not covered

41

Reachable functions

242

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	2
/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: 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	525	58.4%
gold	[1:9]	291	32.4%
yellow	[10:29]	16	1.78%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	66	7.34%
All colors	898	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
176	444	log4cxx::helpers::WideLife ::operator log4cxx::helpers::ClassRegistration&()	call site: 00444	_ZN7log4cxx7helpers8WideLifeINS0_17ClassRegistrationEEC2IRFRKNS0_5ClassEvEJEQntsr3stdE7same_asINS1_IT_EETL0__EEEOSA_DpOT0_
17	88	log4cxx::helpers::Pool::setPool()	call site: 00088	__cxa_allocate_exception
17	140	log4cxx::helpers::LogLog::getInstance()	call site: 00140	fwide
16	311	log4cxx::helpers::OptionConverter::substVars(std::__1::basic_string , std::__1::allocator > const&, log4cxx::helpers::Properties&)	call site: 00311	__cxa_allocate_exception
13	107	log4cxx::helpers::Pool::~Pool()	call site: 00107	apr_filepath_get
13	621	log4cxx::PropertyConfigurator::doConfigure(log4cxx::helpers::Properties&, std::__1::shared_ptr )	call site: 00621
11	73	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00073	__cxa_allocate_exception
11	244	log4cxx::helpers::Properties::load(std::__1::shared_ptr )	call site: 00244	__cxa_allocate_exception
10	285	log4cxx::PropertyConfigurator::doConfigure(log4cxx::File const&, std::__1::shared_ptr )	call site: 00285	__cxa_end_catch
9	644	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: 00644	__cxa_allocate_exception
9	776	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00776	__cxa_guard_acquire
7	232	log4cxx::helpers::FileInputStream::FileInputStreamPrivate::open()	call site: 00232	__cxa_allocate_exception

Runtime coverage analysis

Covered functions

1064

Functions that are reachable but not covered

167

Reachable functions

671

Percentage of reachable functions covered

75.11%

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	4
/src/logging-log4cxx/src/main/cpp/file.cpp	7
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	5
/src/logging-log4cxx/src/main/cpp/propertyconfigurator.cpp	15
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	14
/src/logging-log4cxx/src/main/cpp/configurator.cpp	3
/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/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/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/cpp/consolewriter.cpp	2
/src/logging-log4cxx/src/main/cpp/loader.cpp	5
/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/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/fileinputstream.cpp	2
/src/logging-log4cxx/src/main/cpp/inputstream.cpp	2
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	1
/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/cpp/appenderattachableimpl.cpp	4
/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: 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	26	13.5%
gold	[1:9]	3	1.56%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	163	84.8%
All colors	192	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
8	118	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00118
4	59	(anonymous namespace)::appendCharacterReferenceHandler(std::__1::basic_string , std::__1::allocator >&, int)	call site: 00059
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	149	log4cxx::Level::getWarn()	call site: 00149
3	168	log4cxx::HTMLLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00168
2	35	log4cxx::Layout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00035	apr_pool_destroy
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	48	log4cxx::helpers::OptionConverter::toBoolean(std::__1::basic_string , std::__1::allocator > const&, bool)	call site: 00048
1	102	LLVMFuzzerTestOneInput	call site: 00102

Runtime coverage analysis

Covered functions

830

Functions that are reachable but not covered

29

Reachable functions

180

Percentage of reachable functions covered

83.89%

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	8
/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	3
/src/logging-log4cxx/src/main/cpp/level.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	3
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	2
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	2
/src/logging-log4cxx/src/main/cpp/transform.cpp	7
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/dateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/ndc.cpp	5
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	10
/src/logging-log4cxx/src/main/cpp/mdc.cpp	3
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/usr/local/bin/../include/c++/v1/optional	2

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

1801

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: 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	102	26.2%
gold	[1:9]	71	18.2%
yellow	[10:29]	29	7.45%
greenyellow	[30:49]	14	3.59%
lawngreen	50+	173	44.4%
All colors	389	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	119	log4cxx::helpers::Pool::setPool()	call site: 00119	__cxa_allocate_exception
13	138	log4cxx::helpers::Pool::~Pool()	call site: 00138	apr_filepath_get
8	309	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00309
4	39	LLVMFuzzerTestOneInput	call site: 00039
4	81	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00081	__cxa_throw
4	179	isConsoleWide(_IO_FILE*)	call site: 00179	fputws
4	204	LLVMFuzzerTestOneInput	call site: 00204
3	74	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00074	__cxa_allocate_exception
3	360	LLVMFuzzerTestOneInput	call site: 00360
3	366	log4cxx::pattern::NDCPatternConverter::format(std::__1::shared_ptr const&, std::__1::basic_string , std::__1::allocator >&, log4cxx::helpers::Pool&) const	call site: 00366
3	374	log4cxx::NDC::get(std::__1::basic_string , std::__1::allocator >&)	call site: 00374
3	384	LLVMFuzzerTestOneInput	call site: 00384

Runtime coverage analysis

Covered functions

978

Functions that are reachable but not covered

101

Reachable functions

393

Percentage of reachable functions covered

74.3%

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/level.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	24
/src/logging-log4cxx/src/main/cpp/pool.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	5
/src/logging-log4cxx/src/main/cpp/propertiespatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/cpp/loggingeventpatternconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/patternconverter.cpp	5
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	12
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	6
/src/logging-log4cxx/src/main/cpp/mdc.cpp	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/cpp/loggerpatternconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/namepatternconverter.cpp	3
/src/logging-log4cxx/src/main/cpp/nameabbreviator.cpp	3
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	5
/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	7
/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	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/classnamepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/datepatternconverter.cpp	5
/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/dateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/fulllocationpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/fulllocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/linelocationpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/linelocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/messagepatternconverter.cpp	2
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/cpp/formattinginfo.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/pattern/messagepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/lineseparatorpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/lineseparatorpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/methodlocationpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/methodlocationpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/levelpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/levelpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/relativetimepatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/relativetimepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/threadpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/threadpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/threadusernamepatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/threadusernamepatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/ndcpatternconverter.cpp	2
/usr/local/bin/../include/c++/v1/optional	2
/src/logging-log4cxx/src/main/cpp/ndc.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/ndcpatternconverter.h	2
/src/logging-log4cxx/src/main/cpp/throwableinformationpatternconverter.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/pattern/throwableinformationpatternconverter.h	2

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	30	13.6%
gold	[1:9]	17	7.76%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	172	78.5%
All colors	219	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
8	145	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00145
4	86	(anonymous namespace)::appendCharacterReferenceHandler(std::__1::basic_string , std::__1::allocator >&, int)	call site: 00086
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	176	log4cxx::Level::getWarn()	call site: 00176
3	195	log4cxx::HTMLLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00195
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	58	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00058
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	48	log4cxx::helpers::OptionConverter::toBoolean(std::__1::basic_string , std::__1::allocator > const&, bool)	call site: 00048
1	66	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00066
1	96	(anonymous namespace)::appendValidCharacters(std::__1::basic_string , std::__1::allocator >&, std::__1::basic_string , std::__1::allocator > const&, std::__1::function , std::__1::allocator >&, int)>, bool)	call site: 00096
1	129	LLVMFuzzerTestOneInput	call site: 00129

Runtime coverage analysis

Covered functions

849

Functions that are reachable but not covered

30

Reachable functions

207

Percentage of reachable functions covered

85.51%

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	8
/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	3
/src/logging-log4cxx/src/main/cpp/level.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	3
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	2
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/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/transform.cpp	7
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/dateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/ndc.cpp	5
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	10
/src/logging-log4cxx/src/main/cpp/mdc.cpp	3
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/usr/local/bin/../include/c++/v1/optional	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	31.2%
gold	[1:9]	10	31.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	12	37.5%
All colors	32	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
6	11	chdirExecutableHome()	call site: 00011	time
3	6	findExecutablePath(char*)	call site: 00006	time
1	0	EP	call site: 00000

Runtime coverage analysis

Covered functions

1801

Functions that are reachable but not covered

7

Reachable functions

40

Percentage of reachable functions covered

82.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/PatternLayoutFuzzer.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/logger.h	1
/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	565	54.8%
gold	[1:9]	172	16.6%
yellow	[10:29]	26	2.52%
greenyellow	[30:49]	13	1.26%
lawngreen	50+	255	24.7%
All colors	1031	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	959	log4cxx::helpers::WideLife ::operator log4cxx::AsyncAppender::ClazzAsyncAppender&()	call site: 00959	__dynamic_cast
32	921	log4cxx::helpers::WideLife ::operator log4cxx::spi::AppenderAttachable::ClazzAppenderAttachable&()	call site: 00921	__cxa_guard_abort
17	125	log4cxx::helpers::Pool::setPool()	call site: 00125	__cxa_allocate_exception
16	675	log4cxx::xml::DOMConfigurator::DOMConfiguratorPrivate::parseChildrenOfLoggerElement(apr_xml_elem*, std::__1::shared_ptr , bool)	call site: 00675	__cxa_guard_acquire
16	738	log4cxx::config::PropertySetter::activate()	call site: 00738	__cxa_begin_catch
14	704	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00704	__cxa_guard_acquire
14	877	log4cxx::helpers::WideLife ::operator log4cxx::rolling::FilterBasedTriggeringPolicy::ClazzFilterBasedTriggeringPolicy&()	call site: 00877	__cxa_begin_catch
13	787	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00787
12	766	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00766
10	625	log4cxx::helpers::WideLife ::operator log4cxx::spi::LoggerFactory::ClazzLoggerFactory&()	call site: 00625	__cxa_begin_catch
10	636	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00636
9	806	log4cxx::helpers::WideLife ::operator log4cxx::AppenderSkeleton::ClazzAppenderSkeleton&()	call site: 00806

Runtime coverage analysis

Covered functions

921

Functions that are reachable but not covered

201

Reachable functions

727

Percentage of reachable functions covered

72.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/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	2
/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	1
/src/logging-log4cxx/src/main/include/log4cxx/asyncappender.h	1
/src/logging-log4cxx/src/main/cpp/appenderattachableimpl.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/spi/configurator.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	544	55.5%
gold	[1:9]	138	14.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	3	0.30%
lawngreen	50+	295	30.1%
All colors	980	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	908	log4cxx::helpers::WideLife ::operator log4cxx::AsyncAppender::ClazzAsyncAppender&()	call site: 00908	__dynamic_cast
32	870	log4cxx::helpers::WideLife ::operator log4cxx::spi::AppenderAttachable::ClazzAppenderAttachable&()	call site: 00870	__cxa_guard_abort
16	624	log4cxx::xml::DOMConfigurator::DOMConfiguratorPrivate::parseChildrenOfLoggerElement(apr_xml_elem*, std::__1::shared_ptr , bool)	call site: 00624	__cxa_guard_acquire
16	687	log4cxx::config::PropertySetter::activate()	call site: 00687	__cxa_begin_catch
14	71	log4cxx::helpers::Pool::setPool()	call site: 00071	__cxa_allocate_exception
14	653	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00653	__cxa_guard_acquire
14	826	log4cxx::helpers::WideLife ::operator log4cxx::rolling::FilterBasedTriggeringPolicy::ClazzFilterBasedTriggeringPolicy&()	call site: 00826	__cxa_begin_catch
13	736	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00736
12	715	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00715
10	574	log4cxx::helpers::WideLife ::operator log4cxx::spi::LoggerFactory::ClazzLoggerFactory&()	call site: 00574	__cxa_begin_catch
10	585	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00585
9	755	log4cxx::helpers::WideLife ::operator log4cxx::AppenderSkeleton::ClazzAppenderSkeleton&()	call site: 00755

Runtime coverage analysis

Covered functions

915

Functions that are reachable but not covered

205

Reachable functions

687

Percentage of reachable functions covered

70.16%

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/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/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/cpp/charsetdecoder.cpp	1
/src/logging-log4cxx/src/main/include/log4cxx/private/string_c11.h	1
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	2
/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	1
/src/logging-log4cxx/src/main/include/log4cxx/asyncappender.h	1
/src/logging-log4cxx/src/main/cpp/appenderattachableimpl.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/spi/configurator.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	179	46.2%
gold	[1:9]	52	13.4%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	156	40.3%
All colors	387	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	103	log4cxx::helpers::Pool::setPool()	call site: 00103	__cxa_allocate_exception
27	320	log4cxx::helpers::WideLife ::operator log4cxx::helpers::Object::ClazzObject&()	call site: 00320	__cxa_guard_abort
16	153	log4cxx::helpers::LogLog::getInstance()	call site: 00153	fwide
11	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
10	206	log4cxx::WriterAppender::WriterAppenderPriv::close()	call site: 00206	__cxa_end_catch
9	273	log4cxx::File::mkdirs() const	call site: 00273	__cxa_rethrow
8	262	log4cxx::FileAppender::setFileInternal(std::__1::basic_string , std::__1::allocator > const&, bool, bool, unsigned long)	call site: 00262
8	295	log4cxx::FileAppender::activateOptionsInternal()	call site: 00295	__cxa_end_catch
5	25	LLVMFuzzerTestOneInput	call site: 00025
5	288	log4cxx::WriterAppender::WriterAppenderPriv::writeHeader()	call site: 00288	__clang_call_terminate
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	14	LLVMFuzzerTestOneInput	call site: 00014

Runtime coverage analysis

Covered functions

1215

Functions that are reachable but not covered

99

Reachable functions

374

Percentage of reachable functions covered

73.53%

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	5
/src/logging-log4cxx/src/main/include/log4cxx/appender.h	2
/src/logging-log4cxx/src/main/cpp/fileappender.cpp	8
/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	6
/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	10
/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	3
/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/bytebuffer.cpp	2
/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/cpp/appenderattachableimpl.cpp	2
/src/logging-log4cxx/src/main/cpp/appender.cpp	1