blocks|key|4319098|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4319099|“我很惊讶谷歌C%2B%2B测试框架没有明确支持内存泄漏检查。”|blockquote|4319100|4319101|4319102|它不是(也从来没有)这样做的目的。你实际上可以做一些认证，例如使用google+mock和设置预期的调用(例如析构函数)。但使用专门针对这一方面的工具，肯定会比你自己编写的任何东西都要好。|offset|length|4319103|4319104|“使用另一个C%2B%2B单元测试框架更好吗？”|4319105|4319106|4319107|所以为什么要费心去寻找不同的单元测试框架(那也不会支持这样的特性，至少我所知道的没有)。|4319108|您可以使用像这样的工具，并在它们的控制下运行UnitTester可执行文件来检测内存泄漏。|style|CODE|4319109|备注：|BOLD|4319110|上面关于使用UnitTester可执行文件执行此操作的建议，并不能捕获使用您的代码生成的最终可执行文件中所有可能的内存泄漏，而只是帮助查找实际测试的代码的but+/缺陷。|4319111|entityMap|0|LINK|mutability|MUTABLE|url|https://code.google.com/p/googlemock/^0|0|0|0|0|X|B|0|0|0|0|0|0|0|M|A|0|0|3|0|6|A|0^^$0|@$1|2|3|-4|4|5|6|17|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|18|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|19|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|1A|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|1B|7|@]|8|@$H|1C|I|1D|1|1E]]|9|$]]|$1|J|3|-4|4|5|6|1F|7|@]|8|@]|9|$]]|$1|K|3|L|4|C|6|1G|7|@]|8|@]|9|$]]|$1|M|3|-4|4|5|6|1H|7|@]|8|@]|9|$]]|$1|N|3|-4|4|5|6|1I|7|@]|8|@]|9|$]]|$1|O|3|P|4|5|6|1J|7|@]|8|@]|9|$]]|$1|Q|3|R|4|5|6|1K|7|@$H|1L|I|1M|S|T]]|8|@]|9|$]]|$1|U|3|V|4|5|6|1N|7|@$H|1O|I|1P|S|W]]|8|@]|9|$]]|$1|X|3|Y|4|5|6|1Q|7|@$H|1R|I|1S|S|T]]|8|@]|9|$]]|$1|Z|3|-4|4|5|6|1T|7|@]|8|@]|9|$]]]|10|$11|$4|12|13|14|9|$15|16]]]]

<blockquote>
 "I'm surprised that Google C++ Testing Framework does not explicitly support checking for memory leaks."
</blockquote>

It's not (and never was) purposed to do so. 
You can actually do some certifying, e.g. using <a href="https://code.google.com/p/googlemock/" rel="nofollow">google mock</a> and setting up expected calls (for e.g. destructors). But using a tool specialized upon this aspect, will certainly do better, than everything you're able to write yourself.

<blockquote>
 "is it better to use another C++ unit-testing framework?"
</blockquote>

So why bothering looking for different unit testing frameworks (that won't support such feature either, at least there's none I know of).

There are tools like <a href="http://valgrind.org/" rel="nofollow">valgrind</a> you can use, and run your <code>UnitTester</code> executable under their control to detect memory leaks.

Note: 
The above advice to do this with the <code>UnitTester</code> executable, won't be able to catch all of the possible memory leaks from the final executable produced with your code, but just help to find bugs/flaws with the actually tested code.

blocks|key|2893235|text|如果内存管理对我来说很重要，那么使用另一个C%2B%2B单元测试框架会更好吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2893236|我不知道c%2B%2B单元测试，但我用的是Dr.+memory，它可以在linux+windows和mac上工作，如果你有符号，它甚至可以告诉你内存泄漏发生在哪行！真正有用的:D|2893237|更多信息http://drmemory.org/|offset|length|2893238|entityMap|0|LINK|mutability|MUTABLE|url|http://drmemory.org/^0|0|0|4|K|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

If memory management is crucial for me, is it better to use another C++ unit-testing framework?

i don't know about c++ unit-testing, but i used Dr. memory, it works on linux windows and mac
if you have the symbols it even tells you in what line the memory leak happened! really usefull :D more info 
<a href="http://drmemory.org/" rel="noreferrer">http://drmemory.org/</a>

blocks|key|2058292|text|内存泄漏是系统接口使用不当的结果，单元测试应该检查这些接口是否在被测试的单元中正确使用，而不是那些接口的具体实现结果是什么。它应该检查您的单元直接使用的内存分配和释放接口是否按设计使用。测试系统特定的结果将是组件或集成测试的一部分。在单元测试中，内存管理接口位于被测单元的外部，因此应该使用测试实现来清除。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2058293|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|$]]

Memory leaks are a result of incorrect use of system interfaces, The unit test should check if those interfaces are being used correctly in your unit under test, not what the implementation specific results of any of those interfaces is. It should check that the memory allocation and deallocation interfaces used directly by your unit are being used as designed. Testing the system specific results would be a part of component or integration testing. In the unit test, the memory management interfaces are external to the unit under test and thus should be stubbed out with a test implementation.

