如何调试从Go代码到C代码的调用中的memleak?

时间:2019-05-02 13:49:43

标签: c go

我在Go中有代码,该代码内部使用C语言进行了很多库调用。我编写了接口,使从Go到C的转换,反之亦然。该库没有任何泄漏,因为我已经使用了很长时间了。我肯定在界面级别上缺少一些东西。

尝试使用valgrind,但无法查明泄漏源。从valgrind附加泄漏控制台日志。

==59864== 24 bytes in 2 blocks are definitely lost in loss record 565 of 883
==59864==    at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==59864==    by 0x7E14B3: _cgo_9699bfde5761_Cfunc__Cmalloc (_cgo_export.c:27)
==59864==    by 0x46A2AF: runtime.asmcgocall (in /home/sumanb/work/BangDB-Core/golang/ecommerce/ecommerce)
==59864==    by 0xC00006E17F: ???
==59864==    by 0xAF97E47: ???
==59864==    by 0x466101: runtime.(*mcache).nextFree.func1 (in /home/sumanb/work/BangDB-Core/golang/ecommerce/ecommerce)
==59864==    by 0x4041D7F: ???
==59864==    by 0xC00019484D: ???
==59864==    by 0x106F: ???
==59864==    by 0xC00000197F: ???
==59864==    by 0x442ADF: ??? (in /home/sumanb/work/BangDB-Core/golang/ecommerce/ecommerce)
==59864== 
==59864== 48 bytes in 4 blocks are definitely lost in loss record 674 of 883
==59864==    at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==59864==    by 0x7E14B3: _cgo_9699bfde5761_Cfunc__Cmalloc (_cgo_export.c:27)
==59864==    by 0x46A2AF: runtime.asmcgocall (in /home/sumanb/work/BangDB-Core/golang/ecommerce/ecommerce)
==59864== 

0 个答案:

没有答案