lmi-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi-commits] [lmi] master 2ca30a6e 09/13: Specify $ASAN_OPTIONS in anti


From: Greg Chicares
Subject: [lmi-commits] [lmi] master 2ca30a6e 09/13: Specify $ASAN_OPTIONS in anticipation of using ASan
Date: Fri, 10 Jun 2022 21:09:39 -0400 (EDT)

branch: master
commit 2ca30a6ef089fabbbd45119208db47f2493a2ff9
Author: Gregory W. Chicares <gchicares@sbcglobal.net>
Commit: Gregory W. Chicares <gchicares@sbcglobal.net>

    Specify $ASAN_OPTIONS in anticipation of using ASan
---
 nychthemeral_test.sh | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/nychthemeral_test.sh b/nychthemeral_test.sh
index ae8f073e..f17f609d 100755
--- a/nychthemeral_test.sh
+++ b/nychthemeral_test.sh
@@ -370,6 +370,16 @@ then
 
   export UBSAN_OPTIONS=print_stacktrace=1
 
+  # Specify 'detect_invalid_pointer_pairs' even though that feature
+  # isn't necessarily usable with gcc (see:
+  #   https://lists.nongnu.org/archive/html/lmi/2022-06/msg00033.html
+  # ) to support potential future experimentation. This has no effect
+  # unless an applicable '-fsanitize=' option is specified at build
+  # time; it's too confusing to have to change both a gcc option and
+  # an environment variable. Set its value to one because a value of
+  # two is known to give false positives.
+  export 
ASAN_OPTIONS=detect_leaks=0:detect_invalid_pointer_pairs=1:strict_string_checks=1:detect_stack_use_after_return=1:check_initialization_order=1:strict_init_order=1
+
   make "$coefficiency" build_type=ubsan 2>&1 \
     | tee "$log_dir"/default_targets_ubsan | sed -e "$build_clutter" -e 
"$concinnity_clutter" -e "$install_clutter"
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]