[TOC] 參考：https://www.pengrl.com/p/29054/ ## Ubuntu下載valgrind ``` sudo apt-get install valgrind -y ``` ## Go代碼示例 ``` // cstring.go package main /* #include <stdio.h> int c_print(const char* a) { //puts(a); } */ import "C" import ( "reflect" "unsafe" ) func getCString(s string) *C.char{ s = s + "\000" p := (*reflect.StringHeader)(unsafe.Pointer(&s)) return (*C.char)(unsafe.Pointer(p.Data)) } func main() { for i := 0; i < 99999 ; i++ { C.c_print(C.CString("hello world\n")) } } ``` 編譯 ``` go build -o cstring cstring.go ``` ## 簡單使用 ``` valgrind --leak-check=full ./cstring ``` 輸入 ``` ==25893== LEAK SUMMARY: ==25893== definitely lost: 1,299,987 bytes in 99,999 blocks ==25893== indirectly lost: 0 bytes in 0 blocks ==25893== possibly lost: 1,440 bytes in 5 blocks ==25893== still reachable: 0 bytes in 0 blocks ==25893== suppressed: 0 bytes in 0 blocks ==25893== ==25893== For counts of detected and suppressed errors, rerun with: -v ==25893== Use --track-origins=yes to see where uninitialised values come from ==25893== ERROR SUMMARY: 9 errors from 7 contexts (suppressed: 0 from 0) ``` 可以看到，雖然valgrind給出了`definitely lost`的結果，但是幾乎無法直接找到泄漏的位置。