作者dozer (rezod)
看板LinuxDev
标题[心得] memory leak test tool: valgrind
时间Fri Dec 15 15:50:34 2006
我照着q大提供的连结试用了valgrind
因为我用的是Ubuntu
所以是直接上repository下载的版本 (valgrind-3.2.0-Debian)
用法跟gdb差不多 很直觉
查memeory leak最简单的方法就是用
% valgrind --tool=memcheck program_name
如果一切正常没有漏记忆体 会有如下的画面：
==22574== Memcheck, a memory error detector.
==22574== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al.
==22574== Using LibVEX rev 1606, a library for dynamic binary translation.
==22574== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP.
==22574== Using valgrind-3.2.0-Debian, a dynamic binary instrumentation
framework.
==22574== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al.
==22574== For more details, rerun with: -v
==22574==
==22574==
==22574== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 31 from 1)
==22574== malloc/free: in use at exit: 0 bytes in 0 blocks.
==22574== malloc/free: 10,319 allocs, 10,319 frees, 156,300 bytes allocated.
==22574== For counts of detected errors, rerun with: -v
==22574== All heap blocks were freed -- no leaks are possible.
除了检查漏记忆体之外 他也会找一些看起来不太对劲的语法
比如我之前有一个用来去除字串前後空白的函式
里面用到这样的语法
if(i) strcpy(string,string+i);
(这种东西碰到string是字串常数就会segfault 只是之前偷懒不去管)
他就警告我source跟destination都一样之类的
严格的程度比gcc -Wall更高
另外像C的automatic variable如果宣告太大的阵列
(像char buffer[1024*1024] 之类的东西)
有些位址好像会overlap 运气不好可能就会当的乱七八糟
gcc不会管 但他也会告诉你
总之 目前用的挺满意 供大家参考罗！
--
We are Microsoft. Unix is irrelevant. Openness is futile.
Prepare to be assimilated.
-- seen on slashdot.org
--
※ 发信站: 批踢踢实业坊(ptt.cc)
◆ From: 140.109.176.158
※ 编辑: dozer 来自: 140.109.176.158 (12/15 18:03)
1F：→ qrtt1:呵..建议标题-> memory leak test tool: valgrind 12/15 20:33
2F：→ qrtt1:比较方便爬文的人search 12/15 20:33
※ 编辑: dozer 来自: 140.109.176.158 (12/15 21:29)
3F：→ dozer:完成啦^+++^ 12/15 21:30
※ 编辑: dozer 来自: 122.126.35.54 (12/15 23:52)
4F：→ qrtt1:呵，恭禧啊。分享是件快乐的事啊^^ 12/16 02:28
5F：→ dozer:补充一点 编译binary时要记得加-g才能用valgrind来debug 12/19 18:46