linux排查内存泄漏

最新推荐文章于 2024-02-27 14:55:33 发布

LIEYz

最新推荐文章于 2024-02-27 14:55:33 发布

阅读量2.2k

点赞数 1

分类专栏： linux

本文链接：https://blog.csdn.net/qq_18998145/article/details/94565013

版权

linux 专栏收录该内容

14 篇文章 1 订阅

订阅专栏

1. 查看内存使用情况

可以使用以下命令查看是否有明显内存溢出。

gnome-system-monitor

ubuntu下显示最近一段时间内的CPU、内存、交换区及网络的使用情况的视图工具

vmstat  -t 1

每秒显示内存使用情况

top -H -p pid

* VIRT：线程占用的虚拟内存
* RES：线程占用的物理内存
* SHR：线程使用的共享内存      
* %MEM：线程使用的物理内存和总内存的百分

2. mtrace

修改源程序：添加头文件，并且用mtrace()和muntrace()两条语句将要检测内存泄露的代码块包含起来

编译程序并用该环境变量来定义一个文件log用于输出：

运行程序，log文件分析：

日志中一连串的"+"号表示程序一直在申请内存空间,（若有“-”号，表示程序在释放空间）。

3. valgrind

Memcheck是valgrind应用最广泛的工具，一个重量级的内存检查器，能够发现开发中绝大多数内存错误使用情况，比如：使用未初始化的内存，使用已经释放了的内存，内存访问越界等。

使用示例：

#include <stdio.h>
#include <stdlib.h>
char* getMemory()
{
        char *p = (char *)malloc(30);
        int* a = new int;
        return p;
}

int main()
{
        char *p = getMemory();
        p = NULL;

}

nvidia@tegra-ubuntu:~/yile/work/tmp$ g++ valgrind.cpp  -g
nvidia@tegra-ubuntu:~/yile/work/tmp$ valgrind --tool=memcheck --leak-check=yes --show-reachable=yes ./a.out
==15990== Memcheck, a memory error detector
==15990== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==15990== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==15990== Command: ./a.out
==15990==
==15990==
==15990== HEAP SUMMARY:
==15990==     in use at exit: 72,738 bytes in 3 blocks
==15990==   total heap usage: 3 allocs, 0 frees, 72,738 bytes allocated
==15990==
==15990== 4 bytes in 1 blocks are definitely lost in loss record 1 of 3
==15990==    at 0x48457AC: operator new(unsigned long) (vg_replace_malloc.c:344)
==15990==    by 0x40073B: getMemory() (valgrind.cpp:6)
==15990==    by 0x400757: main (valgrind.cpp:12)
==15990==
==15990== 30 bytes in 1 blocks are definitely lost in loss record 2 of 3
==15990==    at 0x4845178: malloc (vg_replace_malloc.c:309)
==15990==    by 0x40072F: getMemory() (valgrind.cpp:5)
==15990==    by 0x400757: main (valgrind.cpp:12)
==15990==
==15990== 72,704 bytes in 1 blocks are still reachable in loss record 3 of 3
==15990==    at 0x4845178: malloc (vg_replace_malloc.c:309)
==15990==    by 0x490C95B: ??? (in /usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.21)
==15990==    by 0x400DB5F: call_init.part.0 (dl-init.c:72)
==15990==    by 0x400DCA7: call_init (dl-init.c:30)
==15990==    by 0x400DCA7: _dl_init (dl-init.c:120)
==15990==    by 0x4000D43: ??? (in /lib/aarch64-linux-gnu/ld-2.23.so)
==15990==
==15990== LEAK SUMMARY:
==15990==    definitely lost: 34 bytes in 2 blocks
==15990==    indirectly lost: 0 bytes in 0 blocks
==15990==      possibly lost: 0 bytes in 0 blocks
==15990==    still reachable: 72,704 bytes in 1 blocks
==15990==         suppressed: 0 bytes in 0 blocks
==15990==
==15990== For lists of detected and suppressed errors, rerun with: -s
==15990== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)

参数说明：

--tool=memcheck //使用valgrind的memcheck功能，默认就是这个工具

-show-reachable=yes //是否检测控制范围之外的泄漏，比如全局指针、static指针等(分配了的内存,但它的指针没有丢失)

--log-file=a.log //结果输出到文件

--leak-check=yes //显示具体代码中泄漏的地方