mirrors/mimalloc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1ffa48cc61
mimalloc/test
History
daan 461b8aed80 more complete C++ support for compliance and performance
2019-07-14 19:56:33 -07:00
..
CMakeLists.txt fix cmake issues with OBJECT install 2019-07-09 11:32:24 -07:00
main-override.c add check to see if we truly override the system malloc 2019-06-27 13:34:50 -07:00
main-override.cpp more complete C++ support for compliance and performance 2019-07-14 19:56:33 -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 fix path max in realpath on unix (pr #69) 2019-07-08 17:43:10 -07:00
test-stress.c fix cache eviction of smaller segments 2019-07-14 12:52:58 -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.