From 4426ddda1cf1aaa18729cd857cbf1bb82845b90a Mon Sep 17 00:00:00 2001 From: Pawel Dac Date: Wed, 13 Jan 2021 22:21:31 +0100 Subject: Help: Clarify memory check sanitizer option behavior for `log_path` Added information about prepending [ASAN/LSAN/TSAN/MSAN/UBSAN]_OPTIONS to MemoryTesterEnvironmentVariable and `log_path` limitation. --- Help/variable/CTEST_MEMORYCHECK_SANITIZER_OPTIONS.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Help/variable/CTEST_MEMORYCHECK_SANITIZER_OPTIONS.rst b/Help/variable/CTEST_MEMORYCHECK_SANITIZER_OPTIONS.rst index 6cd51fa..b6fee2e 100644 --- a/Help/variable/CTEST_MEMORYCHECK_SANITIZER_OPTIONS.rst +++ b/Help/variable/CTEST_MEMORYCHECK_SANITIZER_OPTIONS.rst @@ -5,3 +5,8 @@ CTEST_MEMORYCHECK_SANITIZER_OPTIONS Specify the CTest ``MemoryCheckSanitizerOptions`` setting in a :manual:`ctest(1)` dashboard client script. + +CTest prepends correct sanitizer options ``*_OPTIONS`` +environment variable to executed command. CTests adds +its own ``log_path`` to sanitizer options, don't provide your +own ``log_path``. -- cgit v0.12