googletest

UnitTestImpl::GetTestSuite(int i) computes the shuffled position from test_suite_indices_, but incorrectly indexes test_suites_ with the original i. In googletest/src/gtest-internal-inl.h, change:

return test_suites_[i];

to:

return test_suites_[index];

The mutable accessor already uses index correctly. Rebuild GoogleTest and relink your test binary after applying the patch. This bug existed since commit bd851333 and was observed on main at commit 08da6214.

This happens on platforms where plain char is signed. In JsonUnitTestResultPrinter::EscapeJson, UTF-8 bytes from 0x80 through 0xFF become negative, so the check ch < ' ' treats them as JSON control characters and escapes each byte separately.

Fix it by interpreting the byte as unsigned before the control-character check:

const unsigned char ch = static_cast<unsigned char>(str[i]);

if (ch < ' ') {
  // Emit the needed \u00XX escape only for real ASCII control characters.
}

Bytes with the high bit set should be left untouched so valid UTF-8 sequences are written as UTF-8. Continue escaping JSON-required characters such as " and \. Then rebuild libgtest and libgtest_main, or upgrade to a GoogleTest release containing the fix for issue #5081.

As a temporary workaround, avoid non-ASCII characters in RecordProperty, test names, file paths, and failure messages, or post-process the JSON to reconstruct the incorrectly split UTF-8 sequences.

The error means GoogleTest is being built with the static debug C runtime (/MTd), while your executable uses the dynamic debug C runtime (/MDd).

Upgrade GoogleTest to a main commit containing the fix for issue #5042. The fix only overrides CRT settings when GoogleTest is the top-level project, so FetchContent and add_subdirectory() consumers inherit the parent project's CRT setting.

If you cannot update immediately, force GoogleTest to use the shared CRT before declaring it:

set(gtest_force_shared_crt ON CACHE BOOL "Use shared CRT for GoogleTest" FORCE)

include(FetchContent)
FetchContent_Declare(
  googletest
  GIT_REPOSITORY https://github.com/google/googletest
  GIT_TAG        main
)
FetchContent_MakeAvailable(googletest)

Then delete the build directory and reconfigure:

Remove-Item -Recurse -Force build
cmake -S . -B build
cmake --build build

Alternatively, to consistently use the static CRT everywhere, set this before creating your targets and adding GoogleTest:

set(CMAKE_MSVC_RUNTIME_LIBRARY "MultiThreaded$<$<CONFIG:Debug>:Debug>")

The error occurs when a MinGW or Cygwin regex.h header leaks into the Linux include path. It macro-remaps POSIX functions such as regcomp, regexec, and regfree to Windows-style names like regcompA, which do not exist in glibc. CMake and GCC versions are not the cause.

1. Check for leaked include paths:

echo "$CPATH $C_INCLUDE_PATH $CPLUS_INCLUDE_PATH $CMAKE_INCLUDE_PATH"
echo | g++ -x c++ -E -Wp,-v -

Look for MinGW, Cygwin, w64-mingw32, or cross-compiler include directories.

2. Remove them from the environment and rebuild from scratch:

unset CPATH C_INCLUDE_PATH CPLUS_INCLUDE_PATH CMAKE_INCLUDE_PATH
rm -rf build
cmake -S . -B build
cmake --build build

If the bad include path cannot be removed immediately, force GoogleTest to use its simple regex implementation instead of POSIX regex:

rm -rf build
cmake -S . -B build -DCMAKE_CXX_FLAGS='-DGTEST_HAS_POSIX_RE=0'
cmake --build build

For a permanent fix, update GoogleTest to a newer release or commit containing the issue #5001 fix, which detects macro-redefined POSIX regex symbols and automatically falls back to SIMPLE_RE.

GoogleTest 1.15.x requires C++17, so build it with C++17 instead of C++14:

CXXFLAGS="-Werror -Wall -Wextra -Wpedantic" cmake -S . -B /tmp/gtestbuildfolder -DCMAKE_CXX_STANDARD=17 -DCMAKE_CXX_STANDARD_REQUIRED=ON
cmake --build /tmp/gtestbuildfolder

The warning occurs because Apple Clang exposes [[maybe_unused]] in C++14 as a compiler extension, even though the attribute was introduced in C++17.

If you must compile an older GoogleTest version in C++14, patch the GTEST_INTERNAL_HAVE_CPP_ATTRIBUTE macro so it also checks __cplusplus:

#if defined(__has_cpp_attribute)
#define GTEST_INTERNAL_HAVE_CPP_ATTRIBUTE(x) (__cplusplus >= __has_cpp_attribute(x))
#else
#define GTEST_INTERNAL_HAVE_CPP_ATTRIBUTE(x) 0
#endif

The preferred fix is to use C++17 or upgrade GoogleTest.