SERVER-48597 Fix stack trace unit tests with TSAN

Stack trace unit tests were failing with TSAN due to the mechanisms and
assumptions of the tests. In one case, we simulate a real failure and do
some thread necromancy to recover from it, which was causing TSAN to
segfault immediately. In another two, we rely on a feature that makes
some assumptions about which threads are running and what signals they
can receive, which TSAN's internal threads violate. These tests and
features are disabled with TSAN for now so we can run further tests with
TSAN.

Separately, one of the tests was failing with a complaint from TSAN that
errno was being stomped on. That is also addressed.

1 files changed, 7 insertions, 2 deletions

diff --git a/src/mongo/stdx/sigaltstack_location_test.cpp b/src/mongo/stdx/sigaltstack_location_test.cpp
index f6e37b94cc2..bfc0aba4393 100644
--- a/src/mongo/stdx/sigaltstack_location_test.cpp
+++ b/src/mongo/stdx/sigaltstack_location_test.cpp
@@ -256,8 +256,13 @@ int runTests() {
         int (*func)();
     } static constexpr kTests[] = {
         {"stackLocationTest", &stackLocationTest},
-// These tests violate the memory space deliberately, so they generate false positives from ASAN.
-#if !__has_feature(address_sanitizer)
+// These tests violate the memory space deliberately, so they generate false
+// positives from ASAN. TSAN also fails because we rescue a thread from a
+// SIGSEGV due to intentional thread exhaustion with creative use of a longjmp.
+// TSAN is more clever than we want here and intercepts the SIGSEGV before we
+// can do the thread necromancy that lets us verify it died for the right reasons
+// without killing the test harness.
+#if !__has_feature(address_sanitizer) && !__has_feature(thread_sanitizer)
         {"recursionTest", &recursionTest},
         {"recursionDeathTest", &recursionDeathTest},
 #endif