mimalloc/test
2023-02-07 11:07:52 -08:00
..
CMakeLists.txt initial progress on valgrind integration 2022-10-28 19:54:56 -07:00
main-override-static.c test non-default heap 2022-12-23 13:04:53 -08:00
main-override.c introduces netbsd's reallocarr overriding. 2021-12-01 22:43:13 +00:00
main-override.cpp fix compilation of heap specific STL allocators for vs2017 2023-02-07 11:07:52 -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-fill.c Fix whitespace 2022-12-03 00:24:20 +01:00
test-api.c Fix whitespace 2022-12-03 00:24:20 +01:00
test-stress.c Fix whitespace 2022-12-03 00:24:20 +01:00
test-wrong.c Fix whitespace 2022-12-03 00:24:20 +01: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.