summaryrefslogtreecommitdiff
path: root/tests/malloc_test.cpp
diff options
context:
space:
mode:
authorMitch Phillips <mitchp@google.com>2020-02-11 15:23:47 -0800
committerMitch Phillips <mitchp@google.com>2020-02-11 15:29:21 -0800
commit3083cc94795e43ba7ec04e6b24ed8d9a1f68b88c (patch)
tree31022bbaa5eae87d09a63d5e014232fad553c131 /tests/malloc_test.cpp
parentd129786e122f4a7136fe4b8b1b3fdc5525897532 (diff)
[malloc dispatch] Install dispatch over the top of GWP-ASan.
When enabled, GWP-ASan sets the current dispatch table. Then, when a shim layer (malloc_debug, malloc_hooks, heapprofd) comes along, they should (by design) overwrite the current dispatch table. Currently, these shim layers check to see whether malloc_limit is installed by checking the current dispatch table against nullptr. Because GWP-ASan owns the current dispatch table, the shim thinks that malloc_limit is installed and falls back to only use the default dispatch, thinking that malloc_limit will call them. This is not the case, and they should take over the current dispatch pointer. Bug: 135634846 Test: atest bionic Change-Id: Ifb6f8864a15af9ac7f20d9364c40f73c5dd9d870
Diffstat (limited to 'tests/malloc_test.cpp')
0 files changed, 0 insertions, 0 deletions