High level conclusions

Fuzzers reach 68.66% code coverage.

Fuzzer PatternConverterFuzzer-wchar_t is blocked:

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

Fuzzer HTMLLayoutFuzzer-utf-8 is blocked:

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

Fuzzer XMLLayoutFuzzer-utf-8 is blocked:

The runtime code coverage of XMLLayoutFuzzer-utf-8 covers 5.714% 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.54% of cyclomatic complexity.

Fuzzers reach 17.95% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

878 / 4889

Cyclomatic complexity statically reachable by fuzzers

8865 / 25664

Runtime code coverage of functions

3357 / 4889

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: 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.2%
gold	[1:9]	14	7.44%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	149	79.2%
All colors	188	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
8	98	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00098
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	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	111	log4cxx::helpers::DateFormat::format(std::__1::basic_string , std::__1::allocator >&, long) const	call site: 00111	apr_pool_destroy
1	11	log4cxx::helpers::OptionConverter::toBoolean(std::__1::basic_string , std::__1::allocator > const&, bool)	call site: 00011
1	34	log4cxx::helpers::WideLife >::~WideLife()	call site: 00034	__cxa_begin_catch
1	37	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00037
1	83	LLVMFuzzerTestOneInput	call site: 00083
1	116	log4cxx::JSONLayout::appendItem(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00116
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

190

Percentage of reachable functions covered

84.21%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/JSONLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/jsonlayout.cpp	14
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	1
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	3
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	8
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/level.cpp	2
/src/logging-log4cxx/src/main/cpp/ndc.cpp	5
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	5
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	12
/src/logging-log4cxx/src/main/cpp/mdc.cpp	4
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	1
/src/logging-log4cxx/src/main/cpp/dateformat.cpp	1
/usr/local/bin/../include/c++/v1/optional	2

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

Runtime coverage analysis

Covered functions

696

Functions that are reachable but not covered

165

Reachable functions

175

Percentage of reachable functions covered

5.71%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/XMLLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/xmllayout.cpp	6
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	3
/src/logging-log4cxx/src/main/cpp/level.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	4
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	5
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	2
/src/logging-log4cxx/src/main/cpp/ndc.cpp	5
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	2
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	14
/src/logging-log4cxx/src/main/cpp/mdc.cpp	4
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/cpp/transform.cpp	5
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	5
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	1
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/usr/local/bin/../include/c++/v1/optional	2

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	68	32.3%
gold	[1:9]	53	25.2%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	89	42.3%
All colors	210	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
17	105	log4cxx::helpers::Pool::setPool()	call site: 00105	__cxa_allocate_exception
16	165	isConsoleWide(_IO_FILE*)	call site: 00165	fputws
13	124	log4cxx::helpers::Pool::~Pool()	call site: 00124	apr_filepath_get
4	24	log4cxx::pattern::PatternParser::parse(std::__1::basic_string , std::__1::allocator > const&, std::__1::map , std::__1::allocator >, std::__1::function (std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)>, std::__1::less , std::__1::allocator > >, std::__1::allocator , std::__1::allocator > const, std::__1::function (std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)> > > > const&)	call site: 00024	__cxa_guard_acquire
4	67	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00067	__cxa_throw
3	60	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00060	__cxa_allocate_exception
2	159	log4cxx::helpers::LogLog::emit_log(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00159
1	10	log4cxx::helpers::WideLife >::~WideLife()	call site: 00010	__cxa_begin_catch
1	19	LLVMFuzzerTestOneInput	call site: 00019
1	29	log4cxx::helpers::WideLife >::~WideLife()	call site: 00029	__cxa_guard_release
1	32	log4cxx::helpers::WideLife >::operator std::__1::shared_ptr &()	call site: 00032	__cxa_guard_abort
1	64	log4cxx::helpers::RuntimeException::RuntimeException(std::__1::basic_string , std::__1::allocator > const&)	call site: 00064

Runtime coverage analysis

Covered functions

934

Functions that are reachable but not covered

59

Reachable functions

210

Percentage of reachable functions covered

71.9%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: PatternLayoutFuzzer-wchar_t

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	538	56.9%
gold	[1:9]	312	33.0%
yellow	[10:29]	16	1.69%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	79	8.35%
All colors	945	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
176	492	log4cxx::helpers::WideLife ::operator log4cxx::helpers::ClassRegistration&()	call site: 00492	_ZN7log4cxx7helpers8WideLifeINS0_17ClassRegistrationEEC2IRFRKNS0_5ClassEvEJEQntsr3stdE7same_asINS1_IT_EETL0__EEEOSA_DpOT0_
17	142	log4cxx::helpers::Pool::setPool()	call site: 00142	__cxa_allocate_exception
16	359	log4cxx::helpers::OptionConverter::substVars(std::__1::basic_string , std::__1::allocator > const&, log4cxx::helpers::Properties&)	call site: 00359	__cxa_allocate_exception
14	194	log4cxx::helpers::LogLog::getInstance()	call site: 00194	fwide
13	161	log4cxx::helpers::Pool::~Pool()	call site: 00161	apr_filepath_get
13	669	log4cxx::PropertyConfigurator::doConfigure(log4cxx::helpers::Properties&, std::__1::shared_ptr )	call site: 00669
12	126	log4cxx::helpers::Transcoder::encode(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00126	__cxa_throw
12	275	log4cxx::helpers::FileInputStream::FileInputStreamPrivate::open()	call site: 00275	__cxa_allocate_exception
11	292	log4cxx::helpers::Properties::load(std::__1::shared_ptr )	call site: 00292	__cxa_allocate_exception
10	333	log4cxx::PropertyConfigurator::doConfigure(log4cxx::File const&, std::__1::shared_ptr )	call site: 00333	__cxa_end_catch
9	822	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00822	__cxa_guard_acquire
7	692	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: 00692	__cxa_allocate_exception

Runtime coverage analysis

Covered functions

1084

Functions that are reachable but not covered

173

Reachable functions

719

Percentage of reachable functions covered

75.94%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: PatternParserFuzzer-wchar_t

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	59	23.6%
gold	[1:9]	77	30.9%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	113	45.3%
All colors	249	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
17	159	log4cxx::helpers::Pool::setPool()	call site: 00159	__cxa_allocate_exception
13	178	log4cxx::helpers::Pool::~Pool()	call site: 00178	apr_filepath_get
4	51	log4cxx::pattern::PatternParser::parse(std::__1::basic_string , std::__1::allocator > const&, std::__1::map , std::__1::allocator >, std::__1::function (std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)>, std::__1::less , std::__1::allocator > >, std::__1::allocator , std::__1::allocator > const, std::__1::function (std::__1::vector , std::__1::allocator >, std::__1::allocator , std::__1::allocator > > > const&)> > > > const&)	call site: 00051	__cxa_guard_acquire
4	121	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00121	__cxa_throw
3	87	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00087	__cxa_allocate_exception
2	6	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00006
2	98	log4cxx::helpers::CharsetEncoder::createDefaultEncoder()	call site: 00098
2	213	log4cxx::helpers::LogLog::emit_log(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00213
1	13	log4cxx::helpers::WideLife >::~WideLife()	call site: 00013	__cxa_begin_catch
1	16	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00016
1	46	LLVMFuzzerTestOneInput	call site: 00046
1	56	log4cxx::helpers::WideLife >::~WideLife()	call site: 00056	__cxa_guard_release

Runtime coverage analysis

Covered functions

965

Functions that are reachable but not covered

41

Reachable functions

242

Percentage of reachable functions covered

83.06%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: 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	554	55.8%
gold	[1:9]	138	13.9%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	1	0.10%
lawngreen	50+	299	30.1%
All colors	992	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
54	920	log4cxx::helpers::WideLife ::operator log4cxx::AsyncAppender::ClazzAsyncAppender&()	call site: 00920	__dynamic_cast
32	882	log4cxx::helpers::WideLife ::operator log4cxx::spi::AppenderAttachable::ClazzAppenderAttachable&()	call site: 00882	__cxa_guard_abort
16	636	log4cxx::xml::DOMConfigurator::DOMConfiguratorPrivate::parseChildrenOfLoggerElement(apr_xml_elem*, std::__1::shared_ptr , bool)	call site: 00636	__cxa_guard_acquire
16	699	log4cxx::config::PropertySetter::activate()	call site: 00699	__cxa_begin_catch
14	71	log4cxx::helpers::Pool::setPool()	call site: 00071	__cxa_allocate_exception
14	665	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00665	__cxa_guard_acquire
14	838	log4cxx::helpers::WideLife ::operator log4cxx::rolling::FilterBasedTriggeringPolicy::ClazzFilterBasedTriggeringPolicy&()	call site: 00838	__cxa_begin_catch
13	748	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00748
12	727	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00727
10	586	log4cxx::helpers::WideLife ::operator log4cxx::spi::LoggerFactory::ClazzLoggerFactory&()	call site: 00586	__cxa_begin_catch
10	597	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00597
9	767	log4cxx::helpers::WideLife ::operator log4cxx::AppenderSkeleton::ClazzAppenderSkeleton&()	call site: 00767

Runtime coverage analysis

Covered functions

917

Functions that are reachable but not covered

207

Reachable functions

695

Percentage of reachable functions covered

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

1857

Functions that are reachable but not covered

0

Reachable functions

1

Percentage of reachable functions covered

100.0%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

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

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

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

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
38	51	LLVMFuzzerTestOneInput	call site: 00051
23	25	LLVMFuzzerTestOneInput	call site: 00025
10	6	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00006
5	0	EP	call site: 00000

Runtime coverage analysis

Covered functions

1857

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: /src/logging-log4cxx/src/fuzzers/cpp/TranscoderFuzzer.cpp

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

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

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
10	0	EP	call site: 00000	fprintf
4	26	(anonymous namespace)::exerciseEncoder(std::__1::shared_ptr const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00026	__cxa_begin_catch
3	44	(anonymous namespace)::checkUTF16RoundTrip(unsigned int)	call site: 00044
2	17	(anonymous namespace)::exerciseDecoder(std::__1::shared_ptr const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00017

Runtime coverage analysis

Covered functions

1857

Functions that are reachable but not covered

4

Reachable functions

61

Percentage of reachable functions covered

93.44%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

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

1857

Functions that are reachable but not covered

2

Reachable functions

36

Percentage of reachable functions covered

94.44%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

1857

Functions that are reachable but not covered

3

Reachable functions

8

Percentage of reachable functions covered

62.5%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: PatternConverterFuzzer-utf-8

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	114	28.4%
gold	[1:9]	60	14.9%
yellow	[10:29]	48	11.9%
greenyellow	[30:49]	6	1.49%
lawngreen	50+	173	43.1%
All colors	401	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
17	119	log4cxx::helpers::Pool::setPool()	call site: 00119	__cxa_allocate_exception
16	179	isConsoleWide(_IO_FILE*)	call site: 00179	fputws
13	138	log4cxx::helpers::Pool::~Pool()	call site: 00138	apr_filepath_get
8	321	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00321
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	216	LLVMFuzzerTestOneInput	call site: 00216
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	372	LLVMFuzzerTestOneInput	call site: 00372
3	378	log4cxx::pattern::NDCPatternConverter::format(std::__1::shared_ptr const&, std::__1::basic_string , std::__1::allocator >&, log4cxx::helpers::Pool&) const	call site: 00378
3	386	log4cxx::NDC::get(std::__1::basic_string , std::__1::allocator >&)	call site: 00386
3	396	LLVMFuzzerTestOneInput	call site: 00396

Runtime coverage analysis

Covered functions

979

Functions that are reachable but not covered

113

Reachable functions

405

Percentage of reachable functions covered

72.1%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: 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	534	58.7%
gold	[1:9]	293	32.2%
yellow	[10:29]	16	1.76%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	66	7.26%
All colors	909	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
176	456	log4cxx::helpers::WideLife ::operator log4cxx::helpers::ClassRegistration&()	call site: 00456	_ZN7log4cxx7helpers8WideLifeINS0_17ClassRegistrationEEC2IRFRKNS0_5ClassEvEJEQntsr3stdE7same_asINS1_IT_EETL0__EEEOSA_DpOT0_
17	88	log4cxx::helpers::Pool::setPool()	call site: 00088	__cxa_allocate_exception
16	323	log4cxx::helpers::OptionConverter::substVars(std::__1::basic_string , std::__1::allocator > const&, log4cxx::helpers::Properties&)	call site: 00323	__cxa_allocate_exception
15	140	log4cxx::helpers::LogLog::getInstance()	call site: 00140	fwide
13	107	log4cxx::helpers::Pool::~Pool()	call site: 00107	apr_filepath_get
13	633	log4cxx::PropertyConfigurator::doConfigure(log4cxx::helpers::Properties&, std::__1::shared_ptr )	call site: 00633
12	157	log4cxx::helpers::ByteBuffer::increment_position(unsigned long)	call site: 00157	fputws
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	256	log4cxx::helpers::Properties::load(std::__1::shared_ptr )	call site: 00256	__cxa_allocate_exception
10	297	log4cxx::PropertyConfigurator::doConfigure(log4cxx::File const&, std::__1::shared_ptr )	call site: 00297	__cxa_end_catch
9	787	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00787	__cxa_guard_acquire
8	656	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: 00656	__cxa_allocate_exception

Runtime coverage analysis

Covered functions

1066

Functions that are reachable but not covered

168

Reachable functions

683

Percentage of reachable functions covered

75.4%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: XMLLayoutFuzzer-wchar_t

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	30	15.7%
gold	[1:9]	14	7.32%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	147	76.9%
All colors	191	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
6	112	(anonymous namespace)::appendValidCharacters(std::__1::basic_string , std::__1::allocator >&, std::__1::basic_string , std::__1::allocator > const&, std::__1::function , std::__1::allocator >&, int)>, bool)	call site: 00112
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	141	log4cxx::xml::XMLLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00141
2	23	log4cxx::Layout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00023	apr_pool_destroy
2	45	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00045
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	53	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00053
1	83	LLVMFuzzerTestOneInput	call site: 00083
1	122	log4cxx::helpers::Transform::appendCharacterReference(std::__1::basic_string , std::__1::allocator >&, unsigned int)	call site: 00122
1	135	log4cxx::helpers::Transform::appendEscapingCDATA(std::__1::basic_string , std::__1::allocator >&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00135
1	170	log4cxx::MDC::get(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00170

Runtime coverage analysis

Covered functions

801

Functions that are reachable but not covered

30

Reachable functions

190

Percentage of reachable functions covered

84.21%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/XMLLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/xmllayout.cpp	6
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	3
/src/logging-log4cxx/src/main/cpp/level.cpp	3
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	8
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	5
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	2
/src/logging-log4cxx/src/main/cpp/ndc.cpp	5
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	2
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	4
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	14
/src/logging-log4cxx/src/main/cpp/mdc.cpp	4
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/cpp/transform.cpp	5
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/usr/local/bin/../include/c++/v1/optional	2

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

1857

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

1857

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: TranscoderFuzzer-wchar_t

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	11	7.23%
gold	[1:9]	25	16.4%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	116	76.3%
All colors	152	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
2	6	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00006
2	49	LLVMFuzzerTestOneInput	call site: 00049	fprintf
2	57	log4cxx::helpers::CharsetEncoder::createDefaultEncoder()	call site: 00057
1	13	log4cxx::helpers::WideLife >::~WideLife()	call site: 00013	__cxa_begin_catch
1	16	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00016
1	65	log4cxx::helpers::CharsetEncoder::getDefaultEncoder()	call site: 00065
1	114	log4cxx::helpers::CharsetEncoder::getEncoder(std::__1::basic_string , std::__1::allocator > const&)	call site: 00114
1	125	LLVMFuzzerTestOneInput	call site: 00125	__cxa_end_catch

Runtime coverage analysis

Covered functions

796

Functions that are reachable but not covered

11

Reachable functions

117

Percentage of reachable functions covered

90.6%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

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

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

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

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
15	0	EP	call site: 00000
6	21	log4cxx::spi::LocationInfo::calcShortFileName(char const*)	call site: 00021	remove
4	16	log4cxx::Logger::isDebugEnabledFor(std::__1::shared_ptr const&)	call site: 00016

Runtime coverage analysis

Covered functions

1857

Functions that are reachable but not covered

2

Reachable functions

47

Percentage of reachable functions covered

95.74%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: /src/logging-log4cxx/src/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

1857

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: 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	168	41.8%
gold	[1:9]	75	18.7%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	158	39.4%
All colors	401	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
30	103	log4cxx::helpers::Pool::setPool()	call site: 00103	__cxa_allocate_exception
29	332	log4cxx::helpers::WideLife ::operator log4cxx::helpers::Object::ClazzObject&()	call site: 00332	__cxa_guard_abort
9	285	log4cxx::File::mkdirs() const	call site: 00285	__cxa_rethrow
8	274	log4cxx::FileAppender::setFileInternal(std::__1::basic_string , std::__1::allocator > const&, bool, bool, unsigned long)	call site: 00274
8	307	log4cxx::FileAppender::activateOptionsInternal()	call site: 00307	__cxa_end_catch
7	161	isConsoleWide(_IO_FILE*)	call site: 00161
7	170	log4cxx::helpers::ByteBuffer::increment_position(unsigned long)	call site: 00170	fputws
5	25	LLVMFuzzerTestOneInput	call site: 00025
5	88	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00088	__cxa_allocate_exception
5	300	log4cxx::WriterAppender::WriterAppenderPriv::writeHeader()	call site: 00300	__clang_call_terminate
4	95	log4cxx::helpers::Exception::Exception(std::__1::basic_string , std::__1::allocator > const&)	call site: 00095	__cxa_throw
4	218	log4cxx::WriterAppender::WriterAppenderPriv::close()	call site: 00218

Runtime coverage analysis

Covered functions

1231

Functions that are reachable but not covered

89

Reachable functions

384

Percentage of reachable functions covered

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

Fuzzer: /src/logging-log4cxx/src/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

1857

Functions that are reachable but not covered

4

Reachable functions

36

Percentage of reachable functions covered

88.89%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: TranscoderFuzzer-utf-8

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

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

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
2	20	LLVMFuzzerTestOneInput	call site: 00020	fprintf
1	54	log4cxx::helpers::CharsetEncoder::getEncoder(std::__1::basic_string , std::__1::allocator > const&)	call site: 00054
1	64	LLVMFuzzerTestOneInput	call site: 00064	__cxa_end_catch

Runtime coverage analysis

Covered functions

783

Functions that are reachable but not covered

4

Reachable functions

79

Percentage of reachable functions covered

94.94%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: 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	199	97.0%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	6	2.92%
All colors	205	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
152	52	log4cxx::HTMLLayout::setOption(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00052	__cxa_guard_acquire
45	0	EP	call site: 00000	__cxa_guard_acquire
2	47	log4cxx::HTMLLayout::setOption(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00047

Runtime coverage analysis

Covered functions

696

Functions that are reachable but not covered

179

Reachable functions

192

Percentage of reachable functions covered

6.77%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/HTMLLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/htmllayout.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/timezone.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	8
/src/logging-log4cxx/src/main/cpp/simpledateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	3
/src/logging-log4cxx/src/main/cpp/level.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	3
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	2
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	2
/src/logging-log4cxx/src/main/cpp/transform.cpp	7
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	5
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	1
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/dateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/ndc.cpp	5
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	10
/src/logging-log4cxx/src/main/cpp/mdc.cpp	3
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/usr/local/bin/../include/c++/v1/optional	2

Fuzzer: JSONLayoutFuzzer-utf-8

Call tree

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

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	21	11.9%
gold	[1:9]	2	1.13%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	153	86.9%
All colors	176	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	132	log4cxx::JSONLayout::appendSerializedNDC(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00132
2	87	log4cxx::helpers::DateFormat::format(std::__1::basic_string , std::__1::allocator >&, long) const	call site: 00087	apr_pool_destroy
1	11	log4cxx::helpers::OptionConverter::toBoolean(std::__1::basic_string , std::__1::allocator > const&, bool)	call site: 00011
1	39	log4cxx::helpers::WideLife >::~WideLife()	call site: 00039	__cxa_begin_catch
1	57	LLVMFuzzerTestOneInput	call site: 00057
1	128	log4cxx::MDC::get(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00128
1	139	log4cxx::NDC::get(std::__1::basic_string , std::__1::allocator >&)	call site: 00139

Runtime coverage analysis

Covered functions

835

Functions that are reachable but not covered

29

Reachable functions

175

Percentage of reachable functions covered

83.43%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/JSONLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/jsonlayout.cpp	14
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	1
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	3
/src/logging-log4cxx/src/main/cpp/level.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	4
/src/logging-log4cxx/src/main/cpp/ndc.cpp	5
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	5
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	12
/src/logging-log4cxx/src/main/cpp/mdc.cpp	4
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	1
/src/logging-log4cxx/src/main/cpp/dateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	5
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	1
/usr/local/bin/../include/c++/v1/optional	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	433	98.4%
gold	[1:9]	3	0.68%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	4	0.90%
All colors	440	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
242	197	log4cxx::helpers::System::getProperty(std::__1::basic_string , std::__1::allocator > const&)	call site: 00197	apr_uid_current
98	0	EP	call site: 00000	__cxa_guard_acquire
45	99	log4cxx::helpers::WideLife ::WideLife()	call site: 00099	__cxa_allocate_exception
36	156	log4cxx::helpers::WideLife ::WideLife()	call site: 00156	apr_pool_create_ex
10	145	log4cxx::helpers::WideLife<(anonymous namespace)::apr_environment>::WideLife()	call site: 00145	apr_initialize
2	193	log4cxx::helpers::System::getProperty(std::__1::basic_string , std::__1::allocator > const&)	call site: 00193	apr_filepath_get

Runtime coverage analysis

Covered functions

696

Functions that are reachable but not covered

410

Reachable functions

437

Percentage of reachable functions covered

6.18%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: 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	31	14.0%
gold	[1:9]	17	7.72%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	172	78.1%
All colors	220	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	146	log4cxx::spi::LoggingEvent::LoggingEventPrivate::renderMessage()	call site: 00146
4	86	(anonymous namespace)::appendCharacterReferenceHandler(std::__1::basic_string , std::__1::allocator >&, int)	call site: 00086
3	1	LLVMFuzzerTestOneInput	call site: 00001
3	177	log4cxx::Level::getWarn()	call site: 00177
3	196	log4cxx::HTMLLayout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&, log4cxx::helpers::Pool&) const	call site: 00196
2	35	log4cxx::Layout::format(std::__1::basic_string , std::__1::allocator >&, std::__1::shared_ptr const&) const	call site: 00035	apr_pool_destroy
2	58	log4cxx::helpers::CharsetDecoder::createDefaultDecoder()	call site: 00058
2	96	(anonymous namespace)::appendValidCharacters(std::__1::basic_string , std::__1::allocator >&, std::__1::basic_string , std::__1::allocator > const&, std::__1::function , std::__1::allocator >&, int)>, bool)	call site: 00096
1	12	log4cxx::helpers::WideLife >::~WideLife()	call site: 00012	__cxa_begin_catch
1	48	log4cxx::helpers::OptionConverter::toBoolean(std::__1::basic_string , std::__1::allocator > const&, bool)	call site: 00048
1	66	log4cxx::helpers::CharsetDecoder::getDefaultDecoder()	call site: 00066
1	130	LLVMFuzzerTestOneInput	call site: 00130

Runtime coverage analysis

Covered functions

849

Functions that are reachable but not covered

30

Reachable functions

207

Percentage of reachable functions covered

85.51%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
/src/logging-log4cxx/src/fuzzers/cpp/HTMLLayoutFuzzer.cpp	1
/src/logging-log4cxx/src/main/cpp/htmllayout.cpp	8
/src/logging-log4cxx/src/main/include/log4cxx/helpers/object.h	2
/src/logging-log4cxx/src/main/include/log4cxx/spi/optionhandler.h	2
/src/logging-log4cxx/src/main/include/log4cxx/layout.h	1
/src/logging-log4cxx/src/main/cpp/timezone.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/helpers/widelife.h	12
/src/logging-log4cxx/src/main/cpp/simpledateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/layout.cpp	3
/src/logging-log4cxx/src/main/cpp/level.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/spi/location/locationinfo.h	1
/src/logging-log4cxx/src/main/cpp/locationinfo.cpp	3
/src/logging-log4cxx/src/main/cpp/pool.cpp	2
/src/logging-log4cxx/src/main/include/log4cxx/private/layout_priv.h	2
/src/logging-log4cxx/src/main/cpp/stringhelper.cpp	2
/src/logging-log4cxx/src/main/cpp/optionconverter.cpp	1
/src/logging-log4cxx/src/main/cpp/transcoder.cpp	2
/src/logging-log4cxx/src/main/cpp/charsetdecoder.cpp	4
/src/logging-log4cxx/src/main/cpp/bytebuffer.cpp	4
/src/logging-log4cxx/src/main/include/log4cxx/helpers/charsetdecoder.h	1
/src/logging-log4cxx/src/main/cpp/transform.cpp	7
/src/logging-log4cxx/src/main/cpp/date.cpp	2
/src/logging-log4cxx/src/main/cpp/dateformat.cpp	1
/src/logging-log4cxx/src/main/cpp/ndc.cpp	5
/src/logging-log4cxx/src/main/cpp/threadspecificdata.cpp	8
/src/logging-log4cxx/src/main/cpp/loggingevent.cpp	10
/src/logging-log4cxx/src/main/cpp/mdc.cpp	3
/src/logging-log4cxx/src/main/cpp/asyncbuffer.cpp	3
/src/logging-log4cxx/src/main/cpp/messagebuffer.cpp	4
/usr/local/bin/../include/c++/v1/sstream	2
/usr/local/bin/../include/c++/v1/optional	2

Fuzzer: 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	189	42.5%
gold	[1:9]	69	15.5%
yellow	[10:29]	2	0.45%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	184	41.4%
All colors	444	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
30	157	log4cxx::helpers::Pool::setPool()	call site: 00157	__cxa_allocate_exception
29	374	log4cxx::helpers::WideLife ::operator log4cxx::helpers::Object::ClazzObject&()	call site: 00374	__cxa_guard_abort
13	207	log4cxx::helpers::LogLog::getInstance()	call site: 00207	fwide
12	141	log4cxx::helpers::Transcoder::encode(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator >&)	call site: 00141	__cxa_throw
10	257	log4cxx::WriterAppender::WriterAppenderPriv::close()	call site: 00257	__cxa_end_catch
9	327	log4cxx::File::mkdirs() const	call site: 00327	__cxa_rethrow
8	316	log4cxx::FileAppender::setFileInternal(std::__1::basic_string , std::__1::allocator > const&, bool, bool, unsigned long)	call site: 00316
8	349	log4cxx::FileAppender::activateOptionsInternal()	call site: 00349	__cxa_end_catch
6	115	log4cxx::helpers::OptionConverter::getSystemProperty(std::__1::basic_string , std::__1::allocator > const&, std::__1::basic_string , std::__1::allocator > const&)	call site: 00115	__cxa_allocate_exception
5	25	LLVMFuzzerTestOneInput	call site: 00025
5	342	log4cxx::WriterAppender::WriterAppenderPriv::writeHeader()	call site: 00342	__clang_call_terminate
4	282	log4cxx::File::FilePrivate::set_apr_path()	call site: 00282

Runtime coverage analysis

Covered functions

1241

Functions that are reachable but not covered

98

Reachable functions

422

Percentage of reachable functions covered

76.78%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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

Fuzzer: /src/logging-log4cxx/src/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

1857

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

1857

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	568	55.0%
gold	[1:9]	169	16.3%
yellow	[10:29]	32	3.10%
greenyellow	[30:49]	7	0.67%
lawngreen	50+	255	24.7%
All colors	1031	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
54	959	log4cxx::helpers::WideLife ::operator log4cxx::AsyncAppender::ClazzAsyncAppender&()	call site: 00959	__dynamic_cast
32	921	log4cxx::helpers::WideLife ::operator log4cxx::spi::AppenderAttachable::ClazzAppenderAttachable&()	call site: 00921	__cxa_guard_abort
17	125	log4cxx::helpers::Pool::setPool()	call site: 00125	__cxa_allocate_exception
16	675	log4cxx::xml::DOMConfigurator::DOMConfiguratorPrivate::parseChildrenOfLoggerElement(apr_xml_elem*, std::__1::shared_ptr , bool)	call site: 00675	__cxa_guard_acquire
16	738	log4cxx::config::PropertySetter::activate()	call site: 00738	__cxa_begin_catch
14	704	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00704	__cxa_guard_acquire
14	877	log4cxx::helpers::WideLife ::operator log4cxx::rolling::FilterBasedTriggeringPolicy::ClazzFilterBasedTriggeringPolicy&()	call site: 00877	__cxa_begin_catch
13	787	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00787
12	766	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00766
10	625	log4cxx::helpers::WideLife ::operator log4cxx::spi::LoggerFactory::ClazzLoggerFactory&()	call site: 00625	__cxa_begin_catch
10	636	std::__1::shared_ptr log4cxx::cast (std::__1::shared_ptr const&)	call site: 00636
9	610	log4cxx::xml::DOMConfigurator::DOMConfiguratorPrivate::parse(apr_xml_elem*)	call site: 00610

Runtime coverage analysis

Covered functions

922

Functions that are reachable but not covered

203

Reachable functions

727

Percentage of reachable functions covered

72.08%

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

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

Function name	source code lines	source lines hit	percentage hit

Files reached

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