High level conclusions

Fuzzers reach 67.49% code coverage.

Fuzzer TimeBasedRollingPolicyFuzzer-wchar_t is blocked:

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

Fuzzers reach 17.68% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

839 / 4744

Cyclomatic complexity statically reachable by fuzzers

8410 / 24661

Runtime code coverage of functions

3202 / 4744

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	57	29.3%
gold	[1:9]	53	27.3%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	84	43.2%
All colors	194	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
23	117	log4cxx::helpers::Pool::~Pool()	call site: 00117	__cxa_throw
8	105	log4cxx::helpers::Pool::setPool()	call site: 00105	__cxa_allocate_exception
5	163	log4cxx::helpers::SystemErrWriter::write(std::__1::basic_string , std::__1::allocator > const&)	call site: 00163	fwide
4	24	log4cxx::pattern::PatternParser::parse(std::__1::basic_string , std::__1::allocator > const&, std::__1::map , std::__1::allocator >, std::__1::function (std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)>, std::__1::less , std::__1::allocator > >, std::__1::allocator , std::__1::allocator > const, std::__1::function (std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)> > > > const&)	call site: 00024	__cxa_guard_acquire
4	67	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00067	__cxa_throw
3	60	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00060	__cxa_allocate_exception
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
1	92	log4cxx::helpers::APRInitializer::APRInitializer()	call site: 00092	__assert_fail

Runtime coverage analysis

Covered functions

929

Functions that are reachable but not covered

46

Reachable functions

186

Percentage of reachable functions covered

75.27%

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	2
/src/logging-log4cxx/src/main/cpp/patternconverter.cpp	1

Fuzzer: HTMLLayoutFuzzer-wchar_t

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	25	12.8%
gold	[1:9]	15	7.69%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	155	79.4%
All colors	195	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	125	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00125
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	152	log4cxx::Level::getWarn()	call site: 00152
3	171	log4cxx::HTMLLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00171
2	34	log4cxx::Layout::getFormattedEventCharacterCount() const	call site: 00034	apr_pool_destroy
2	55	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00055
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	46	log4cxx::helpers::OptionConverter::toBoolean(std::__1::basic_string , std::__1::allocator > const&, bool)	call site: 00046
1	63	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00063
1	109	LLVMFuzzerTestOneInput	call site: 00109

Runtime coverage analysis

Covered functions

840

Functions that are reachable but not covered

30

Reachable functions

189

Percentage of reachable functions covered

84.13%

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	2
/src/logging-log4cxx/src/main/cpp/layout.cpp	2
/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/cpp/stringhelper.cpp	2
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	1
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	4
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	5
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/transform.cpp	1
/src/logging-log4cxx/src/main/cpp/date.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/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: 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	103	26.8%
gold	[1:9]	81	21.0%
yellow	[10:29]	57	14.8%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	143	37.2%
All colors	384	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
23	131	log4cxx::helpers::Pool::~Pool()	call site: 00131	__cxa_throw
8	119	log4cxx::helpers::Pool::setPool()	call site: 00119	__cxa_allocate_exception
8	302	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00302
5	177	log4cxx::helpers::SystemErrWriter::write(std::__1::basic_string , std::__1::allocator > const&)	call site: 00177	fwide
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	198	LLVMFuzzerTestOneInput	call site: 00198
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	355	LLVMFuzzerTestOneInput	call site: 00355
3	361	log4cxx::pattern::NDCPatternConverter::format(std::__1::shared_ptr const&, std::__1::basic_string , std::__1::allocator >&, log4cxx::helpers::Pool&) const	call site: 00361
3	369	log4cxx::NDC::get(std::__1::basic_string , std::__1::allocator >&)	call site: 00369
3	379	LLVMFuzzerTestOneInput	call site: 00379

Runtime coverage analysis

Covered functions

972

Functions that are reachable but not covered

100

Reachable functions

379

Percentage of reachable functions covered

