mimalloc/test
2021-02-24 15:49:43 -08:00
..
CMakeLists.txt bump version to 1.7.0 2021-01-31 13:51:19 -08:00
main-override-static.c fix statistics to include padding correctly (issue #301) 2020-10-11 13:14:43 -07:00
main-override.c update test files and overriding 2019-07-23 15:00:13 -07:00
main-override.cpp use 2-6TiB area for hints to accommodate pre-windows8 better 2021-02-24 15:49:43 -08:00
main.c remove lock code from atomics (as it is unused) 2019-06-24 17:54:41 -07:00
readme.md update documentation 2019-11-21 16:09:34 -08:00
test-api.c Add test to exercise mi_usable_size on aligned allocations 2020-04-06 22:50:21 +10:00
test-stress.c update override on macOS with interpose of malloc_default_zone (issues #313) 2020-12-15 16:03:54 -08:00

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_DEBUG_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.