Fixed some check-lsan tests
Linux/cleanup_in_tsd_destructor.c Linux/fork.cpp Linux/fork_threaded.cpp Linux/use_tls_static.cpp many_tls_keys_thread.cpp
Usage:
- asan calls ClearShadowForThreadStackAndTLS to mark the TLS block addressable: notify lsan (when used together) about the TLS ranges
- lsan calls ScanRangeForPointers on the TLS block to find reachable chunks.
- msan and tsan's __tls_get_addr interceptors unpoison/reset dtv ranges to avoid false positives (https://github.com/google/sanitizers/issues/547), e.g. test/msan/dtls_test.c
- AdjustStackSize shared by lsan/msan/tsan: ensure the thread stack size is sufficiently large. Not sure this is needed by musl.
would it be better to put these mechanics in musl? (then have it provide an API to grab the [d]tls bounds ?)