{CodeRoyale}
All challenges
Multiple ChoiceHard 45s

Static initialization order fiasco

The 'static initialization order fiasco' refers to:
Options
  1. 1Static members racing against each other at runtime when multiple threads touch them.
  2. 2The linker placing static objects into the wrong segment so their addresses are scrambled.
  3. 3Non-local static objects in different TUs initializing in unspecified order, so one may use another before it is constructed.
  4. 4Destructor order being guaranteed to match constructor order for non-local static objects.
cppstatic-initodrinitialization

Think you can answer under pressure?

Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.

Play this in a 3-minute battle