Should ASAN build use `-shared-libsan`?

[lucascolley]

@isuruf do I understand you correctly at scipy/scipy#24066 (comment) that you are suggesting the following diff for CPython?

diff --git a/configure.ac b/configure.ac
index 3a9841b1e7d..7b44be75623 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3520,7 +3520,7 @@ AC_ARG_WITH([address_sanitizer],
 [
 AC_MSG_RESULT([$withval])
 BASECFLAGS="-fsanitize=address -fno-omit-frame-pointer $BASECFLAGS"
-LDFLAGS="-fsanitize=address $LDFLAGS"
+LDFLAGS="-fsanitize=address -shared-libsan $LDFLAGS"
 # ASan works by controlling memory allocation, our own malloc interferes.
 with_pymalloc="no"
 ],

Also, is this only necessary on linux?

[StanFromIreland]

This would break compiling with GCC, as it doesn’t support such a link option (see the documentation). And is this purely for downstream ASan testing of third-party extension modules?

[lucascolley]

This would break compiling with GCC, as it doesn’t support such a link option (see the documentation).

Can we add it conditionally if the compiler is clang?

And is this purely for downstream ASan testing of third-party extension modules?

That is the current use-case I am working on.