mimalloc/test
David CARLIER 5834751ca6 api test conceal gcc pragma 2021-10-20 16:17:13 +01:00
..
CMakeLists.txt fix installation directories on unix to use /lib, /include, /share; fix issues #399, #223, and #89 2021-05-21 15:15:50 -07: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 update tests with static 2021-07-26 19:14:29 -07: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 api test conceal gcc pragma 2021-10-20 16:17:13 +01:00
test-stress.c fixes for M1; disable interpose use zones; fix pedantic warnings 2021-06-17 19:15:09 -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_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.