search for: quarantine_size_mb

...10007fff7fff]` || HighShadow || || `[0x00008fff7000, 0x02008fff6fff]` || ShadowGap || || `[0x00007fff8000, 0x00008fff6fff]` || LowShadow || || `[0x000000000000, 0x00007fff7fff]` || LowMem || MemToShadow(shadow): 0x00008fff7000 0x000091ff6dff 0x004091ff6e00 0x02008fff6fff redzone=16 max_redzone=2048 quarantine_size_mb=256M thread_local_quarantine_size_kb=1024K malloc_context_size=30 SHADOW_SCALE: 3 SHADOW_GRANULARITY: 8 SHADOW_OFFSET: 0x7fff8000 ==3401806==Installed the sigaction for signal 11 ==3401806==Installed the sigaction for signal 7 ==3401806==Installed the sigaction for signal 8 ==3401806==T0: stack [0x...

...w verify that this heap-use-after-free is happening? > E.g. print all the pointer values coming from memory::allocate, coming into > memory::deallocate, and coming into sat::clause::operator[] > > If curious, check what size of quarantine is required to catch this bug > (ASAN_OPTIONS=quarantine_size_mb=N, default=256) > Valgrind may have smaller default quarantine and thus misses this bug. I was lazy and just told valgrind to execute the program (built by gcc without ASan) with the largest quarantine it supported. ``` LD_LIBRARY_PATH=`pwd` valgrind --freelist-vol=10000000000 ./c_example ```...

...x02008fff6fff]` || ShadowGap || >> || `[0x00007fff8000, 0x00008fff6fff]` || LowShadow || >> || `[0x000000000000, 0x00007fff7fff]` || LowMem || >> MemToShadow(shadow): 0x00008fff7000 0x000091ff6dff 0x004091ff6e00 0x02008fff6fff >> redzone=16 >> max_redzone=2048 >> quarantine_size_mb=256M >> thread_local_quarantine_size_kb=1024K >> malloc_context_size=30 >> SHADOW_SCALE: 3 >> SHADOW_GRANULARITY: 8 >> SHADOW_OFFSET: 0x7fff8000 >> ==3401806==Installed the sigaction for signal 11 >> ==3401806==Installed the sigaction for signal 7 >>...

Hi, # TL;DR I've been building an application with and without the address sanitizer (with gcc 5.3 and clang 3.7.1) and I've observed that the application's behaviour changes (assertion hit/ not hit). I'm wondering if this could be a bug in address sanitizer or if the application I'm running is just buggy (e.g. doing bad things like relying on memory layout, etc.). I'm

...t; > E.g. print all the pointer values coming from memory::allocate, coming >> > into >> > memory::deallocate, and coming into sat::clause::operator[] >> > >> > If curious, check what size of quarantine is required to catch this bug >> > (ASAN_OPTIONS=quarantine_size_mb=N, default=256) >> > Valgrind may have smaller default quarantine and thus misses this bug. >> >> I was lazy and just told valgrind to execute the program (built by gcc >> without ASan) with the largest quarantine it supported. > > > There are some differences be...