[ASAN] sanitizing static initialization order fiasco

Clang Frontend
1

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.

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

Best
Piotr Padlewski

2

Hi,
so I've heard that ASAN supports sanitizing static initialization order
fiasco:

AddressSanitizer — Clang 18.0.0git documentation

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:

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.

3

Thanks Kostya :slight_smile: