diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2020-07-02 16:52:13 +0300 |
|---|---|---|
| committer | Monty <monty@mariadb.org> | 2020-07-02 17:59:28 +0300 |
| commit | b6ec1e8bbf0ffca2d715aded694722e0c4b5d484 (patch) | |
| tree | 50a26d45267de2570fe0761f1776aa1397252c93 /vio/viossl.c | |
| parent | 65f831d17c84900c1faea49164688e2f5ce59563 (diff) | |
| download | mariadb-git-b6ec1e8bbf0ffca2d715aded694722e0c4b5d484.tar.gz | |
MDEV-20377 post-fix: Introduce MEM_MAKE_ADDRESSABLE
In AddressSanitizer, we only want memory poisoning to happen
in connection with custom memory allocation or freeing.
The primary use of MEM_UNDEFINED is for declaring memory uninitialized
in Valgrind or MemorySanitizer. We do not want MEM_UNDEFINED to
have the unwanted side effect that AddressSanitizer would no longer
be able to complain about accessing unallocated memory.
MEM_UNDEFINED(): Define as no-op for AddressSanitizer.
MEM_MAKE_ADDRESSABLE(): Define as MEM_UNDEFINED() or
ASAN_UNPOISON_MEMORY_REGION().
MEM_CHECK_ADDRESSABLE(): Wrap also __asan_region_is_poisoned().
Diffstat (limited to 'vio/viossl.c')
0 files changed, 0 insertions, 0 deletions