Report generation date: 2025-07-01

Project overview: immer

High level conclusions

Fuzzers reach 83.28% of cyclomatic complexity.

"No files with coverage data was found. This is either because an error occurred when compiling and running coverage runs, or because the introspector run was intentionally done without coverage collection. In order to get optimal results coverage data is needed.

Reachability and coverage overview

Functions statically reachable by fuzzers

4778 / 6516

Cyclomatic complexity statically reachable by fuzzers

25827 / 31010

Runtime code coverage of functions

0 / 6516

Fuzzers overview

Fuzzer	Fuzzer filename	Functions Reached	Functions unreached	Fuzzer depth	Files reached	Basic blocks reached	Cyclomatic complexity	Details
set	/src/immer/extra/fuzzer/set.cpp	290	65	11	16	1065	503	set.cpp
array-gc	/src/immer/extra/fuzzer/array-gc.cpp	225	25	9	14	487	374	array-gc.cpp
set-gc	/src/immer/extra/fuzzer/set-gc.cpp	254	51	11	14	794	412	set-gc.cpp
map-gc	/src/immer/extra/fuzzer/map-gc.cpp	318	63	11	16	1098	671	map-gc.cpp
array	/src/immer/extra/fuzzer/array.cpp	158	19	11	12	362	261	array.cpp
vector-gc	/src/immer/extra/fuzzer/vector-gc.cpp	471	143	13	15	1404	809	vector-gc.cpp
vector-st	/src/immer/extra/fuzzer/vector-st.cpp	417	138	13	13	1288	732	vector-st.cpp
map	/src/immer/extra/fuzzer/map.cpp	385	64	11	16	1704	862	map.cpp
set-st	/src/immer/extra/fuzzer/set-st.cpp	310	66	11	15	1269	592	set-st.cpp
vector	/src/immer/extra/fuzzer/vector.cpp	446	138	13	19	1411	775	vector.cpp
set-st-str	/src/immer/extra/fuzzer/set-st-str.cpp	318	66	11	15	1692	1055	set-st-str.cpp
set-st-str-conflict	/src/immer/extra/fuzzer/set-st-str-conflict.cpp	320	66	11	15	1695	1057	set-st-str-conflict.cpp
map-st	/src/immer/extra/fuzzer/map-st.cpp	361	64	11	15	1539	760	map-st.cpp
map-st-str-conflict	/src/immer/extra/fuzzer/map-st-str-conflict.cpp	400	77	11	18	2355	1532	map-st-str-conflict.cpp
map-st-str	/src/immer/extra/fuzzer/map-st-str.cpp	398	77	11	18	2352	1530	map-st-str.cpp
flex-vector-st	/src/immer/extra/fuzzer/flex-vector-st.cpp	1856	355	19	19	8315	4746	flex-vector-st.cpp
flex-vector-bo	/src/immer/extra/fuzzer/flex-vector-bo.cpp	1835	356	19	19	8212	4680	flex-vector-bo.cpp
flex-vector	/src/immer/extra/fuzzer/flex-vector.cpp	1886	355	19	23	8440	4774	flex-vector.cpp
flex-vector-gc	/src/immer/extra/fuzzer/flex-vector-gc.cpp	1902	336	19	16	8205	4710	flex-vector-gc.cpp

Project functions overview

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	Fuzzers runtime hit	Func lines hit %	I Count	BB Count	Cyclomatic complexity	Functions reached	Reached by functions	Accumulated cyclomatic complexity	Undiscovered complexity

Fuzzer details

Fuzzer: set

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: array-gc

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: set-gc

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: map-gc

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: array

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: vector-gc

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: vector-st

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: map

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: set-st

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: vector

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: set-st-str

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: set-st-str-conflict

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: map-st

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: map-st-str-conflict

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: map-st-str

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: flex-vector-st

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: flex-vector-bo

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: flex-vector

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Fuzzer: flex-vector-gc

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

Full calltree

Call tree overview bitmap:

The project has no code coverage. Will not display blockers as blockers depend on code coverage.

Analyses and suggestions

Optimal target analysis

Remaining optimal interesting functions

The following table shows a list of functions that are optimal targets. Optimal targets are identified by finding the functions that in combination, yield a high code coverage.

