当我使用“-pg”编译我的程序时，Valgrind报告了“内存泄漏”？

编译以下简单代码时，我收到了Valgrind报告的内存泄漏，并启用了-pg。当我使用“-pg”编译我的程序时，Valgrind报告了“内存泄漏”？

#include <iostream> 
#include <boost/filesystem.hpp> 

#define BOOST_FILESYSTEM_VERSION 3 

using boost::filesystem::path; 

using namespace std; 

int main() { 

     path ptDir; 
     ptDir = "/home/foo/bar"; 

     if (true == is_directory((const path &)ptDir)){ 
       cout << "ptDir: " << ptDir << endl; 
     } 
}

完整编译选项如下。

g++ -pg -g test.cpp -lboost_system -lboost_filesystem

运行的valgrind的命令是：

valgrind --gen-suppressions=all --track-origins=yes --error-limit=no --leak-check=full --show-reachable=yes -v --trace-children=yes --track-fds=yes --log-file=vg.log ./a.out

然后Valgrind的给了我一个内存泄漏错误。

==9598== HEAP SUMMARY: 
==9598==  in use at exit: 4,228 bytes in 1 blocks 
==9598== total heap usage: 136 allocs, 135 frees, 17,984 bytes allocated 
==9598== 
==9598== Searching for pointers to 1 not-freed blocks 
==9598== Checked 130,088 bytes 
==9598== 
==9598== 4,228 bytes in 1 blocks are still reachable in loss record 1 of 1 
==9598== at 0x402A5E6: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) 
==9598== by 0x4260F44: monstartup (gmon.c:134) 
==9598== by 0xBED6B636: ??? 
==9598== by 0x4E45504E: ??? 
==9598== 
{ 
    <insert_a_suppression_name_here> 
    Memcheck:Leak 
    fun:calloc 
    fun:monstartup 
    obj:* 
    obj:* 
} 
==9598== LEAK SUMMARY: 
==9598== definitely lost: 0 bytes in 0 blocks 
==9598== indirectly lost: 0 bytes in 0 blocks 
==9598==  possibly lost: 0 bytes in 0 blocks 
==9598== still reachable: 4,228 bytes in 1 blocks 
==9598==   suppressed: 0 bytes in 0 blocks 
==9598== 
==9598== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) 
==9598== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

这是正确的吗？我使用Ubuntu 12.04 /内核3.2.0-32泛型

来源

2012-12-24 macpaul

你应该“相信”valgrind，但如果性能分析功能没有释放所有的内存，我不会感到惊讶。尝试使用“-pg”进行编译，看看是否有所作为 –

Valgrind FAQ：

"still reachable" means your program is probably ok -- it didn't free some 
memory it could have. This is quite common and often reasonable. Don't use 
--show-reachable=yes if you don't want to see these reports.

来源

2012-12-24 08:28:05 perreal

的分配与来自这样的事实： by 0x4260F44: monstartup (gmon.c:134) 表明它是-pg的副作用 - 这没有什么可以做的。不要混用-pg和valgrind是我的建议。

来源

2012-12-24 09:21:53

当我使用“-pg”编译我的程序时，Valgrind报告了“内存泄漏”？

回答

相关问题