在Linux环境下查找C代码中的内存泄漏

发布于 2024-09-16 01:22:45 字数 172 浏览 7 评论 0原文

你好，我在使用 valgrind 时遇到问题当我将它与 valgrind --leak-check=full 一起使用时，然后执行文件的名称它会告诉我内存泄漏在哪些块中，但是当我找不到我使用 free 的指针时。是否有某种标志可以告诉指针的名称。如果有任何人告诉我 Visual Studio 上的泄漏位置，我也非常想听听

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

梦归所梦 2024-09-23 01:22:45

它无法告诉您指针的名称，因为内存泄漏的整个概念是没有指针再指向内存（至少，对于 Valgrind 描述的泄漏类型） “肯定输了”）。

它可以告诉您的是分配内存的源文件和行号 - 然后您需要在源文件中查找该行以找出内存应该在哪里 em> 被释放。例如，如果 Valgrind 损失记录如下所示：

==17110== 49 bytes in 1 blocks are definitely lost in loss record 17 of 35
==17110==    at 0x4023D6E: malloc (vg_replace_malloc.c:207)
==17110==    by 0x80C4CF8: do_foo (foo.c:1161)
==17110==    by 0x80AE325: xyzzy (bar.c:466)
==17110==    by 0x8097C46: io (bar.c:950)
==17110==    by 0x8098163: main (quux.c:1291)

那么您需要查看 foo.c 中的第 1161 行，该行位于函数 do_foo() 内。这就是内存分配的地方（使用malloc()），只有你可以说出应该在哪里释放它。

It can't tell you the name of the pointer, because the whole idea of a memory leak is that no pointer points at the memory any more (at least, for the kinds of leaks that Valgrind describes as "definitely lost").

What it can tell you is the source file and line number where the memory was allocated - you then will need to look up that line in your source to figure out where the memory is supposed to be deallocated. For example, if the Valgrind loss record looks like:

==17110== 49 bytes in 1 blocks are definitely lost in loss record 17 of 35
==17110==    at 0x4023D6E: malloc (vg_replace_malloc.c:207)
==17110==    by 0x80C4CF8: do_foo (foo.c:1161)
==17110==    by 0x80AE325: xyzzy (bar.c:466)
==17110==    by 0x8097C46: io (bar.c:950)
==17110==    by 0x8098163: main (quux.c:1291)

Then you need to look at line 1161 in foo.c, which is within the function do_foo(). That's where the memory was allocated (with malloc()), and only you can say where it should have been freed.

回复收藏 0 原文