search for: ubsan_options

Hello, I have several low priority UBSan questions... (1) Is there a way for UBSan to print its output to a file that the user specified (e.g. via option) instead of dumping everything on stderr? (2) Out of curiosity, why is the name of the option for printing the stacktrace spelled "UBSAN_OPTIONS=print_stacktrace=1", though the allowed value is 1? Since the only one value is accepted, maybe it's more practical (and intuitive) to spell it "UBSAN_OPTIONS=print_stacktrace" (4) Do you know if there is better (i.e. more complete) documentation for UBSan somewhere? This one...

...ve 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 then these flags are o...

...t; > > 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 &gt...

Hi Alex Thanks for your email. But it seems not work. I removed the -fsanitize=address flag. The global buffer overflow message doesn't show. However, no *.sancov file is created after I run perlbench. Thus, I could not get the BB coverage. Do you have any ideas? Many Thanks Regards Muhui Alexander Potapenko <glider at google.com> 于2018年9月5日周三 下午7:14写道： > Hi Muhui, > > If

...s on AddressSanitizer mode, making it impossible to mark it as XFAIL. Before making XFAIL more powerful, I'd rather find the problem and try to solve it. The file checks for two copies of missing_return.cpp, one for f() and one for main(), but on ARM's stack trace, there's only one: $ UBSAN_OPTIONS=print_stacktrace=1 ./missing_return.cpp.tmp .../compiler-rt/test/ubsan/TestCases/Misc/missing_return.cpp:6:5: runtime error: execution reached the end of a value-returning function without returning a value #0 0x1c7cf in f() .../compiler-rt/test/ubsan/TestCases/Misc/missing_return.cpp:6:9...

Is there a way to get the undefined-behavior sanitizer to include stack traces in their error messages? Also, I'm sometimes seeing raw addresses where I'd expect to see file names and line numbers. Do I need to point this sanitizer to llvm-symbolizer? And if so, how? Thanks, Greg

Hi, I have just tagged 3.7.1-rc1, so it is ready for testing. As a reminder, when doing regression testing, use the 3.7.0 release as your baseline. Thanks, Tom