Func name	Functions filename	Arg count	Args	Function depth	instr count	bb count	cyclomatic complexity	Reachable functions	total cyclomatic complexity	Unreached complexity
decltype(auto)immer::detail::rbts::regular_sub_pos ,immer::unsafe_refcount_policy,immer::no_lock_policy,immer::no_transience_policy,false,true>,2u,2u>>::visit ,immer::unsafe_refcount_policy,immer::no_lock_policy,immer::no_transience_policy,false,true>,2u,2u>,true,true>,unsignedlong&,immer::no_transience_policy::apply >::type::edit&>(immer::detail::rbts::slice_right_mut_visitor ,immer::unsafe_refcount_policy,immer::no_lock_policy,immer::no_transience_policy,false,true>,2u,2u>,true,true>,unsignedlong&,immer::no_transience_policy::apply >::type::edit&)	/src/immer/immer/detail/rbts/position.hpp	4	['class.std::__1::tuple ', 'struct.immer::detail::rbts::regular_sub_pos ', 'size_t ', 'struct.immer::detail::rbts::dec_visitor ']	36	30	3	2	246	772	617
`decltype(auto)immer::detail::rbts::regular_sub_pos ,immer::unsafe_refcount_policy,immer::no_lock_policy,immer::no_transience_policy,false,true>,2u,2u>>::visit ,immer::unsafe_refcount_policy,immer::no_lock_policy,immer::no_transience_policy,false,true>,2u,2u>,true>,unsignedlong&>(immer::detail::rbts::slice_right_visitor ,immer::unsafe_refcount_policy,immer::no_lock_policy,immer::no_transience_policy,false,true>,2u,2u>,true>,unsignedlong&)`	/src/immer/immer/detail/rbts/position.hpp	3	['class.std::__1::tuple ', 'struct.immer::detail::rbts::regular_sub_pos ', 'size_t *']	24	24	3	2	121	308	229
decltype(auto)immer::detail::rbts::full_pos ,immer::no_refcount_policy,immer::spinlock_policy,immer::gc_transience_policy,false,false>,2u,2u>>::visit ,immer::no_refcount_policy,immer::spinlock_policy,immer::gc_transience_policy,false,false>,2u,2u>>,immer::gc_transience_policy::apply >::type::edit&,immer::gc_transience_policy::apply >::type::edit&,immer::detail::rbts::relaxed_pos ,immer::no_refcount_policy,immer::spinlock_policy,immer::gc_transience_policy,false,false>,2u,2u>>&,immer::detail::rbts::leaf_pos ,immer::no_refcount_policy,immer::spinlock_policy,immer::gc_transience_policy,false,false>,2u,2u>>&,immer::gc_transience_policy::apply >::type::edit&>(immer::detail::rbts::concat_right_mut_visitor ,immer::no_refcount_policy,immer::spinlock_policy,immer::gc_transience_policy,false,false>,2u,2u>>,immer::gc_transience_policy::apply >::type::edit&,immer::gc_transience_policy::apply >::type::edit&,immer::detail::rbts::relaxed_pos ,immer::no_refcount_policy,immer::spinlock_policy,immer::gc_transience_policy,false,false>,2u,2u>>&,immer::detail::rbts::leaf_pos ,immer::no_refcount_policy,immer::spinlock_policy,immer::gc_transience_policy,false,false>,2u,2u>>&,immer::gc_transience_policy::apply >::type::edit&)	/src/immer/immer/detail/rbts/position.hpp	7	['struct.immer::detail::rbts::concat_center_pos ', 'struct.immer::detail::rbts::leaf_sub_pos ', 'struct.std::__1::__cxx_atomic_base_impl ', 'struct.std::__1::__cxx_atomic_base_impl ', 'struct.immer::detail::rbts::relaxed_pos ', 'struct.immer::detail::rbts::leaf_pos ', 'struct.std::__1::__cxx_atomic_base_impl *']	24	43	3	2	359	573	175

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

Functions statically reachable by fuzzers

4887 / 6516

Cyclomatic complexity statically reachable by fuzzers

26848 / 31010

All functions overview

If you implement fuzzers for these functions, the status of all functions in the project will be:

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

