valgrind工具检测内存错误.pdfVIP

valgrind 工具检测内存错误 1 内存泄露 1.2 错误提示 are definitely lost in loss 1.1 c 源代码mem_leak1.c #include stdlib.h #include stdio.h #include string.h static void mem_leak(void) { char *p =malloc(10); } int main() { mem_leak(); } 1.2 使用命令 gcc -o mem_leak1 –g mem_leak1.c valgrind --track-fds=yes --leak-check=full --undef-value-errors=yes ./mem_leak1 1.3 检测结果 ==3653== Memcheck, a memory error detector ==3653== Copyright (C) 2002-2011, and GNU GPLd, by Julian Seward et al. ==3653== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==3653== Command: ./a.out ==3653== ==3653== ==3653== FILE DESCRIPTORS: 3 open at exit. ==3653== Open file descriptor 2: /dev/pts/1 ==3653== inherited from parent ==3653== ==3653== Open file descriptor 1: /dev/pts/1 ==3653== inherited from parent ==3653== ==3653== Open file descriptor 0: /dev/pts/1 ==3653== inherited from parent ==3653== ==3653== ==3653== HEAP SUMMARY: ==3653== in use at exit: 10 bytes in 1 blocks ==3653== total heap usage: 1 allocs, 0 frees, 10 bytes allocated ==3653== ==3653== 10 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==3653== at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==3653== by 0x400505: mem_leak (mem_leak1.c:6) ==3653== by 0x400514: main (mem_leak1.c:10) //////////////////////////////////////// 在这里报告内存泄露的位置和大小。 /////////////////////////////////////////// ==3653== ==3653== LEAK SUMMARY: ==3653== definitely lost: 10 bytes in 1 blocks ==3653== indirectly lost: 0 bytes in 0 blocks ==3653== possibly lost: 0 bytes in 0 blocks ==3653== still reachable: 0 bytes in 0 blocks ==3653== suppressed: 0 bytes in 0 blocks ==3653== ==3653== For counts of detected and suppressed errors, rerun with: -v ==3653== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 2 from 2)