3party/mimalloc
0
0
Fork 0
mirror of https://github.com/microsoft/mimalloc.git synced 2024-12-26 12:41:10 +08:00
Code Issues Projects Releases Wiki Activity
mimalloc/test
History
daan 2f5fbffaa7 merge from dev
2020-07-22 10:56:59 -07:00
..
CMakeLists.txt
bump version to v1.6.0
2020-02-09 18:53:39 -08:00
main-override-static.c
merge from dev
2020-07-22 10:56:59 -07:00
main-override.c
update test files and overriding
2019-07-23 15:00:13 -07:00
main-override.cpp
merge from dev
2020-05-05 11:00:36 -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
set extra debug padding per-heap
2020-04-20 17:09:28 -07:00
test-stress.c
merge from dev
2020-04-30 20:40:48 -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.