search for: __asan_poison_memory_region

On Mon, Nov 9, 2015 at 7:20 PM, Kostya Serebryany <kcc at google.com> wrote: > Most likely, you need > https://github.com/google/sanitizers/wiki/AddressSanitizerLeakSanitizer Thanks! > I don't think lsan supports this mode directly, > but why do you think that the init-time allocations are going to be > "leaked"? > If there is some object still pointing to

...tests/asan_asm_test.cc compiler-rt/test/asan/TestCases/Linux/asan-asm-stacktrace-test.cc - Prelinking not supported: compiler-rt/test/asan/TestCases/Linux/asan_prelink_test.cc - Intra-object padding not supported: compiler-rt/test/asan/TestCases/intra-object-overflow.cc - Calls __asan_poison_memory_region in middle of shadow byte: compiler-rt/lib/asan/tests/asan_interface_test.cc SimplePoisonMemoryRegionTest OverlappingPoisonMemoryRegionTest PoisoningStressTest compiler-rt/test/asan/TestCases/small_memcpy_test.cc compiler-rt/test/asan/TestCases/strtol_strict.c compi...

...ors: it seems sensible not to insert 32-byte sentinels between every object, but the result is that some stack overflow gets reported as unknown or use-after-scope. I have a patch that improves on the default behavior, but there remains cases where the error reports will not be as good. - __asan_poison_memory_region is now more limited. A typical case that doesn't work is the poisoning of 8-byte or 16-byte that maps to the middle of a shadow byte. For testing, I have a few questions: - Would it make sense to provide an internal compiler flag to set the shadow granularity, so that there we can at l...

...I have a patch that > improves on the default behavior, but there remains cases where the > error reports will not be as good. > Hmm. Not sure what's the problem here. It's totally fine to insert 32-byte redzone around stack objects. (in 32-byte granularity mode) > > - __asan_poison_memory_region is now more limited. A typical case > that doesn't work is the poisoning of 8-byte or 16-byte that maps to > the middle of a shadow byte. > yep. > > For testing, I have a few questions: > > - Would it make sense to provide an internal compiler flag to set the >...