整个测试代码包含在main.cpp中,如下所示:
#include <iostream>
using std::cout;
using std::endl;
void f(int i) {
int* pi = new int;
*pi = i;
std::cout << "*pi = " << *pi << std::endl;
}
int main(int argc, char *argv[]) {
int i = 0;
while (i < 10000) {
f(i);
++i;
}
return 0;
}
Run Code Online (Sandbox Code Playgroud)
我编译没有优化-O0(来自Eclipse Qt项目):
g++ -c -pipe -O0 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -Irelease -o release/main.o main.cpp
Run Code Online (Sandbox Code Playgroud)
然后链接如下:
g++ -Wl,-O0 -o test release/main.o -L/usr/lib -lQtGui -lQtCore -lpthread
Run Code Online (Sandbox Code Playgroud)
我通过valgrind运行可执行文件并获得以下输出:
laptop:~/workspace/test$ valgrind --leak-check=yes test
==3939== Memcheck, a memory error detector
==3939== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==3939== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info
==3939== Command: test
==3939==
==3939==
==3939== HEAP SUMMARY:
==3939== in use at exit: 0 bytes in 0 blocks
==3939== total heap usage: 1,387 allocs, 1,387 frees, 64,394 bytes allocated
==3939==
==3939== All heap blocks were freed -- no leaks are possible
==3939==
==3939== For counts of detected and suppressed errors, rerun with: -v
==3939== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 8)
Run Code Online (Sandbox Code Playgroud)
我相信valgrind应该报告内存泄漏而不是因为调用中分配的堆内存而不会发生泄漏 new int
编辑:更改上面的代码使用std :: cout而不是qDebug()具有相同的结果
如果我编译并链接相同的代码(来自Eclipse CDT项目)没有Qt依赖项,valgrind会检测到泄漏:
g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"main.d" -MT"main.d" -o"main.o" "../main.cpp"
g++ -o"test2" ./main.o
==4604== HEAP SUMMARY:
==4604== in use at exit: 40,000 bytes in 10,000 blocks
==4604== total heap usage: 10,000 allocs, 0 frees, 40,000 bytes allocated
==4604==
==4604== 40,000 bytes in 10,000 blocks are definitely lost in loss record 1 of 1
==4604== at 0x402569A: operator new(unsigned int) (vg_replace_malloc.c:255)
==4604== by 0x8048756: f(int) (main.cpp:7)
==4604== by 0x80487BB: main (main.cpp:18)
==4604==
==4604== LEAK SUMMARY:
==4604== definitely lost: 40,000 bytes in 10,000 blocks
==4604== indirectly lost: 0 bytes in 0 blocks
==4604== possibly lost: 0 bytes in 0 blocks
==4604== still reachable: 0 bytes in 0 blocks
==4604== suppressed: 0 bytes in 0 blocks
==4604==
==4604== For counts of detected and suppressed errors, rerun with: -v
==4604== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 19 from 8)
Run Code Online (Sandbox Code Playgroud)
我正在使用Kubuntu 10.04 32位并尝试过Debug和Release版本,我做错了什么或者为什么valgrind在与Qt链接时报告内存泄漏?
Pet*_*McG 21
发生这种情况的原因是致电:
valgrind --leak-check=yes test
Run Code Online (Sandbox Code Playgroud)
实际上是在/ usr/bin/test上运行valgrind,它是一个内置程序,用于检查文件类型并比较值,我需要的只是:
valgrind --leak-check=yes ./test
Run Code Online (Sandbox Code Playgroud)
| 归档时间: |
|
| 查看次数: |
4532 次 |
| 最近记录: |