C++ valgrind 在 hello world 中显示内存泄漏

问题描述

我的程序代码是

#include <iostream>

int main(int argc, const char *argv[])
{
  std::cout << "hello world!
";
  return 0;
}

我用标志编译它

-Wpedantic -pedantic-errors -std=c++11 -g -Wall -Wextra

在上面运行Valgrind，看到了一些奇怪的东西，这个简单的程序有内存泄漏，valgrind --leak-check=full --show-leak-kinds=all命令的输出是

Run Valgrind on it and saw something strange, this simple program has memory leak, output of valgrind --leak-check=full --show-leak-kinds=all command is

==4492== 72,704 bytes in 1 blocks are still reachable in loss record 1 of 1
==4492==    at 0x4C28C20: malloc (vg_replace_malloc.c:296)
==4492==    by 0x4EBF11F: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
==4492==    by 0x400E9F9: call_init.part.0 (dl-init.c:78)
==4492==    by 0x400EAE2: call_init (dl-init.c:36)
==4492==    by 0x400EAE2: _dl_init (dl-init.c:126)
==4492==    by 0x40011C9: ??? (in /lib/x86_64-linux-gnu/ld-2.19.so)

我的问题是 - 如何找出发生了什么?

my question is - how to find out what is going on?

推荐答案

这是linux系统动态库加载器永远保留的内存.找出发生了什么的方法包括阅读 _dl_init() 函数的代码，例如:此处.另一种选择是使用调试器逐步执行您的程序，您需要在运行之前 break _init 并且可能还使用 disassemble 和 si，因为 glibc 不能在未优化的情况下构建.

This is memory reserved forever by linux system dynamic library loader. Ways to find out what's going on include reading code for _dl_init() function, e.g.: here. Another option is to step-through your program with debugger, you'll want to break _init before run and probably also use disassemble and si, as glibc can't be built unoptimized.

查看讨论这里(可能标记作为重复)

See discussion here (and probably mark as dup)

这篇关于C++ valgrind 在 hello world 中显示内存泄漏的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！