search for: lsan_opt

...fine until we have a single sanitizer - e.g. for TSan or MSan. The situation gets crazy when we combine multiple sanitizers in a single process, for instance use ASan+LSan+UBSan (the default use case in some setups). Each tool has its own defaults for common flag values, and each of ASAN_OPTIONS, LSAN_OPTIONS and UBSAN_OPTIONS can define both tool-specific and common flags. These environment variables are parsed at different time, sometimes in undefined order. We can easily end up in situation where ASan initializes some parts of sanitizer_common assuming certain values of common runtime flags, but...

...or MSan. > > > > The situation gets crazy when we combine multiple sanitizers in a single > > process, for instance use ASan+LSan+UBSan (the default use case in some > > setups). Each tool has its own defaults for common flag values, and each > of > > ASAN_OPTIONS, LSAN_OPTIONS and UBSAN_OPTIONS can define both > tool-specific > > and common flags. These environment variables are parsed at different > time, > > sometimes in undefined order. We can easily end up in situation where > ASan > > initializes some parts of sanitizer_common assuming...

Hi, I'm currently trying to find and fix memory leaks (compiling with ``-fsanitize=address``) in the KLEE tool [1] an having found some leaks and I'm having trouble suppressing them. I'm trying to suppress them using the ``-fsanitize-blacklist=blacklist.txt`` option as documented at [2]. I'm using Clang 3.7 ( Arch Linux package 3.7.0-6). The sort of reported leaks I see are ```