73.61%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/PatternConverterFuzzer.cpp	2
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	5
/src/logging-log4cxx/src/main/cpp/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	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/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: 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	106	24.7%
gold	[1:9]	88	20.5%
yellow	[10:29]	15	3.50%
greenyellow	[30:49]	16	3.73%
lawngreen	50+	203	47.4%
All colors	428	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
23	179	log4cxx::helpers::Pool::~Pool()	call site: 00179	__cxa_throw
9	168	log4cxx::helpers::Pool::setPool()	call site: 00168	__cxa_allocate_exception
8	347	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00347
4	65	LLVMFuzzerTestOneInput	call site: 00065
4	130	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00130	__cxa_throw
4	243	LLVMFuzzerTestOneInput	call site: 00243
3	100	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00100	__cxa_allocate_exception
3	399	LLVMFuzzerTestOneInput	call site: 00399
3	405	log4cxx::pattern::NDCPatternConverter::format(std::__1::shared_ptr const&, std::__1::basic_string , std::__1::allocator >&, log4cxx::helpers::Pool&) const	call site: 00405
3	413	log4cxx::NDC::get(std::__1::basic_string , std::__1::allocator >&)	call site: 00413
3	423	LLVMFuzzerTestOneInput	call site: 00423
2	6	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00006

Runtime coverage analysis

Covered functions

1006

Functions that are reachable but not covered

94

Reachable functions

427

Percentage of reachable functions covered

77.99%

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

1751

Functions that are reachable but not covered

0

Reachable functions

1

Percentage of reachable functions covered

100.0%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

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

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	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

1751

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

