From 52204f78f94d7512df1f0f3bea1d47437a2c3a58 Mon Sep 17 00:00:00 2001 From: Andy Getzendanner Date: Wed, 26 Mar 2025 12:19:38 -0700 Subject: [PATCH] Remove obsolete references to LinuxThreads. PiperOrigin-RevId: 740860675 Change-Id: I73bf9fd36e6135eb7577da54254254df7eebdf7b --- docs/faq.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index c7d10b50..4e958384 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -511,19 +511,6 @@ However, there are cases where you have to define your own: list of the constructor. (Early versions of `gcc` doesn't force you to initialize the const member. It's a bug that has been fixed in `gcc 4`.) -## Why does ASSERT_DEATH complain about previous threads that were already joined? - -With the Linux pthread library, there is no turning back once you cross the line -from a single thread to multiple threads. The first time you create a thread, a -manager thread is created in addition, so you get 3, not 2, threads. Later when -the thread you create joins the main thread, the thread count decrements by 1, -but the manager thread will never be killed, so you still have 2 threads, which -means you cannot safely run a death test. - -The new NPTL thread library doesn't suffer from this problem, as it doesn't -create a manager thread. However, if you don't control which machine your test -runs on, you shouldn't depend on this. - ## Why does GoogleTest require the entire test suite, instead of individual tests, to be named `*DeathTest` when it uses `ASSERT_DEATH`? GoogleTest does not interleave tests from different test suites. That is, it