Issue #20274 has been updated by nobu (Nobuyoshi Nakada). At first, ASAN is not related to Ruby VM, neither the constant nor method under `RubyVM` do not make sense. How are you going to detect it? Maybe from CFLAGS? ---------------------------------------- Feature #20274: Add RubyVM::ASAN.enabled? https://bugs.ruby-lang.org/issues/20274#change-106840 * Author: kjtsanaktsidis (KJ Tsanaktsidis) * Status: Open * Priority: Normal ---------------------------------------- Some parts of the Ruby test suite won't work correctly under ASAN. In particular, `assert_no_memory_leak` will need different parameters for ASAN (or be skipped, in the same way as for MJIT/RJIT). I propose that we add a module `RubyVM::ASAN` (which will be unconditionally defined), and `RubyVM::ASAN.enabled?` (which will return true if Ruby was compiled with ASAN, or false otherwise). This means we can check if ASAN is enabled by running `defined?(RubyVM::ASAN) && RubyVM::ASAN.enabled?`, in the same way that the mjit/rjit check is performed. -- https://bugs.ruby-lang.org/