blocks|key|4319212|text|即使这个帖子已经很旧了。我最近一直在找这个。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4319213|现在我想出了一个简单的解决方案(灵感来自https://stackoverflow.com/a/19315100/8633816)|offset|length|4319214|只需写下下面的头：|4319215|#include+"gtest/gtest.h"
#include+<crtdbg.h>

class+MemoryLeakDetector+{
public:
++++MemoryLeakDetector()+{
++++++++_CrtMemCheckpoint(&memState_);
++++}

++++~MemoryLeakDetector()+{
++++++++_CrtMemState+stateNow,+stateDiff;
++++++++_CrtMemCheckpoint(&stateNow);
++++++++int+diffResult+=+_CrtMemDifference(&stateDiff,+&memState_,+&stateNow);
++++++++if+(diffResult)
++++++++++++reportFailure(stateDiff.lSizes[1]);
++++}
private:
++++void+reportFailure(unsigned+int+unfreedBytes)+{
++++++++FAIL()+<<+"Memory+leak+of+"+<<+unfreedBytes+<<+"+byte(s)+detected.";
++++}
++++_CrtMemState+memState_;
};|code-block|syntax|javascript|4319216|然后只需将本地MemoryLeakDetector添加到您的测试中：|4319217|TEST(TestCase,+Test)+{
++++//+Do+memory+leak+detection+for+this+test
++++MemoryLeakDetector+leakDetector;

++++//Your+test+code
}|4319218|示例：|style|BOLD|4319219|像这样的测试：|4319220|TEST(MEMORY,+FORCE_LEAK)+{
++++MemoryLeakDetector+leakDetector;

++++int*+dummy+=+new+int;
}|4319221|生成输出：|4319222|​|4319223|📷|atomic|4319224|4319225|我相信有更好的工具，但这是一个非常简单和简单的解决方案。|4319226|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/19315100/8633816|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/957caf6d4cbf7cc0735c4140215ffd76.png|imageAlt^0|0|K|18|0|0|0|0|0|0|0|3|0|0|0|0|0|0|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1N|8|@]|9|@$D|1O|E|1P|1|1Q]]|A|$]]|$1|F|3|G|5|6|7|1R|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1S|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1T|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|1U|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|1V|8|@$D|1W|E|1X|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|W|3|X|5|J|7|1Z|8|@]|9|@]|A|$K|L]]|$1|Y|3|Z|5|6|7|20|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|21|8|@]|9|@]|A|$]]|$1|12|3|13|5|14|7|22|8|@]|9|@$D|23|E|24|1|25]]|A|$]]|$1|15|3|11|5|6|7|26|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|27|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|28|8|@]|9|@]|A|$]]]|19|$1A|$5|1B|1C|1D|A|$1E|1F]]|1G|$5|1H|1C|1I|A|$1J|1K|1L|-4]]]]

Even if this thread is very old. I was searching for this lately.
I now came up with a simple solution (inspired by <a href="https://stackoverflow.com/a/19315100/8633816">https://stackoverflow.com/a/19315100/8633816</a>)
Just write the following header:
<pre><code>#include &quot;gtest/gtest.h&quot;
#include &lt;crtdbg.h&gt;

class MemoryLeakDetector {
public:
 MemoryLeakDetector() {
 _CrtMemCheckpoint(&amp;memState_);
 }

 ~MemoryLeakDetector() {
 _CrtMemState stateNow, stateDiff;
 _CrtMemCheckpoint(&amp;stateNow);
 int diffResult = _CrtMemDifference(&amp;stateDiff, &amp;memState_, &amp;stateNow);
 if (diffResult)
 reportFailure(stateDiff.lSizes[1]);
 }
private:
 void reportFailure(unsigned int unfreedBytes) {
 FAIL() &lt;&lt; &quot;Memory leak of &quot; &lt;&lt; unfreedBytes &lt;&lt; &quot; byte(s) detected.&quot;;
 }
 _CrtMemState memState_;
};
</code></pre>
Then just add a local MemoryLeakDetector to your Test:
<pre><code>TEST(TestCase, Test) {
 // Do memory leak detection for this test
 MemoryLeakDetector leakDetector;

 //Your test code
}
</code></pre>
Example:
A test like:
<pre><code>TEST(MEMORY, FORCE_LEAK) {
 MemoryLeakDetector leakDetector;

 int* dummy = new int;
}
</code></pre>
Produces the output:
<a href="https://i.stack.imgur.com/LuNJf.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/LuNJf.png" alt="enter image description here" /></a>
I am sure there are better tools out there, but this is a very easy and simple solution.

blocks|key|283473|text|不确定这在2015年是否有效，但从2018年左右开始，我们将GoogleTest与CLang的消毒剂一起使用，包括LeakSanitizer、AddressSanitizer和UndefinedBehavior消毒剂。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|283474|只需构建启用了杀菌器的测试，例如基于CMake的项目：|283475|++add_compile_options(-fsanitize=leak,address,undefined+-fno-omit-frame-pointer+-fno-common+-O1)
++link_libraries(-fsanitize=leak,address,undefined)|code-block|syntax|javascript|283476|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Not sure whether this worked in 2015, but since 2018 or so we use GoogleTest with CLang's sanitizers, including LeakSanitizer, AddressSanitizer and UndefinedBehavior sanitizer.
Just build tests with sanitizers enabled, example for the CMake-based project:
<pre><code> add_compile_options(-fsanitize=leak,address,undefined -fno-omit-frame-pointer -fno-common -O1)
 link_libraries(-fsanitize=leak,address,undefined)
</code></pre>

I'm surprised that Google C++ Testing Framework does not explicitly support checking for memory leaks. There is, however, a workaround for Microsoft Visual C++, but what about Linux?

If memory management is crucial for me, is it better to use another C++ unit-testing framework?

GoogleTest and Memory Leaks

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我很惊讶谷歌C++测试框架没有明确支持内存泄漏检查。然而，Microsoft Visual C++有一个变通办法，但是Linux呢？如果内存管理对我来说很重要，那么使用另一个C++单元测试框架会更好吗？

问GoogleTest和内存泄漏
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问GoogleTest和内存泄漏EN