[cfe-dev] [ASAN] sanitizing static initialization order fiasco

[Kostya Serebryany via cfe-dev]

On Mon, Nov 9, 2015 at 8:54 AM, Piotr Padlewski via cfe-dev <
cfe-dev at lists.llvm.org> wrote:

> Hi,
> so I've heard that ASAN supports sanitizing static initialization order
> fiasco:
>
> http://clang.llvm.org/docs/AddressSanitizer.html#initialization-order-checking
>
> I assume that it only reports occurrences of fiasco, and not cases when it
> could happen but we were lucky enough that initialization order was right.
>

There is a stricter mode  that will find potential fiasco as well:
https://github.com/google/sanitizers/wiki/AddressSanitizerInitializationOrderFiasco#strict-init-order-checking



> Am I right or not? If so, is there any way to staticly prove that code is
> initialization order fiasco free?
>

I'd guess this can be checked statically but I am not aware of a tool that
does it.


>
> Best
> Piotr Padlewski
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20151109/23f97018/attachment.html>