diff options
| author | Sergei Golubchik <serg@mariadb.org> | 2018-01-20 17:59:11 +0100 |
|---|---|---|
| committer | Sergei Golubchik <serg@mariadb.org> | 2018-01-22 11:39:54 +0100 |
| commit | 22ae3843db6c8b2a84ca5d16cd99025abb52cc27 (patch) | |
| tree | 78cd7d2f09ac106939cdfdb81e5677ceb9135e22 /include/my_valgrind.h | |
| parent | 204cb85aab3e6326e9f7a51c478efd6fad44801a (diff) | |
| download | mariadb-git-22ae3843db6c8b2a84ca5d16cd99025abb52cc27.tar.gz | |
Correct TRASH() macro usage
TRASH was mapped to TRASH_FREE and was supposed to be used for memory
that should not be accessed anymore, while TRASH_ALLOC() is to be
used for uninitialized but to-be-used memory.
But sometimes TRASH() was used in the latter sense.
Remove TRASH() macro, always use explicit TRASH_ALLOC() or TRASH_FREE().
Diffstat (limited to 'include/my_valgrind.h')
| -rw-r--r-- | include/my_valgrind.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/include/my_valgrind.h b/include/my_valgrind.h index a9dba1cb06c..6fcc4dfa54a 100644 --- a/include/my_valgrind.h +++ b/include/my_valgrind.h @@ -45,4 +45,3 @@ #endif #define TRASH_ALLOC(A,B) TRASH_FILL(A,B,0xA5) #define TRASH_FREE(A,B) TRASH_FILL(A,B,0x8F) -#define TRASH(A,B) TRASH_FREE(A,B) |