You can play with these flags to reduce heap overheads:
ASAN_FLAG(
bool, poison_heap, true,
"Poison (or not) the heap memory on [de]allocation. Zero value is
useful "
"for benchmarking the allocator or instrumentator.")
ASAN_FLAG(
int, max_malloc_fill_size, 0x1000, // By default,
This is more or less expected.
As Kuba said, there's no distinction between a check for a heap overflow or
global overflow - we just check that every memory access is valid.
On Thu, Jun 22, 2017 at 9:08 AM, Aayushi Agrawal
wrote:
> Yes I tried but its coming out to be almost same.
>
> Slowdown i
Yes I tried but its coming out to be almost same.
Slowdown is almost 2 times.
On Wed, Jun 21, 2017 at 9:28 PM, Kuba Mracek wrote:
> How big is the slowdown? Did you try using ASan with higher optimization
> levels (-O1, -O2, -O3)?
>
> At the point where ASan instruments memory reads and writes
