blocks|key|3791264|text|第二个valgrind...我将添加electric+fence。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3791265|entityMap|0|LINK|mutability|MUTABLE|url|http://valgrind.org/|1|http://directory.fsf.org/project/ElectricFence/^0|3|8|0|I|E|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

second the <a href="http://valgrind.org/" rel="noreferrer">valgrind</a>... and I'll add <a href="http://directory.fsf.org/project/ElectricFence/" rel="noreferrer">electric fence</a>.

blocks|key|730499|text|linux下的Valgrind相当不错；我在Windows下没有这方面的经验。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|730500|entityMap|0|LINK|mutability|MUTABLE|url|http://valgrind.org/^0|7|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://valgrind.org/" rel="nofollow noreferrer">Valgrind</a> under linux is fairly good; I have no experience under Windows with this.

blocks|key|3791733|text|如果你有钱：IBM+Rational+Purify是一个非常强大的行业强度的内存泄漏和内存损坏检测器的C/C%2B%2B。存在于Windows、Solaris和Linux中。如果您只使用linux，并且想要一个便宜的解决方案，那么可以使用Valgrind。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3791734|entityMap|0|LINK|mutability|MUTABLE|url|http://www-01.ibm.com/software/awdtools/purify/^0|6|J|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you have the money: <a href="http://www-01.ibm.com/software/awdtools/purify/" rel="nofollow noreferrer">IBM Rational Purify</a> is an extremely powerful industry-strength memory leak and memory corruption detector for C/C++. Exists for Windows, Solaris and Linux. If you're linux-only and want a cheap solution, go for Valgrind.

blocks|key|730795|text|Mudflap为gcc！它实际上将检查编译成可执行文件。只需添加|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|730796|-fmudflap+-lmudflap|code-block|syntax|javascript|730797|敬你们的gcc旗帜。|730798|entityMap|0|LINK|mutability|MUTABLE|url|http://gcc.gnu.org/wiki/Mudflap_Pointer_Debugging^0|0|7|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

<a href="http://gcc.gnu.org/wiki/Mudflap_Pointer_Debugging" rel="nofollow noreferrer">Mudflap</a> for gcc! It actually compiles the checks into the executable. Just add

<pre><code>-fmudflap -lmudflap
</code></pre>

to your gcc flags.

blocks|key|725919|text|lint+(与splint非常相似的开源工具)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|725920|entityMap|0|LINK|mutability|MUTABLE|url|http://splint.org/^0|7|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

lint (very similar open-source tool called <a href="http://splint.org/" rel="nofollow noreferrer">splint</a>)

blocks|key|3791375|text|很痛苦，但如果你非要用一个..|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3791376|我推荐DevPartner+BoundsChecker套间。这就是我工作场所的人为了这个目的而使用的。付费n专有..不是免费软件。|offset|length|3791377|entityMap|0|LINK|mutability|MUTABLE|url|http://www.borland.com/products/devpartner/read/^0|0|3|O|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Painful but if you had to use one.. 
I'd recommend the <a href="http://www.borland.com/products/devpartner/read/" rel="nofollow noreferrer">DevPartner BoundsChecker</a> suite.. that's what people at my workplace use for this purpose. Paid n proprietary.. not freeware.

blocks|key|730868|text|如果您在Linux上使用glibc，那么内置的调试堆代码也是值得使用的。要使用它，请链接到-lmcheck或使用值1、2或3定义(并导出)+MALLOC_CHECK_环境变量。The+glibc+manual+provides+more+information.|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|730869|此模式对于检测双重释放最有用，并且在执行释放操作时，它经常发现分配的内存区之外的写操作。我不认为它会报告内存泄漏。|730870|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gnu.org/software/libtool/manual/libc/Heap-Consistency-Checking.html^0|19|8|1Y|D|2G|17|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

Also worth using if you're on Linux using glibc is the built-in debug heap code. To use it, link with -lmcheck or define (and export) the MALLOC_CHECK_ environment variable with the value 1, 2, or 3. <a href="http://www.gnu.org/software/libtool/manual/libc/Heap-Consistency-Checking.html" rel="nofollow noreferrer">The glibc manual provides more information.</a>

This mode is most useful for detecting double-frees, and it often finds writes outside the allocated memory area when doing a free. I don't think it reports leaked memory.

blocks|key|5202926|text|我在cppcheck上有相当多的成功，它只做静态分析。它是开源的，并且有一个命令行界面(我没有以任何其他方式使用它)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5202927|entityMap|0|LINK|mutability|MUTABLE|url|http://sourceforge.net/apps/mediawiki/cppcheck/index.php?title=Main_Page#Cppcheck_-_A_tool_for_static_C.2FC.2B.2B_code_analysis^0|2|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I had quite some hits with <a href="http://sourceforge.net/apps/mediawiki/cppcheck/index.php?title=Main_Page#Cppcheck_-_A_tool_for_static_C.2FC.2B.2B_code_analysis" rel="nofollow">cppcheck</a>, which does static analysis only. It is open source and has a command line interface (I did not use it in any other way).

blocks|key|2946909|text|我对任何内存泄漏检测器的关注度都很低。通常情况下，它们有太多的假阳性，没有任何用处。我建议这两个是干扰最小的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2946910|GlowCode|offset|length|2946911|Debug+heap|2946912|entityMap|0|LINK|mutability|MUTABLE|url|http://www.glowcode.com/|1|http://msdn.microsoft.com/en-us/library/974tc9t1(VS.80).aspx^0|0|0|8|0|0|0|A|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

I've had minimal love for any memory leak detectors. Typically there are far too many false positives for them to be of any use. I would recommend these two as beiong the least intrusive:

<a href="http://www.glowcode.com/" rel="nofollow noreferrer">GlowCode</a>

<a href="http://msdn.microsoft.com/en-us/library/974tc9t1(VS.80).aspx" rel="nofollow noreferrer">Debug heap</a>

blocks|key|5202486|text|对于内存泄漏的Win32调试，我有非常好的使用普通老式CRT+Debug+Heap的经验，它是Visual+C的一个库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5202487|在调试构建中，malloc+(et+al)被重新定义为_malloc_dbg+(et+al)，并且还有其他用于检索结果的调用，如果没有设置_DEBUG，这些调用都是未定义的。它在堆上设置了各种边界保护，并允许您在任何时候显示结果。|5202488|当我意识到一些时间例程扰乱了库运行时间分配，直到我发现_CRT_BLOCK时，我发现了一些误报。|5202489|我必须首先生产DOS，然后是Win32控制台和永远运行的服务。据我所知，没有内存泄漏，并且在至少一个地方，代码在PC上的监视器出现故障之前在无人值守的情况下运行了两年(尽管PC是正常的！)。|5202490|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

For Win32 debugging of memory leaks I have had very good experiences with the plain old CRT Debug Heap, that comes as a lib with Visual C.

In a Debug build malloc (et al) get redefined as _malloc_dbg (et al) and there are other calls to retrieve results, which are all undefined if _DEBUG is not set. It sets up all sorts of boundary guards on the heap, and allows you to diplay the results at any time.

I had a few false positives when I was witting some time routines that messed with the library run time allocations until I discovered _CRT_BLOCK.

I had to produce first DOS, then Win32 console and services that would run for ever. As far as I know there are no memory leaks, and in at least one place the code run for two years unattended before the monitor on the PC failed (though the PC was fine!).

blocks|key|3791880|text|在Windows上，我使用的是Visual+Leak+Detector。与VC%2B%2B集成，易于使用(只需包含一个头文件并设置LIB以查找lib)，开源，免费使用FTW。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3791881|entityMap|0|LINK|mutability|MUTABLE|url|http://vld.codeplex.com/^0|F|K|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

On Windows, I have used <a href="http://vld.codeplex.com" rel="nofollow noreferrer">Visual Leak Detector</a>. Integrates with VC++, easy to use (just include a header and set LIB to find the lib), open source, free to use FTW.

blocks|key|730634|text|在大学里，当我在Unix+Solaris下做大多数事情的时候，我用的是gdb。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|730635|然而，我会在Linux下使用valgrind。|730636|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gnu.org/software/gdb/|1|http://valgrind.org/^0|Z|3|0|0|E|8|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

At university when I was doing most things under Unix Solaris I used <a href="http://www.gnu.org/software/gdb/" rel="nofollow noreferrer">gdb</a>. 

However I would go with <a href="http://valgrind.org/" rel="nofollow noreferrer">valgrind</a> under Linux.

blocks|key|3791672|text|这些工具的鼻祖是商业的、闭源的Purify工具，它先是卖给了IBM，然后又卖给了联通。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3791673|Parasoft的Insure%2B%2B+(源代码工具)和valgrind+(开源)是另外两个真正的竞争对手。|3791674|琐事:+Purify的原始作者Reed+Hastings继续创建了NetFlix。|3791675|entityMap|0|LINK|mutability|MUTABLE|url|http://unicomsi.com/products/purifyplus/|1|http://en.wikipedia.org/wiki/Insure%252B%252B^0|F|6|0|0|9|8|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

The granddaddy of these tools is the commercial, closed-source <a href="http://unicomsi.com/products/purifyplus/" rel="nofollow noreferrer">Purify</a> tool, which was sold to IBM and then to UNICOM

Parasoft's <a href="http://en.wikipedia.org/wiki/Insure%2B%2B" rel="nofollow noreferrer">Insure++</a> (source code instrumentation) and valgrind (open source) are the two other real competitors. 

Trivia: the original author of Purify, Reed Hastings, went on to found NetFlix.

blocks|key|726295|text|没有人提到clang's+MSan，它非常强大。不过，它只在Linux上得到官方支持。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|726296|entityMap|0|LINK|mutability|MUTABLE|url|http://clang.llvm.org/docs/MemorySanitizer.html^0|5|C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

No one mentioned <a href="http://clang.llvm.org/docs/MemorySanitizer.html" rel="nofollow">clang's MSan</a>, which is quite powerful. It is officially supported on Linux only, though.

blocks|key|2947802|text|这个问题可能很老了，但我还是会回答它--也许我的答案会帮助某人找到他们的内存泄漏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2947803|这是我自己的项目--我把它作为开源代码：|2947804|https://sourceforge.net/projects/diagnostic/|offset|length|2947805|支持Windows+32位和64位平台，支持本机和混合模式调用堆栈。|2947806|不支持.NET垃圾回收。(C%2B%2B+cli的gcnew或C#的new)|2947807|It高性能工具，不需要任何集成(除非你真的想集成它)。|2947808|完整的手册可以在这里找到：|2947809|http://diagnostic.sourceforge.net/index.html|2947810|不要害怕它会在你的进程中实际检测到多少漏洞。它捕获整个进程中的内存泄漏。只分析最大的泄漏，而不是所有的。|2947811|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|18|0|0|0|0|0|0|0|18|1|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@$F|14|G|15|1|16]]|A|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1B|8|@]|9|@$F|1C|G|1D|1|1E]]|A|$]]|$1|R|3|S|5|6|7|1F|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|E]]|10|$5|W|X|Y|A|$Z|Q]]]]

This question maybe old, but I'll answer it anyway - maybe my answer will help someone to find their memory leaks.

This is my own project - I've put it as open source code:

<a href="https://sourceforge.net/projects/diagnostic/" rel="nofollow noreferrer">https://sourceforge.net/projects/diagnostic/</a>

Windows 32 &amp; 64-bit platforms are supported, native and mixed mode callstacks are supported.

.NET garbage collection is not supported. (C++ cli's gcnew or C#'s new)

It high performance tool, and does not require any integration (unless you really want to integrate it).

Complete manual can be found here:

