title: Finding C++ static initialization order problems
body: <p>We've run into some problems with the <a href="http://www.parashift.com/c++-faq-lite/static-init-order.html" rel="noreferrer">static initialization order fiasco</a>, and I'm looking for ways to comb through a whole lot of code to find possible occurrences.  Any suggestions on how to do this efficiently?</p>
  <p>Edit: I'm getting some good answers on how to SOLVE the static initialization order problem, but that's not really my question.  I'd like to know how to FIND objects that are subject to this problem.  Evan's answer seems to be the best so far in this regard; I don't think we can use valgrind, but we may have memory analysis tools that could perform a similar function.  That would catch problems only where the initialization order is wrong for a given build, and the order can change with each build.  Perhaps there's a static analysis tool that would catch this.  Our platform is IBM XLC/C++ compiler running on AIX.</p>