From d3af011562a63fe0361034a75568cd777d3a4862 Mon Sep 17 00:00:00 2001 From: Andrew Kaster Date: Sun, 23 May 2021 11:40:13 -0600 Subject: [PATCH] CI: Enable more verbose and strict sanitizer options Options shamelessly stolen from this article on systemd's website: https://systemd.io/TESTING_WITH_SANITIZERS/ We make ASAN more strict and tell UBSAN to print more verbose output on failure. One of the more interesting ASAN options, detect_stack_use_after_return, sadly causes both UBSAN and ASAN failures in test-js. --- .github/workflows/cmake.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/workflows/cmake.yml b/.github/workflows/cmake.yml index 9bc0d674f4..bdbb7cdc60 100644 --- a/.github/workflows/cmake.yml +++ b/.github/workflows/cmake.yml @@ -242,7 +242,9 @@ jobs: timeout-minutes: 4 env: CTEST_OUTPUT_ON_FAILURE: 1 - UBSAN_OPTIONS: "halt_on_error=1" + # FIXME: enable detect_stack_use_after_return=1 #7420 + ASAN_OPTIONS: "strict_string_checks=1:check_initialization_order=1:strict_init_order=1" + UBSAN_OPTIONS: "print_stacktrace=1:print_summary=1:halt_on_error=1" if: ${{ matrix.with-fuzzers == 'NO_FUZZ' }} notify_irc: