Interactively

建立以下<代码>main.cpp文档(在新的专册中):

#include <string.h>
int main()
{
 int a = 1;
 char* s = new char[17];
 strcpy_s(s,17,"stackoverflow_pb");
 char* ss = new char[14];
 strcpy_s(ss, 14,"stackoverflow");
 delete[] ss;
 return 0;
}

然后:

Put a breakpoint on the first line "int a..."
Click Debug > Windows > Show Diagnostic Tools; and pick memory usage
Then debug the code (F5), when the breakpoint is hit, click Take snapshot on the Memory Usage summary toolbar.
Go to the last line "return 0.." (step over (F10) several times) and take another snapshot.
Click on the red arrow in the second snapshot (in memory usage tab)
this will open a new "snapshot" tab that permits you to compare this snapshot with the first one (or another one) and to detect memory leaks. In this example there is a memory leak for variable s (stackoverflow_pb). You can find it by double click the "char[]" object.

上述程序的关键步骤见以下图象:

By programming

将守则改为:

#include <iostream>

#include "windows.h"
#define _CRTDBG_MAP_ALLOC //to get more details
#include <stdlib.h>  
#include <crtdbg.h>   //for malloc and free
int main()
{
    _CrtMemState sOld;
    _CrtMemState sNew;
    _CrtMemState sDiff;
    _CrtMemCheckpoint(&sOld); //take a snapshot
    char* s = new char[17];
    strcpy_s(s, 17, "stackoverflow_pb");
    char* ss = new char[14];
    strcpy_s(ss, 14, "stackoverflow");
    delete[] ss;
    _CrtMemCheckpoint(&sNew); //take a snapshot 
    if (_CrtMemDifference(&sDiff, &sOld, &sNew)) // if there is a difference
    {
        OutputDebugString(L"-----------_CrtMemDumpStatistics ---------");
        _CrtMemDumpStatistics(&sDiff);
        OutputDebugString(L"-----------_CrtMemDumpAllObjectsSince ---------");
        _CrtMemDumpAllObjectsSince(&sOld);
        OutputDebugString(L"-----------_CrtDumpMemoryLeaks ---------");
        _CrtDumpMemoryLeaks();
    }
    return 0;
}

同样,但通过编码,你可以将其融入自动建筑系统,其职能是:_CrtMemCheckpoint<<<<>>> 参考书目/参考书目/目录相比之下,血清和回归的真实记忆有所不同。

Since it is the case, it enters the conditional block and prints details about the leaks via several functions (see _CrtMemDumpStatistics , _CrtMemDumpAllObjectsSince and _CrtDumpMemoryLeaks - the latter doesn t require snapshots).

参看该产出,在最后一行“返回0”上打了一个断点,打上了,并看着 de。产出如下:

获取更多信息,见以下链接:

Interactive analysis : Measure memory usage in Visual Studio
via programming : Find memory leaks with the CRT library and CRT debug Heap Files (for heap corruption also)

Answer 2

How about 视觉探测器? 它没有被削弱,但我认为它是最受欢迎的。

Answer 3

Dr. Memory是一种记忆监测工具,能够查明与记忆有关的方案错误,例如:获得未开端记忆的机会、获得不可弥补的记忆的机会(包括分配的蒸气单位之外、蒸气流和溢出)、获得免费记忆的机会、双重自由、记忆和(视窗)处理泄漏、全球空间数据基础设施使用差错以及获得未保留的地方存储器。

记忆博士在视窗、赖恩、Mac、或ARM硬件上运行未经修改的双版。

记忆博士以

Answer 4

http://www.softwareverification.com/cpp-memory.php>rel=“nofollow”>C++ 记忆验证仪发现并处理利用演播室、德尔菲和其他编辑制作的本土视窗节目中的泄漏。快速并能够处理大量的工作量(一些用户在一次运行中追踪数亿美元的拨款和交易地点)。

披露: I m是C++记忆验证器的设计者。我们建造了这一设施,因为其他工具在我们与ColiWorks R&公司(D Ltd)合作时能够处理工作量。

Answer 5

《2015年视觉演播室》和后来版本有《土著记忆分析工具》,详细检查:https://dzone.com/articles/native-memory-leak-diagnostics 。

Answer 6

Application Verifier是检测本地(C或C++)应用中泄漏的一个良好工具。你可以与视觉演播室或WinDbg一起使用。除了记忆泄露外,你还可以检查黑色的腐败,处理错误的做法。与WinDbg(!analyze-v)一起使用用户提供了很好的见解。

Answer 7

可靠的解决办法是使用。这是一个跨平台/跨编解决方案,因此,所获取的知识可转让至 gcc和部族。

这一工具可以延伸到翻新的机敏化和一般记忆错误探测(在免费、双重免费、未初步使用等之后使用),但泄漏探测是其强点之一。你们需要Microsoft汇编商的/fsanitize=address /Zi备选办法,但你可以提及关于如何将其纳入解决方案和更大项目的第一条相关条款(通过CMake配置或项目财产贴现)。

Answer 8

你们可以利用DevPartner工具,利用视觉演播室,在C++应用中发现传闻。

Answer 9

A standalone tool (CLI) for tracking native (C++) memory leaks. Run your app in Release mode (PDBs should be available) and let it run along with it. It outputs all the suspected call stacks and their respected leak size:

Git Hub: C++ Windows Leak探测器

Interactively

By programming

友情链接