mimalloc

History

daan ff9f29660b remove double_free call		2019-10-28 12:27:32 -07:00
..
CMakeLists.txt	more comments	2019-07-23 15:00:13 -07:00
main-override-static.c	fix double free check in secure = 4 mode; inline _mi_ptr_cookie	2019-10-19 08:34:18 -07:00
main-override.c	update test files and overriding	2019-07-23 15:00:13 -07:00
main-override.cpp	remove double_free call	2019-10-28 12:27:32 -07:00
main.c	remove lock code from atomics (as it is unused)	2019-06-24 17:54:41 -07:00
readme.md	Add initial testing file, test target, and readme about testing, issue #10 , pr #57	2019-06-27 13:36:19 -07:00
test-api.c	limit aligned allocation to power-of-two alignment	2019-09-11 17:49:28 -07:00
test-stress.c	improve page_free_extend performance slightly; do not maintain expensive statistics in release mode	2019-09-06 16:48:48 -07:00

readme.md

Testing allocators is difficult as bugs may only surface after particular allocation patterns. The main approach to testing mimalloc is therefore to have extensive internal invariant checking (see page_is_valid in page.c for example), which is enabled in debug mode with -DMI_CHECK_FULL=ON. The main testing strategy is then to run mimalloc-bench using full invariant checking to catch any potential problems over a wide range of intensive allocation benchmarks and programs.

However, this does not test well for the entire API surface and this is tested with test-api.c when using make test (from out/debug etc). (This is not complete yet, please add to it.)

The main.c and main-override.c are there to test if building and overriding from a local install works and therefore these build a separate test/CMakeLists.txt.