On Wed, Jul 16, 2014 at 7:50 PM, Konstantin Serebryany <[email protected]> wrote: > > > > On Wed, Jul 16, 2014 at 7:42 PM, Tomek Bury <[email protected]> wrote: >> >> Hi all, >> >> The default mode for asan is to start clean and temporarily poison some >> areas. Wouldn't the opposite be more robust? I mean, start with entire >> memory poisoned and temporarily un-poison small bits of memory for their >> life time. > > > There are pieces of memory that come from outside of asan's control (e.g. > memory mmaped via a pure mmap syscall) -- they have to be clean. > If we can be sure that we control all allocated memory -- then yes, there is > such option.
Also I am not sure what it will give us. For malloc it already works in the best possible way. For other memory it will only verify asan's guessing of what memory is OK to access. This can become a constant pain point w/o any benefits. -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