1751

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	553	57.1%
gold	[1:9]	321	33.1%
yellow	[10:29]	16	1.65%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	77	7.96%
All colors	967	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
180	508	log4cxx::helpers::WideLife ::operator log4cxx::helpers::ClassRegistration&()	call site: 00508	_ZN7log4cxx7helpers8WideLifeINS0_17ClassRegistrationEEC2IRFRKNS0_5ClassEvEJEQntsr3stdE7same_asINS1_IT_EETL0__EEEOSA_DpOT0_
22	148	log4cxx::helpers::Pool::~Pool()	call site: 00148	__cxa_throw
16	375	log4cxx::helpers::OptionConverter::substVars(std::__1::basic_string , std::__1::allocator > const&, log4cxx::helpers::Properties&)	call site: 00375	__cxa_allocate_exception
13	689	log4cxx::PropertyConfigurator::doConfigure(log4cxx::helpers::Properties&, std::__1::shared_ptr )	call site: 00689
12	121	log4cxx::helpers::Transcoder::encode(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00121	__cxa_throw
11	289	log4cxx::helpers::Properties::load(std::__1::shared_ptr )	call site: 00289	__cxa_allocate_exception
9	137	log4cxx::helpers::Pool::setPool()	call site: 00137	__cxa_allocate_exception
9	314	log4cxx::helpers::InputStreamReader::read(log4cxx::helpers::Pool&)	call site: 00314	__cxa_allocate_exception
9	840	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00840	__cxa_guard_acquire
8	351	log4cxx::PropertyConfigurator::doConfigure(log4cxx::File const&, std::__1::shared_ptr )	call site: 00351	__cxa_end_catch
8	930	init()	call site: 00930	apr_file_remove
7	190	log4cxx::helpers::LogLog::getInstance()	call site: 00190	fwide

Runtime coverage analysis

Covered functions

1077

Functions that are reachable but not covered

167

Reachable functions

728

Percentage of reachable functions covered

77.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/PatternLayoutFuzzer.cpp	4
/src/logging-log4cxx/src/main/cpp/file.cpp	9
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	8
/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	11
/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	11
/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	7
/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	2
/src/logging-log4cxx/src/main/cpp/loader.cpp	6
/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	1
/src/logging-log4cxx/src/main/cpp/inputstream.cpp	2
/src/logging-log4cxx/src/main/cpp/inputstreamreader.cpp	3
/src/logging-log4cxx/src/main/cpp/reader.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	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/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/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/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

1751

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: 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	542	58.4%
gold	[1:9]	303	32.6%
yellow	[10:29]	16	1.72%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	66	7.11%
All colors	927	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
180	467	log4cxx::helpers::WideLife ::operator log4cxx::helpers::ClassRegistration&()	call site: 00467	_ZN7log4cxx7helpers8WideLifeINS0_17ClassRegistrationEEC2IRFRKNS0_5ClassEvEJEQntsr3stdE7same_asINS1_IT_EETL0__EEEOSA_DpOT0_
22	100	log4cxx::helpers::Pool::~Pool()	call site: 00100	__cxa_throw
17	333	log4cxx::helpers::OptionConverter::substVars(std::__1::basic_string , std::__1::allocator > const&, log4cxx::helpers::Properties&)	call site: 00333	__cxa_allocate_exception
13	648	log4cxx::PropertyConfigurator::doConfigure(log4cxx::helpers::Properties&, std::__1::shared_ptr )	call site: 00648
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	247	log4cxx::helpers::Properties::load(std::__1::shared_ptr )	call site: 00247	__cxa_allocate_exception
10	142	log4cxx::helpers::LogLog::getInstance()	call site: 00142	fwide
9	272	log4cxx::helpers::InputStreamReader::read(log4cxx::helpers::Pool&)	call site: 00272	__cxa_allocate_exception
9	671	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: 00671	__cxa_allocate_exception
9	801	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00801	__cxa_guard_acquire
8	88	log4cxx::helpers::Pool::setPool()	call site: 00088	__cxa_allocate_exception
8	309	log4cxx::PropertyConfigurator::doConfigure(log4cxx::File const&, std::__1::shared_ptr )	call site: 00309	__cxa_end_catch

Runtime coverage analysis

Covered functions

1059

Functions that are reachable but not covered

169

Reachable functions

689

Percentage of reachable functions covered

75.47%

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	9
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	7
/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	7
/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	2
/src/logging-log4cxx/src/main/cpp/loader.cpp	6
/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	1
/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	3
/src/logging-log4cxx/src/main/cpp/reader.cpp	2
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	8
/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/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/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/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

1751

Functions that are reachable but not covered

0

Reachable functions

1

Percentage of reachable functions covered

100.0%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

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

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

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

Runtime coverage analysis

Covered functions

1751

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

1751

Functions that are reachable but not covered

1

Reachable functions

16

Percentage of reachable functions covered

93.75%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: DOMConfiguratorFuzzer-wchar_t

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	615	59.9%
gold	[1:9]	138	13.4%
yellow	[10:29]	10	0.97%
greenyellow	[30:49]	7	0.68%
lawngreen	50+	256	24.9%
All colors	1026	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
53	956	log4cxx::helpers::WideLife ::operator log4cxx::AsyncAppender::ClazzAsyncAppender&()	call site: 00956	__dynamic_cast
35	661	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00661	__cxa_guard_acquire
23	927	log4cxx::helpers::WideLife ::operator log4cxx::spi::AppenderAttachable::ClazzAppenderAttachable&()	call site: 00927	__cxa_begin_catch
20	735	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00735	__cxa_begin_catch
19	349	log4cxx::Level::toLevelLS(std::__1::basic_string , std::__1::allocator > const&, std::__1::shared_ptr const&)	call site: 00349	__cxa_guard_acquire
18	303	log4cxx::Level::toLevelLS(std::__1::basic_string , std::__1::allocator > const&, std::__1::shared_ptr const&)	call site: 00303	__cxa_guard_acquire
15	131	log4cxx::helpers::Pool::~Pool()	call site: 00131	__cxa_throw
14	709	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00709	__cxa_guard_acquire
14	881	log4cxx::helpers::WideLife ::operator log4cxx::rolling::FilterBasedTriggeringPolicy::ClazzFilterBasedTriggeringPolicy&()	call site: 00881	__cxa_begin_catch
13	767	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00767	__cxa_guard_acquire
13	792	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00792
10	630	log4cxx::helpers::WideLife ::operator log4cxx::spi::LoggerFactory::ClazzLoggerFactory&()	call site: 00630	__cxa_begin_catch

Runtime coverage analysis

Covered functions

889

Functions that are reachable but not covered

213

Reachable functions

730

Percentage of reachable functions covered

70.82%

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	24
/src/logging-log4cxx/src/main/cpp/file.cpp	8
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	8
/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	9
/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	5
/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	2
/src/logging-log4cxx/src/main/cpp/loader.cpp	10
/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	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/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/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/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: /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

1751

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

1751

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: 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	399	96.8%
gold	[1:9]	7	1.69%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	1.45%
All colors	412	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
119	220	log4cxx::helpers::WideLife ::operator log4cxx::spi::RepositorySelector::ClazzRepositorySelector&()	call site: 00220	__cxa_guard_abort
75	0	EP	call site: 00000	apr_pool_destroy
64	347	log4cxx::helpers::WideLife ::operator log4cxx::helpers::Object::ClazzObject&()	call site: 00347	__cxa_guard_abort
59	109	log4cxx::helpers::WideLife ::WideLife()	call site: 00109	__cxa_allocate_exception
32	171	log4cxx::helpers::System::getProperty(std::__1::basic_string , std::__1::allocator > const&)	call site: 00171	apr_uid_current
21	87	log4cxx::helpers::WideLife ::WideLife()	call site: 00087	apr_pool_create_ex
10	76	log4cxx::helpers::WideLife<(anonymous namespace)::apr_environment>::WideLife()	call site: 00076	apr_initialize
6	206	log4cxx::helpers::SystemErrWriter::write(std::__1::basic_string , std::__1::allocator > const&)	call site: 00206	fputs
6	213	log4cxx::helpers::WideLife ::WideLife()	call site: 00213	__cxa_atexit
6	340	log4cxx::helpers::WideLife ::WideLife()	call site: 00340	__cxa_atexit
1	204	log4cxx::helpers::SystemErrWriter::write(std::__1::basic_string , std::__1::allocator > const&)	call site: 00204	fwide

Runtime coverage analysis

Covered functions

696

Functions that are reachable but not covered

357

Reachable functions

401

Percentage of reachable functions covered

10.97%

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/pool.cpp	5
/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/layout.cpp	1
/src/logging-log4cxx/src/main/cpp/rollingfileappender.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/appender.h	2
/src/logging-log4cxx/src/main/cpp/fileappender.cpp	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	8
/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	9
/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	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/rolloverdescription.cpp	4
/src/logging-log4cxx/src/main/cpp/file.cpp	10
/src/logging-log4cxx/src/main/include/log4cxx/private/writerappender_priv.h	1
/src/logging-log4cxx/src/main/include/log4cxx/appenderskeleton.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

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	22	88.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	3	12.0%
All colors	25	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
12	0	EP	call site: 00000
6	18	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00018	remove
4	13	log4cxx::Logger::isDebugEnabledFor(std::__1::shared_ptr const&)	call site: 00013

Runtime coverage analysis

Covered functions

1751

Functions that are reachable but not covered

2

Reachable functions

45

Percentage of reachable functions covered

95.56%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/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/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

1751

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: 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	22	12.0%
gold	[1:9]	15	8.24%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	145	79.6%
All colors	182	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	96	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00096
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	132	log4cxx::xml::XMLLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00132
2	22	log4cxx::Layout::getFormattedEventCharacterCount() const	call site: 00022	apr_pool_destroy
2	43	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00043
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	51	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00051
1	80	LLVMFuzzerTestOneInput	call site: 00080
1	161	log4cxx::MDC::get(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00161

Runtime coverage analysis

Covered functions

802

Functions that are reachable but not covered

30

Reachable functions

188

Percentage of reachable functions covered

84.04%

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	2
/src/logging-log4cxx/src/main/cpp/level.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	14
/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/cpp/ndc.cpp	5
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	1
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	4
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	5
/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	2
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/usr/local/bin/../include/c++/v1/optional	2

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	165	45.7%
gold	[1:9]	55	15.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	141	39.0%
All colors	361	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
25	297	log4cxx::helpers::WideLife ::operator log4cxx::helpers::Object::ClazzObject&()	call site: 00297	__cxa_guard_abort
24	109	log4cxx::helpers::StringHelper::toString(int, log4cxx::helpers::Pool&, std::__1::basic_string , std::__1::allocator >&)	call site: 00109	__cxa_throw
11	85	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00085	__cxa_allocate_exception
10	153	log4cxx::helpers::LogLog::getInstance()	call site: 00153	fwide
8	100	log4cxx::helpers::Pool::setPool()	call site: 00100	__cxa_allocate_exception
8	187	log4cxx::WriterAppender::WriterAppenderPriv::close()	call site: 00187	__cxa_end_catch
8	243	log4cxx::FileAppender::setFileInternal(std::__1::basic_string , std::__1::allocator > const&, bool, bool, unsigned long, log4cxx::helpers::Pool&)	call site: 00243
8	271	log4cxx::FileAppender::activateOptionsInternal(log4cxx::helpers::Pool&)	call site: 00271	__cxa_end_catch
5	25	LLVMFuzzerTestOneInput	call site: 00025
5	255	log4cxx::File::mkdirs(log4cxx::helpers::Pool&) const	call site: 00255	__cxa_rethrow
5	264	log4cxx::WriterAppender::WriterAppenderPriv::writeHeader()	call site: 00264	__clang_call_terminate
3	2	LLVMFuzzerTestOneInput	call site: 00002

Runtime coverage analysis

Covered functions

1192

Functions that are reachable but not covered

93

Reachable functions

349

Percentage of reachable functions covered

73.35%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/TimeBasedRollingPolicyFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	5
/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/layout.cpp	1
/src/logging-log4cxx/src/main/cpp/rollingfileappender.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/appender.h	2
/src/logging-log4cxx/src/main/cpp/fileappender.cpp	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	7
/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	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/rolloverdescription.cpp	4
/src/logging-log4cxx/src/main/cpp/file.cpp	10
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/writerappender_priv.h	1
/src/logging-log4cxx/src/main/include/log4cxx/appenderskeleton.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

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	599	61.3%
gold	[1:9]	114	11.6%
yellow	[10:29]	5	0.51%
greenyellow	[30:49]	2	0.20%
lawngreen	50+	257	26.3%
All colors	977	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
53	907	log4cxx::helpers::WideLife ::operator log4cxx::AsyncAppender::ClazzAsyncAppender&()	call site: 00907	__dynamic_cast
35	612	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00612	__cxa_guard_acquire
23	878	log4cxx::helpers::WideLife ::operator log4cxx::spi::AppenderAttachable::ClazzAppenderAttachable&()	call site: 00878	__cxa_begin_catch
20	686	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00686	__cxa_begin_catch
19	300	log4cxx::Level::toLevelLS(std::__1::basic_string , std::__1::allocator > const&, std::__1::shared_ptr const&)	call site: 00300	__cxa_guard_acquire
18	254	log4cxx::Level::toLevelLS(std::__1::basic_string , std::__1::allocator > const&, std::__1::shared_ptr const&)	call site: 00254	__cxa_guard_acquire
14	660	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00660	__cxa_guard_acquire
14	832	log4cxx::helpers::WideLife ::operator log4cxx::rolling::FilterBasedTriggeringPolicy::ClazzFilterBasedTriggeringPolicy&()	call site: 00832	__cxa_begin_catch
13	718	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00718	__cxa_guard_acquire
13	743	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00743
10	71	log4cxx::helpers::Pool::setPool()	call site: 00071	__cxa_allocate_exception
10	581	log4cxx::helpers::WideLife ::operator log4cxx::spi::LoggerFactory::ClazzLoggerFactory&()	call site: 00581	__cxa_begin_catch

Runtime coverage analysis

Covered functions

865

Functions that are reachable but not covered

216

Reachable functions

678

Percentage of reachable functions covered

68.14%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/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	24
/src/logging-log4cxx/src/main/cpp/file.cpp	8
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	20
/src/logging-log4cxx/src/main/cpp/configurator.cpp	1
/src/logging-log4cxx/src/main/cpp/logmanager.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/aprinitializer.h	2
/src/logging-log4cxx/src/main/cpp/aprinitializer.cpp	7
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	95
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/loglog.cpp	14
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	7
/src/logging-log4cxx/src/main/cpp/system.cpp	1
/src/logging-log4cxx/src/main/cpp/exception.cpp	10
/usr/local/bin/../include/c++/v1/__exception/exception.h	1
/src/logging-log4cxx/src/main/cpp/pool.cpp	5
/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	2
/src/logging-log4cxx/src/main/cpp/loader.cpp	10
/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	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/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/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/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: 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	60	25.1%
gold	[1:9]	73	30.5%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	106	44.3%
All colors	239	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
23	165	log4cxx::helpers::Pool::~Pool()	call site: 00165	__cxa_throw
9	154	log4cxx::helpers::Pool::setPool()	call site: 00154	__cxa_allocate_exception
4	50	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: 00050	__cxa_guard_acquire
4	116	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00116	__cxa_throw
3	86	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00086	__cxa_allocate_exception
2	6	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00006
2	96	log4cxx::helpers::CharsetEncoder::createDefaultEncoder()	call site: 00096
2	211	log4cxx::helpers::SystemErrWriter::write(std::__1::basic_string , std::__1::allocator > const&)	call site: 00211	fwide
1	13	log4cxx::helpers::WideLife >::~WideLife()	call site: 00013	__cxa_begin_catch
1	16	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00016
1	45	LLVMFuzzerTestOneInput	call site: 00045
1	55	log4cxx::helpers::WideLife >::~WideLife()	call site: 00055	__cxa_guard_release

Runtime coverage analysis

Covered functions

961

Functions that are reachable but not covered

41

Reachable functions

234

Percentage of reachable functions covered

82.48%

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	9
/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	2
/src/logging-log4cxx/src/main/cpp/patternconverter.cpp	1

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	22	13.2%
gold	[1:9]	2	1.20%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	142	85.5%
All colors	166	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
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	158	LLVMFuzzerTestOneInput	call site: 00158	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	84	log4cxx::JSONLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00084
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

825

Functions that are reachable but not covered

29

Reachable functions

165

Percentage of reachable functions covered

82.42%

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	2
/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/cpp/cacheddateformat.cpp	4
/usr/local/bin/../include/c++/v1/optional	2

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	19	12.0%
gold	[1:9]	3	1.89%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	136	86.0%
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	70	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00070
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	107	log4cxx::xml::XMLLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00107
2	22	log4cxx::Layout::getFormattedEventCharacterCount() const	call site: 00022	apr_pool_destroy
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	54	LLVMFuzzerTestOneInput	call site: 00054
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

781

Functions that are reachable but not covered

29

Reachable functions

159

Percentage of reachable functions covered

81.76%

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	2
/src/logging-log4cxx/src/main/cpp/level.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	10
/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/cpp/ndc.cpp	5
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	1
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	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	2
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/usr/local/bin/../include/c++/v1/optional	2

Fuzzer: HTMLLayoutFuzzer-utf-8

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	22	12.9%
gold	[1:9]	3	1.76%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	145	85.2%
All colors	170	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
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	126	log4cxx::Level::getWarn()	call site: 00126
3	146	log4cxx::HTMLLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00146
2	34	log4cxx::Layout::getFormattedEventCharacterCount() const	call site: 00034	apr_pool_destroy
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	46	log4cxx::helpers::OptionConverter::toBoolean(std::__1::basic_string , std::__1::allocator > const&, bool)	call site: 00046
1	83	LLVMFuzzerTestOneInput	call site: 00083

Runtime coverage analysis

Covered functions

819

Functions that are reachable but not covered

29

Reachable functions

160

Percentage of reachable functions covered

81.88%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/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	2
/src/logging-log4cxx/src/main/cpp/layout.cpp	2
/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/cpp/stringhelper.cpp	2
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	1
/src/logging-log4cxx/src/main/cpp/transform.cpp	1
/src/logging-log4cxx/src/main/cpp/date.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/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: 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	25	13.1%
gold	[1:9]	14	7.36%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	151	79.4%
All colors	190	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	97	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00097
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	144	log4cxx::JSONLayout::appendSerializedNDC(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00144
2	27	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00027
2	182	LLVMFuzzerTestOneInput	call site: 00182	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	82	LLVMFuzzerTestOneInput	call site: 00082
1	107	log4cxx::JSONLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00107
1	140	log4cxx::MDC::get(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00140
1	151	log4cxx::NDC::get(std::__1::basic_string , std::__1::allocator >&)	call site: 00151

Runtime coverage analysis

Covered functions

847

Functions that are reachable but not covered

30

Reachable functions

198

Percentage of reachable functions covered

84.85%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/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	4
/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	5
/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/cpp/cacheddateformat.cpp	4
/usr/local/bin/../include/c++/v1/optional	2