Fuzz engine guidance

This sections provides heuristics that can be used as input to a fuzz engine when running a given fuzz target. The current focus is on providing input that is usable by libFuzzer.

/src/immer/extra/fuzzer/set.cpp

Dictionary

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

/src/immer/extra/fuzzer/array-gc.cpp

Dictionary

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

/src/immer/extra/fuzzer/set-gc.cpp

Dictionary

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

/src/immer/extra/fuzzer/map-gc.cpp

Dictionary

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

/src/immer/extra/fuzzer/array.cpp

Dictionary

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

/src/immer/extra/fuzzer/vector-gc.cpp

Dictionary

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

/src/immer/extra/fuzzer/vector-st.cpp

Dictionary

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

/src/immer/extra/fuzzer/map.cpp

Dictionary

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

/src/immer/extra/fuzzer/set-st.cpp

Dictionary

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

/src/immer/extra/fuzzer/vector.cpp

Dictionary

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

/src/immer/extra/fuzzer/set-st-str.cpp

Dictionary

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

/src/immer/extra/fuzzer/set-st-str-conflict.cpp

Dictionary

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

/src/immer/extra/fuzzer/map-st.cpp

Dictionary

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

/src/immer/extra/fuzzer/map-st-str-conflict.cpp

Dictionary

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

/src/immer/extra/fuzzer/map-st-str.cpp

Dictionary

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

/src/immer/extra/fuzzer/flex-vector-st.cpp

Dictionary

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

/src/immer/extra/fuzzer/flex-vector-bo.cpp

Dictionary

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

/src/immer/extra/fuzzer/flex-vector.cpp

Dictionary

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

/src/immer/extra/fuzzer/flex-vector-gc.cpp

Dictionary

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

Runtime coverage analysis

No runtime coverage data was found

Files and Directories in report

This section shows which files and directories are considered in this report. The main reason for showing this is fuzz introspector may include more code in the reasoning than is desired. This section helps identify if too many files/directories are included, e.g. third party code, which may be irrelevant for the threat model. In the event too much is included, fuzz introspector supports a configuration file that can exclude data from the report. See the following link for more information on how to create a config file: link

Files in report

Source file	Reached by	Covered by
	[]	[]
