mimalloc/test
2024-10-21 05:04:27 -07:00
..
CMakeLists.txt initial progress on valgrind integration 2022-10-28 19:54:56 -07:00
main-override-static.c Merge branch 'dev-guarded' into dev 2024-08-21 11:30:33 -07:00
main-override.c
main-override.cpp add test for issue #944 2024-10-21 05:04:27 -07:00
main.c
readme.md
test-api-fill.c fix multi-threaded free to unprotect guarded blocks 2024-08-20 09:55:57 -07:00
test-api.c initial working guarded pages 2024-08-19 21:21:40 -07:00
test-stress.c increase TSAN test to 400 iterations 2024-08-21 17:13:51 -07:00
test-wrong.c add documentation for tracking tools; rename with prefix MI_TRACK_tool 2023-03-06 09:02:38 -08:00
testhelper.h Fix whitespace 2022-12-03 00:24:20 +01: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.