This exact thing was implement earlier this year in <https://reviews.llvm.org/D30101>.
Kuba > On Nov 3, 2017, at 9:38 AM, Christian Holler <[email protected]> wrote: > > Hi, > > > I think it could be valuable to have a "free_fill_byte" option, similar > to the existing "malloc_fill_byte" option. This option would fill any > free'd memory with the specified byte pattern. This could help us > identify accesses to this memory that come from uninstrumented code (in > our case JIT code or third-party libraries that have not been built with > ASan). > > Of course this comes with a performance penalty so it should be off by > default. But we would gladly turn this on in some of our automated > testing for Firefox to find additional issues. > > Would it be possible to implement this? > > > Thanks, > > Christian Holler (:decoder) > Staff Security Engineer > Fuzzing Team > Mozilla Corporation > > -- > 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. -- 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.
