supp. coro releated asan errors

Signed-off-by: Pratik Mankawde <3397372+pratikmankawde@users.noreply.github.com>
This commit is contained in:
Pratik Mankawde
2026-02-13 16:53:08 +00:00
parent 358c6d95bf
commit ea2ab17b95
2 changed files with 3 additions and 10 deletions

View File

@@ -101,6 +101,7 @@ words:
- fcontext
- finalizers
- firewalled
- flackiness
- fmtdur
- fsanitize
- funclets

View File

@@ -9,17 +9,9 @@
# - stack-buffer-overflow errors in seemingly unrelated code (e.g., std::chrono::steady_clock::now())
# - stack-buffer-underflow errors in seemingly unrelated code (e.g., xxhasher::retrieveHash(), clock_gettime)
#
# These are suppressed via:
# 1. Runtime option: detect_stack_use_after_return=0 (in ASAN_OPTIONS in CI workflow)
# 2. Compile-time flag: -fno-sanitize-address-use-after-scope (in cmake/XrplSanitizers.cmake)
#
# Note: stack-buffer-overflow false positives from coroutines cannot be fully suppressed
# without disabling ASAN entirely for Boost. Clang builds use -fsanitize-blacklist to
# exclude Boost headers, but GCC does not support this feature.
#
# See: https://github.com/google/sanitizers/issues/189
# These are now handled by using coroutine2 and ucontext backend.
# Boost - false positives from stackful coroutines
interceptor_name:clock_gettime
interceptor_name:__bzero
interceptor_name:nudb
interceptor_name:coro # Suppress any flackiness