sanitizer-coverage vs asan_blacklist

[Timur Iskhodzhanov]

... especially since the blacklist option is called -fsanitize-blacklist.
Just looking at its name, I'd had assumed it affected -fsanitize-coverage
too.

пт, 10 апр. 2015 г. в 21:08, Timur Iskhodzhanov <timurrrr at google.com>:

> Kostya, Alexey,
>
> I'm currently working on sanitizer coverage on Windows for Chromium.
> As described in http://crbug.com/459166 , we currently blacklist some
> sandbox code from ASan instrumentation, otherwise shadow memory is accessed
> before the RTL is even loaded.
> As it turns out, we should also disable coverage instrumentation for that
> code, otherwise the guard variables are checked before the RTL is loaded.
>
> That being said, the ASan blacklist should probably be used in the
> coverage instrumentation module pass.  Or it should have a separate
> blacklist...
>
> What do you think?
> ––
> Timur
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150410/d56f3470/attachment.html>