<a href="http://diagnostic.sourceforge.net/index.html" rel="nofollow noreferrer">http://diagnostic.sourceforge.net/index.html</a>

Don't be afraid of how much it actually detects leaks it your process. It catches memory leaks from whole process. Analyze only biggest leaks, not all.

blocks|key|5202426|text|我将把valgrind作为内存泄漏的外部工具。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5202427|但是，对于我必须解决的大多数问题，我总是使用内部构建的工具。有时，外部工具的开销太大，或者设置起来太复杂。|5202428|既然可以编写自己的代码，为什么还要使用已经编写的代码:)|5202429|我开玩笑，但有时你需要一些简单的东西，而且你自己写会更快。通常，我只是将对malloc()和free()的调用替换为能够更好地跟踪谁分配了什么的函数。我的大多数问题似乎都是忘记释放的人，这有助于解决这个问题。|5202430|这真的取决于泄漏在哪里，如果你知道了，那么你就不需要任何工具了。但是，如果您对它的泄漏之处有一些了解，那么就使用您自己的工具，看看它是否对您有帮助。|5202431|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I'll second the valgrind as an external tool for memory leaks. 
But, for most of the problems I've had to solve I've always used internally built tools. Sometimes the external tools have too much overhead or are too complicated to set up.

Why use already written code when you can write your own :)

I joke, but sometimes you need something simple and it's faster to write it yourself.
Usually I just replace calls to malloc() and free() with functions that keep better
track of who allocates what. Most of my problems seem to be someone forgot to free and this helps to solve that problem.

It really depends on where the leak is, and if you knew that, then you would not need any tools. But if you have some insight into where you think it's leaking, then put in your own instrumentation and see if it helps you.

blocks|key|730899|text|我们的CheckPointer工具可以对GNUC3/4、C的MS方言和GreenHills+C执行此操作。它可以发现Valgrind无法发现的内存管理问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|730900|如果您的代码只是泄漏，在退出时，CheckPointer将告诉您所有未释放的内存被分配到哪里。|730901|entityMap|0|LINK|mutability|MUTABLE|url|http://www.semanticdesigns.com/Products/MemorySafety^0|3|C|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Our <a href="http://www.semanticdesigns.com/Products/MemorySafety" rel="nofollow">CheckPointer</a> tool can do this for GNU C 3/4 and, MS dialects of C, and GreenHills C. It can find memory management problems that Valgrind cannot.

If your code simply leaks, on exit CheckPointer will tell you where all the unfreed memory was allocated.

What memory leak detectors have people had a good experience with?

Here is a summary of the answers so far:

<a href="http://valgrind.org/" rel="nofollow noreferrer">Valgrind</a> - Instrumentation framework for building dynamic analysis tools.

<a href="http://directory.fsf.org/project/ElectricFence/" rel="nofollow noreferrer">Electric Fence</a> - A tool that works with GDB

<a href="http://splint.org/" rel="nofollow noreferrer">Splint</a> - Annotation-Assisted Lightweight Static Checking

<a href="http://www.glowcode.com/" rel="nofollow noreferrer">Glow Code</a> - This is a complete real-time performance and memory profiler for Windows and .NET programmers who develop applications with C++, C#, or any .NET Framework

Also see this <a href="https://stackoverflow.com/questions/45627/how-do-you-detectavoid-memory-leaks-in-your-unmanaged-code">stackoverflow post</a>.

Memory leak detectors for C?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

人们对哪些内存泄漏检测器有很好的体验？以下是到目前为止的答案摘要： -用于构建动态分析工具的工具框架。 -使用GDB的工具 -辅助注释的轻量级静态检查 -这是一个完整的实时性能和内存分析器，适用于使用C++、C#或任何.NET框架开发应用程序的Windows和.NET程序员另请参阅此。

问内存泄漏检测器的C？
EN

回答 17

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问内存泄漏检测器的C？EN

回答 17

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问内存泄漏检测器的C？
EN