/src/immer/extra/fuzzer/fuzzer_input.hpp	['set', 'array-gc', 'set-gc', 'map-gc', 'array', 'vector-gc', 'vector-st', 'map', 'set-st', 'vector', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str', 'flex-vector-st', 'flex-vector-bo', 'flex-vector', 'flex-vector-gc']	[]
/src/immer/immer/detail/arrays/with_capacity.hpp	['array-gc', 'array']	[]
/src/immer/immer/detail/rbts/rrbtree_iterator.hpp	['flex-vector-st', 'flex-vector-bo', 'flex-vector']	[]
/src/immer/immer/algorithm.hpp	['set', 'set-gc', 'map-gc', 'map', 'set-st', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str']	[]
/src/immer/extra/fuzzer/map-gc.cpp	['map-gc']	[]
/src/immer/immer/transience/no_transience_policy.hpp	['set', 'array', 'vector-st', 'map', 'set-st', 'vector', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str', 'flex-vector-st', 'flex-vector-bo', 'flex-vector']	[]
/src/immer/immer/refcount/unsafe_refcount_policy.hpp	['vector-st', 'set-st', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str', 'flex-vector-st', 'flex-vector-bo']	[]
/src/immer/immer/detail/rbts/rrbtree.hpp	['flex-vector-st', 'flex-vector-bo', 'flex-vector', 'flex-vector-gc']	[]
/src/immer/immer/detail/rbts/rbtree.hpp	['vector-gc', 'vector-st', 'vector']	[]
/src/immer/immer/box.hpp	['map-st-str-conflict', 'map-st-str', 'flex-vector-st', 'flex-vector-bo', 'flex-vector']	[]
/src/immer/immer/detail/rbts/position.hpp	['vector-gc', 'vector-st', 'vector', 'flex-vector-st', 'flex-vector-bo', 'flex-vector', 'flex-vector-gc']	[]
/src/immer/extra/fuzzer/vector-gc.cpp	['vector-gc']	[]
/src/immer/extra/fuzzer/set.cpp	['set']	[]
/src/immer/immer/heap/free_list_heap.hpp	['vector', 'flex-vector']	[]
/src/immer/immer/detail/iterator_facade.hpp	['set', 'map-gc', 'map', 'set-st', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str', 'flex-vector-st', 'flex-vector-bo', 'flex-vector']	[]
/src/immer/extra/fuzzer/set-st-str.cpp	['set-st-str']	[]
/src/immer/extra/fuzzer/flex-vector-bo.cpp	['flex-vector-bo']	[]
/src/immer/immer/detail/rbts/operations.hpp	['vector-gc', 'vector-st', 'vector', 'flex-vector-st', 'flex-vector-bo', 'flex-vector', 'flex-vector-gc']	[]
/src/immer/extra/fuzzer/map.cpp	['map']	[]
/src/immer/immer/detail/combine_standard_layout.hpp	['set', 'array-gc', 'set-gc', 'map-gc', 'array', 'vector-gc', 'vector-st', 'map', 'set-st', 'vector', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str', 'flex-vector-st', 'flex-vector-bo', 'flex-vector', 'flex-vector-gc']	[]
/src/immer/extra/fuzzer/fuzzer_gc_guard.hpp	['array-gc', 'set-gc', 'map-gc', 'vector-gc', 'flex-vector-gc']	[]
/src/immer/extra/fuzzer/map-st-str.cpp	['map-st-str']	[]
/src/immer/immer/heap/unsafe_free_list_heap.hpp	['vector', 'flex-vector']	[]
/src/immer/immer/heap/with_data.hpp	['vector', 'flex-vector']	[]
/src/immer/immer/detail/hamts/champ.hpp	['set', 'set-gc', 'map-gc', 'map', 'set-st', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str']	[]
/src/immer/immer/refcount/no_refcount_policy.hpp	['array-gc', 'set-gc', 'map-gc', 'vector-gc', 'flex-vector-gc']	[]
/src/immer/immer/flex_vector.hpp	['flex-vector-st', 'flex-vector-bo', 'flex-vector', 'flex-vector-gc']	[]
/src/immer/extra/fuzzer/flex-vector-gc.cpp	['flex-vector-gc']	[]
/src/immer/immer/heap/split_heap.hpp	['vector', 'flex-vector']	[]
/src/immer/extra/fuzzer/set-gc.cpp	['set-gc']	[]
/src/immer/immer/heap/cpp_heap.hpp	['set', 'array', 'vector-st', 'map', 'set-st', 'vector', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str', 'flex-vector-st', 'flex-vector-bo', 'flex-vector']	[]
/src/immer/immer/heap/gc_heap.hpp	['array-gc', 'set-gc', 'map-gc', 'vector-gc', 'flex-vector-gc']	[]
/src/immer/immer/detail/hamts/champ_iterator.hpp	['set', 'map-gc', 'map', 'set-st', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str']	[]
/src/immer/immer/detail/arrays/node.hpp	['array-gc', 'array']	[]
/src/immer/immer/vector.hpp	['vector-gc', 'vector-st', 'vector']	[]
/src/immer/extra/fuzzer/map-st.cpp	['map-st']	[]
/src/immer/extra/fuzzer/array.cpp	['array']	[]
/src/immer/immer/map.hpp	['map-gc', 'map', 'map-st', 'map-st-str-conflict', 'map-st-str']	[]
/src/immer/extra/fuzzer/set-st.cpp	['set-st']	[]
/src/immer/immer/array.hpp	['array-gc', 'array']	[]
/src/immer/extra/fuzzer/vector-st.cpp	['vector-st']	[]
/src/immer/immer/detail/hamts/node.hpp	['set', 'set-gc', 'map-gc', 'map', 'set-st', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str']	[]
/src/immer/immer/detail/arrays/no_capacity.hpp	['array-gc']	[]
/src/immer/extra/fuzzer/flex-vector-st.cpp	['flex-vector-st']	[]
/src/immer/immer/transience/gc_transience_policy.hpp	['array-gc', 'set-gc', 'map-gc', 'vector-gc', 'flex-vector-gc']	[]
/src/immer/extra/fuzzer/vector.cpp	['vector']	[]
/src/immer/extra/fuzzer/map-st-str-conflict.cpp	['map-st-str-conflict']	[]
/src/immer/immer/detail/rbts/visitor.hpp	['flex-vector-st', 'flex-vector-bo', 'flex-vector', 'flex-vector-gc']	[]
/src/immer/extra/fuzzer/array-gc.cpp	['array-gc']	[]
/src/immer/immer/vector_transient.hpp	['vector-gc']	[]
/src/immer/extra/fuzzer/set-st-str-conflict.cpp	['set-st-str-conflict']	[]
/src/immer/immer/flex_vector_transient.hpp	['flex-vector-gc']	[]
/src/immer/immer/detail/hamts/bits.hpp	['set', 'set-gc', 'map-gc', 'map', 'set-st', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str']	[]
/usr/local/bin/../include/c++/v1/exception	['set', 'array-gc', 'set-gc', 'map-gc', 'array', 'vector-gc', 'vector-st', 'map', 'set-st', 'vector', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str', 'flex-vector-st', 'flex-vector-bo', 'flex-vector', 'flex-vector-gc']	[]
/src/immer/immer/heap/thread_local_free_list_heap.hpp	['vector', 'flex-vector']	[]
/src/immer/immer/detail/util.hpp	['set', 'array-gc', 'set-gc', 'map-gc', 'array', 'vector-gc', 'vector-st', 'map', 'set-st', 'vector', 'set-st-str', 'set-st-str-conflict', 'map-st', 'map-st-str-conflict', 'map-st-str', 'flex-vector-st', 'flex-vector-bo', 'flex-vector', 'flex-vector-gc']	[]
/src/immer/immer/heap/debug_size_heap.hpp	['set', 'array', 'map', 'vector', 'map-st-str-conflict', 'map-st-str', 'flex-vector-st', 'flex-vector-bo', 'flex-vector']	[]
/src/immer/extra/fuzzer/flex-vector.cpp	['flex-vector']	[]
/src/immer/immer/set.hpp	['set', 'set-gc', 'set-st', 'set-st-str', 'set-st-str-conflict']	[]
/src/immer/immer/array_transient.hpp	['array-gc']	[]
/src/immer/immer/detail/rbts/node.hpp	['vector-gc', 'vector-st', 'vector', 'flex-vector-st', 'flex-vector-bo', 'flex-vector', 'flex-vector-gc']	[]
/src/immer/immer/refcount/refcount_policy.hpp	['set', 'array', 'map', 'vector', 'map-st-str-conflict', 'map-st-str', 'flex-vector-st', 'flex-vector-bo', 'flex-vector']	[]

Directories in report

Directory

/src/immer/immer/detail/arrays/
/usr/local/bin/../include/c++/v1/
/src/immer/immer/heap/
/src/immer/immer/refcount/
/src/immer/immer/detail/
/src/immer/immer/transience/
/src/immer/extra/fuzzer/
/src/immer/immer/
/src/immer/immer/detail/hamts/
/src/immer/immer/detail/rbts/

Metadata section

This sections shows the raw data that is used to produce this report. This is mainly used for further processing and developer debugging.

Fuzzer	Calltree file	Program data file
set	fuzzerLogFile-0-JHzMD39cLe.data	fuzzerLogFile-0-JHzMD39cLe.data.yaml
array-gc	fuzzerLogFile-0-EyuP0vWLjd.data	fuzzerLogFile-0-EyuP0vWLjd.data.yaml
set-gc	fuzzerLogFile-0-w7V2C5HpIX.data	fuzzerLogFile-0-w7V2C5HpIX.data.yaml
map-gc	fuzzerLogFile-0-PyTLJ01M4R.data	fuzzerLogFile-0-PyTLJ01M4R.data.yaml
array	fuzzerLogFile-0-eH1AP9ssUF.data	fuzzerLogFile-0-eH1AP9ssUF.data.yaml
vector-gc	fuzzerLogFile-0-TH5pQmaBx5.data	fuzzerLogFile-0-TH5pQmaBx5.data.yaml
vector-st	fuzzerLogFile-0-x3mapnnK8M.data	fuzzerLogFile-0-x3mapnnK8M.data.yaml
map	fuzzerLogFile-0-tGb9t8Tmxr.data	fuzzerLogFile-0-tGb9t8Tmxr.data.yaml
set-st	fuzzerLogFile-0-N4gnJTi4ex.data	fuzzerLogFile-0-N4gnJTi4ex.data.yaml
vector	fuzzerLogFile-0-rMkjVlcslh.data	fuzzerLogFile-0-rMkjVlcslh.data.yaml
set-st-str	fuzzerLogFile-0-37Whh6gFXo.data	fuzzerLogFile-0-37Whh6gFXo.data.yaml
set-st-str-conflict	fuzzerLogFile-0-3CnFfuqWxd.data	fuzzerLogFile-0-3CnFfuqWxd.data.yaml
map-st	fuzzerLogFile-0-ScHZbrmc3B.data	fuzzerLogFile-0-ScHZbrmc3B.data.yaml
map-st-str-conflict	fuzzerLogFile-0-K2IfJCxv0H.data	fuzzerLogFile-0-K2IfJCxv0H.data.yaml
map-st-str	fuzzerLogFile-0-RTKjfAi13Q.data	fuzzerLogFile-0-RTKjfAi13Q.data.yaml
flex-vector-st	fuzzerLogFile-0-1vSJmkVCkH.data	fuzzerLogFile-0-1vSJmkVCkH.data.yaml
flex-vector-bo	fuzzerLogFile-0-Sc2QbAO1uL.data	fuzzerLogFile-0-Sc2QbAO1uL.data.yaml
flex-vector	fuzzerLogFile-0-yG9WlG8ZBl.data	fuzzerLogFile-0-yG9WlG8ZBl.data.yaml
flex-vector-gc	fuzzerLogFile-0-XSZB4rHuqO.data	fuzzerLogFile-0-XSZB4rHuqO.data.yaml

Table of contents

Project overview: immer

High level conclusions

Reachability and coverage overview

Fuzzers overview

Project functions overview

Fuzzer details

Fuzzer: set

Call tree

Fuzzer: array-gc

Call tree

Fuzzer: set-gc

Call tree

Fuzzer: map-gc

Call tree

Fuzzer: array

Call tree

Fuzzer: vector-gc

Call tree

Fuzzer: vector-st

Call tree

Fuzzer: map

Call tree

Fuzzer: set-st

Call tree

Fuzzer: vector

Call tree

Fuzzer: set-st-str

Call tree

Fuzzer: set-st-str-conflict

Call tree

Fuzzer: map-st

Call tree

Fuzzer: map-st-str-conflict

Call tree

Fuzzer: map-st-str

Call tree

Fuzzer: flex-vector-st

Call tree

Fuzzer: flex-vector-bo

Call tree

Fuzzer: flex-vector

Call tree

Fuzzer: flex-vector-gc

Call tree

Analyses and suggestions

Optimal target analysis

Remaining optimal interesting functions

All functions overview

Fuzz engine guidance

/src/immer/extra/fuzzer/set.cpp

Dictionary

/src/immer/extra/fuzzer/array-gc.cpp

Dictionary

/src/immer/extra/fuzzer/set-gc.cpp

Dictionary

/src/immer/extra/fuzzer/map-gc.cpp

Dictionary

/src/immer/extra/fuzzer/array.cpp

Dictionary

/src/immer/extra/fuzzer/vector-gc.cpp

Dictionary

/src/immer/extra/fuzzer/vector-st.cpp

Dictionary

/src/immer/extra/fuzzer/map.cpp

Dictionary

/src/immer/extra/fuzzer/set-st.cpp

Dictionary

/src/immer/extra/fuzzer/vector.cpp

Dictionary

/src/immer/extra/fuzzer/set-st-str.cpp

Dictionary

/src/immer/extra/fuzzer/set-st-str-conflict.cpp

Dictionary

/src/immer/extra/fuzzer/map-st.cpp

Dictionary

/src/immer/extra/fuzzer/map-st-str-conflict.cpp

Dictionary

/src/immer/extra/fuzzer/map-st-str.cpp

Dictionary