Do as we do for MALLOC_PERTURB and set a sensible value for both ASAN_OPTIONS and UBSAN_OPTIONS to abort on failure and give more helpful output at the same time. We do not set these options if the user has exported a value themselves to allow override. In the last week alone, I've observed two cases where people were expecting sanitizers to abort on failure and were surprised when it didn't: 1)pull/12403/head252d693797
2)c47df433f7
Correct this - which is in-line with meson's DWIM/DTRT philosophy. Signed-off-by: Sam James <sam@gentoo.org>
parent
e2a87afa52
commit
7b7d2e060b
4 changed files with 24 additions and 0 deletions
@ -0,0 +1,5 @@ |
||||
## Tests now abort on errors by default under sanitizers |
||||
|
||||
Sanitizers like AddressSanitizer and UndefinedBehaviorSanitizer do not abort |
||||
by default on detected violations. Meson now exports `ASAN_OPTIONS` and `UBSAN_OPTIONS` |
||||
when unset in the environment to provide sensible abort-by-default behavior. |
Loading…
Reference in new issue