[心得] memory leak test tool: valgrind

看板LinuxDev作者dozer (rezod)時間18年前 (2006/12/15 15:40)推噓0(0推 0噓 5→)

留言5則, 2人參與討論串1/1

我照著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)