blocks|key|1676843|text|也许可以使用valgrind来查找未初始化内存的使用情况。对于“静态初始化顺序失败”最好的解决方案是使用一个静态函数，它返回对象的一个实例，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1676844|class+A+{
public:
++++static+X+&getStatic()+{+static+X+my_static;+return+my_static;+}
};|code-block|syntax|javascript|1676845|这种访问静态对象的方式是通过调用getStatic，这将确保它在第一次使用时被初始化。|1676846|如果你需要担心反初始化的顺序，可以返回一个新的对象，而不是一个静态分配的对象。|1676847|编辑:删除了冗余的静态对象，我不知道为什么，但在我的原始示例中，我混合并匹配了两个具有静态对象的方法。|1676848|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

perhaps use valgrind to find usage of uninitialized memory. The nicest solution to the "static initialization order fiasco" is to use a static function which returns an instance of the object like this:

<pre><code>class A {
public:
 static X &amp;getStatic() { static X my_static; return my_static; }
};
</code></pre>

This way you access your static object is by calling getStatic, this will guarantee it is initialized on first use. 

If you need to worry about order of de-initialization, return a new'd object instead of a statically allocated object. 

EDIT: removed the redundant static object, i dunno why but i mixed and matched two methods of having a static together in my original example.

blocks|key|1676902|text|将所有全局对象替换为全局函数，这些函数返回对在函数中声明的静态对象的引用。这不是线程安全的，所以如果你的应用是多线程的，你可能需要一些技巧，比如pthread_once或全局锁。这将确保所有内容在使用之前都已初始化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1676903|现在，要么你的程序能工作(太棒了！)否则它会陷入无限循环，因为你有一个循环依赖(需要重新设计)，或者你会转移到下一个bug。|1676904|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Replace all the global objects with global functions that return a reference to an object declared static in the function. This isn't thread-safe, so if your app is multi-threaded you might need some tricks like pthread_once or a global lock. This will ensure that everything is initialized before it is used.

Now, either your program works (hurrah!) or else it sits in an infinite loop because you have a circular dependency (redesign needed), or else you move on to the next bug.

blocks|key|1461828|text|您需要做的第一件事是列出所有具有非平凡构造函数的静态对象。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1461829|考虑到这一点，您要么需要一次插入一个，要么简单地将它们全部替换为单一模式对象。|1461830|单例模式受到了很多批评，但懒惰的“按需”构造是一种相当简单的方法，可以解决现在和未来的大多数问题。|1461831|老..。|1461832|MyObject+myObject|code-block|syntax|javascript|1461833|新的..。|1461834|MyObject+&myObject()
{
++static+MyObject+myActualObject;
++return+myActualObject;
}|1461835|当然，如果您的应用程序是多线程的，这可能会给您带来比最初更多的问题…|1461836|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

The first thing you need to do is make a list of all static objects that have non-trivial constructors.

Given that, you either need to plug through them one at a time, or simply replace them all with singleton-pattern objects.

The singleton pattern comes in for a lot of criticism, but the lazy "as-required" construction is a fairly easy way to fix the majority of the problems now and in the future.

old...

<pre><code>MyObject myObject
</code></pre>

new...

<pre><code>MyObject &amp;myObject()
{
 static MyObject myActualObject;
 return myActualObject;
}
</code></pre>

Of course, if your application is multi-threaded, this can cause you more problems than you had in the first place...

blocks|key|1677011|text|Www.gimpel.com声称他们的PC-Lint/FlexeLint静态分析工具将检测到这样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1677012|我对他们的工具有很好的经验，但不是在这个特定的问题上，所以我不能保证他们会有多大的帮助。|1677013|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Gimpel Software (www.gimpel.com) claims that their PC-Lint/FlexeLint static analysis tools will detect such problems.

I have had good experience with their tools, but not with this specific issue so I can't vouch for how much they would help.

blocks|key|1461984|text|有一些代码本质上是“初始化”由编译器生成的C%2B%2B。找到这段代码/调用堆栈的一种简单方法是创建一个静态对象，该对象在调试器中的构造函数中取消引用NULL+-+break并探索一下。MSVC编译器设置一个函数指针表，该表被迭代以进行静态初始化。您应该能够访问此表，并确定程序中发生的所有静态初始化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1461985|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There is code that essentially "initializes" C++ that is generated by the compiler. An easy way to find this code / the call stack at the time is to create a static object with something that dereferences NULL in the constructor - break in the debugger and explore a bit. The MSVC compiler sets up a table of function pointers that is iterated over for static initialization. You should be able to access this table and determine all static initialization taking place in your program.

blocks|key|1462056|text|其他答案是正确的，我只想补充说，对象的getter应该在.cpp文件中实现，并且它不应该是静态的。如果你在一个头文件中实现它，这个对象将会在你调用它的每个库/框架中被创建...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1462057|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Other answers are correct, I just wanted to add that the object's getter should be implemented in a .cpp file and it should not be static. If you implement it in a header file, the object will be created in each library / framework you call it from....

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?
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.

Finding C++ static initialization order problems

5位重磅专家聚焦 AI 时代开发者核心成长需求，带你深入解锁全栈进化、人机协作关键路径！点击报名到场：<a href="https://cloud.tencent.com/developer/salon/salon-2403/signup" target="_blank">https://cloud.tencent.com/developer/salon/salon-2403/signup</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/487c82639d2338df3ef66dfb1450601a.png"/>

腾讯技术创作特训营「年度论坛」正在报名中！

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们遇到了一些的问题，我正在寻找一种方法来梳理大量代码，以找到可能出现的情况。关于如何有效地完成这项工作，有什么建议吗？编辑:关于如何解决静态初始化顺序问题，我得到了一些很好的答案，但这不是我的问题。我想知道如何查找存在此问题的对象。在这方面，Evan的答案似乎是到目前为止最好的；我不认为我们可以使用valgrind，...

问查找C++静态初始化顺序问题
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问查找C++静态初始化顺序问题EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问查找C++静态初始化顺序问题
EN