On Wed, Jul 16, 2014 at 9:36 PM, Yuri Gribov <[email protected]> wrote: > On Wed, Jul 16, 2014 at 7:59 PM, 'Dmitry Vyukov' via address-sanitizer > <[email protected]> wrote: >> 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. > > My colleagues from kernel team pointed out that forced poisoning of > stack frames could serve as a poor man's UAR detector (especially if > frames could be interspersed with randomly sized poisoned areas).
This is somewhat harder to do in user-space, because we don't necessary know when a stack is mapped, when it's unmapped and what's its size (on linux, windows and mac). -- 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.
