(十三)valgrind在ARM上交叉编译和内存泄漏检测

最新推荐文章于 2024-07-25 15:50:18 发布
最新推荐文章于 2024-07-25 15:50:18 发布
阅读量2.1k 收藏 11
点赞数 1
分类专栏： 系统工具总结 文章标签： arm arm开发 linux
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_23123181/article/details/125165608
版权

valgrind是一款用于内存调试、内存泄漏检测以及性能分析的软件开发工具。

1、下载valgrind-3.17.0

2、交叉编译

修改configure： armv7*) 改成 armv7*|arm)

./configure --host=aarch64-linux  \
CC=/gzy_mnt/aarch64-linux-gds/bin/aarch64-linux-gnu-gcc  \
CPP=/gzy_mnt/aarch64-linux-gds/bin/aarch64-linux-gnu-cpp \
CXX=/gzy_mnt/aarch64-linux-gds/bin/aarch64-linux-gnu-g++ \
--prefix=/gzy_mnt/valgrind

然后进行make -j8编译和安装make install。

/gzy_mnt/valgrind目录下生成好的bin、include、lib、libexec、share目录

3、运行

/gzy_mnt是挂载在arm板子上的共享目录。我们对NanoDet的MNN进行内存泄露检测。在目录/gzy_mnt/valgrind下执行：

./valgrind --leak-check=full /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection /gzy_mnt/club

Memcheck是默认工具。--leak-check选项打开详细的内存泄漏检测器。程序运行速度会比正常情况慢很多，并且会占用更多内存。Memcheck将发出有关内存错误和检测到的泄漏的消息。格式如下:

valgrind toolparamters appname appargs

一开始是valgrind信息“==2130==”表示进程号

==2130== Memcheck, a memory error detector
==2130== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2130== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info
==2130== Command: /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection /gzy_mnt/club
==2130==

程序访问非法地址的内存，无效写入

==2130== Invalid write of size 8
==2130== at 0x6806FE0: ??? (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== Address 0x1fff000360 is on thread 1's stack
==2130== 16 bytes below stack pointer
==2130==
==2130== Invalid read of size 8
==2130== at 0x68077F0: ??? (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== Address 0x1fff000360 is on thread 1's stack
==2130== 16 bytes below stack pointer
==2130==
==2130== Invalid write of size 8
==2130== at 0x6807920: ??? (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== Address 0x1fff000360 is on thread 1's stack
==2130== 16 bytes below stack pointer
==2130==
==2130== Invalid write of size 8
==2130== at 0x6807924: ??? (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== Address 0x1fff000350 is on thread 1's stack
==2130== 32 bytes below stack pointer
==2130==
==2130== Invalid write of size 8
==2130== at 0x6807928: ??? (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== Address 0x1fff000340 is on thread 1's stack
==2130== 48 bytes below stack pointer
==2130==
==2130== Invalid write of size 8
==2130== at 0x680792C: ??? (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== Address 0x1fff000330 is on thread 1's stack
==2130== 64 bytes below stack pointer
==2130==
==2130== Invalid read of size 8
==2130== at 0x6807DE0: ??? (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== Address 0x1fff000360 is on thread 1's stack
==2130== 16 bytes below stack pointer
==2130==
==2130== Invalid read of size 8
==2130== at 0x6807DE4: ??? (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== Address 0x1fff000350 is on thread 1's stack
==2130== 32 bytes below stack pointer
==2130==
==2130== Invalid read of size 8
==2130== at 0x6807DE8: ??? (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== Address 0x1fff000340 is on thread 1's stack
==2130== 48 bytes below stack pointer
==2130==
==2130== Invalid read of size 8
==2130== at 0x6807DEC: ??? (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== Address 0x1fff000330 is on thread 1's stack
==2130== 64 bytes below stack pointer
==2130==

堆区情况:

==2130== HEAP SUMMARY:
==2130== in use at exit: 56,224 bytes in 658 blocks
==2130== total heap usage: 59,896 allocs, 59,238 frees, 27,306,731 bytes allocated
==2130==
==2130== 608 (144 direct, 464 indirect) bytes in 2 blocks are definitely lost in loss record 409 of 422
==2130== at 0x48497E0: operator new(unsigned long) (vg_replace_malloc.c:417)
==2130== by 0x66EC66F: MNN::Tensor::create(std::vector<int, std::allocator > const&, halide_type_t, void*, MNN::Tensor::DimensionType) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F2C27: MNN::CV::ImageProcess::createImageTensor(halide_type_t, int, int, int, void*) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F2CCF: MNN::CV::ImageProcess::convert(unsigned char const*, int, int, int, void*, int, int, int, int, halide_type_t) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F323B: MNN::CV::ImageProcess::convert(unsigned char const*, int, int, int, MNN::Tensor*) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x418BEB: NanoDet::detect(cv::Mat&, std::vector<BoxInfo, std::allocator >&) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x40CFE7: golf::GolfDetection::globalRun(cv::Mat, std::__cxx11::basic_string<char, std::char_traits, std::allocator >) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x41B2BB: image_demo_union(golf::GolfDetection&, golf::GolfDetection&, char const*) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x406D13: main (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130==
==2130== 608 (144 direct, 464 indirect) bytes in 2 blocks are definitely lost in loss record 410 of 422
==2130== at 0x48497E0: operator new(unsigned long) (vg_replace_malloc.c:417)
==2130== by 0x66EC66F: MNN::Tensor::create(std::vector<int, std::allocator > const&, halide_type_t, void*, MNN::Tensor::DimensionType) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F2C27: MNN::CV::ImageProcess::createImageTensor(halide_type_t, int, int, int, void*) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F2CF3: MNN::CV::ImageProcess::convert(unsigned char const*, int, int, int, void*, int, int, int, int, halide_type_t) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F323B: MNN::CV::ImageProcess::convert(unsigned char const*, int, int, int, MNN::Tensor*) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x418BEB: NanoDet::detect(cv::Mat&, std::vector<BoxInfo, std::allocator >&) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x40CFE7: golf::GolfDetection::globalRun(cv::Mat, std::__cxx11::basic_string<char, std::char_traits, std::allocator >) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x41B2BB: image_demo_union(golf::GolfDetection&, golf::GolfDetection&, char const*) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x406D13: main (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130==
==2130== 608 (144 direct, 464 indirect) bytes in 2 blocks are definitely lost in loss record 411 of 422
==2130== at 0x48497E0: operator new(unsigned long) (vg_replace_malloc.c:417)
==2130== by 0x66EC66F: MNN::Tensor::create(std::vector<int, std::allocator > const&, halide_type_t, void*, MNN::Tensor::DimensionType) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F2C27: MNN::CV::ImageProcess::createImageTensor(halide_type_t, int, int, int, void*) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F2CCF: MNN::CV::ImageProcess::convert(unsigned char const*, int, int, int, void*, int, int, int, int, halide_type_t) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F323B: MNN::CV::ImageProcess::convert(unsigned char const*, int, int, int, MNN::Tensor*) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x418BEB: NanoDet::detect(cv::Mat&, std::vector<BoxInfo, std::allocator >&) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x40D463: golf::GolfDetection::localBallRun(cv::Mat, float, float, ShootType, std::__cxx11::basic_string<char, std::char_traits, std::allocator >) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x41B59B: image_demo_union(golf::GolfDetection&, golf::GolfDetection&, char const*) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x406D13: main (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130==
==2130== 608 (144 direct, 464 indirect) bytes in 2 blocks are definitely lost in loss record 412 of 422
==2130== at 0x48497E0: operator new(unsigned long) (vg_replace_malloc.c:417)
==2130== by 0x66EC66F: MNN::Tensor::create(std::vector<int, std::allocator > const&, halide_type_t, void*, MNN::Tensor::DimensionType) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F2C27: MNN::CV::ImageProcess::createImageTensor(halide_type_t, int, int, int, void*) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F2CF3: MNN::CV::ImageProcess::convert(unsigned char const*, int, int, int, void*, int, int, int, int, halide_type_t) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66F323B: MNN::CV::ImageProcess::convert(unsigned char const*, int, int, int, MNN::Tensor*) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x418BEB: NanoDet::detect(cv::Mat&, std::vector<BoxInfo, std::allocator >&) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x40D463: golf::GolfDetection::localBallRun(cv::Mat, float, float, ShootType, std::__cxx11::basic_string<char, std::char_traits, std::allocator >) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x41B59B: image_demo_union(golf::GolfDetection&, golf::GolfDetection&, char const*) (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130== by 0x406D13: main (in /gzy_mnt/gdsplusv2/demo/clublocal/golfDetection)
==2130==
==2130== 912 bytes in 3 blocks are possibly lost in loss record 415 of 422
==2130== at 0x484E024: calloc (vg_replace_malloc.c:1117)
==2130== by 0x400FA8F: allocate_dtv (in /lib/ld-2.28.so)
==2130== by 0x4010347: _dl_allocate_tls (in /lib/ld-2.28.so)
==2130== by 0x48720FB: pthread_create@@GLIBC_2.17 (in /lib/libpthread-2.28.so)
==2130== by 0x697D863: std:thread:_M_start_thread(std::unique_ptr<std:thread:_State, std::default_deletestd:thread:_State >, void (*)()) (in /lib/libstdc++.so.6.0.25)
==2130== by 0x67D0CF3: MNN::ThreadPool::ThreadPool(int) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x67D0F37: MNN::ThreadPool::init(int) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x67805DB: MNN::CPURuntime::CPURuntime(MNN::Backend::Info const&) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x6780733: MNN::CPURuntimeCreator::onCreate(MNN::Backend::Info const&) const (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66E277F: MNN::RuntimeFactory::create(MNN::Backend::Info const&) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66D5DBB: MNN::Interpreter::createRuntime(std::vector<MNN::ScheduleConfig, std::allocatorMNN::ScheduleConfig > const&) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130== by 0x66D6E53: MNN::Interpreter::createMultiPathSession(std::vector<MNN::ScheduleConfig, std::allocatorMNN::ScheduleConfig > const&) (in /gzy_mnt/gdsplusv2/lib/libMNN.so)
==2130==

内存泄漏消息如下所示：有几种泄漏; 两个最重要的类别是，肯定泄露（definitely lost），可能已经泄露（possibly lost）

==2130== LEAK SUMMARY:
==2130== definitely lost: 576 bytes in 8 blocks
==2130== indirectly lost: 1,856 bytes in 16 blocks
==2130== possibly lost: 912 bytes in 3 blocks
==2130== still reachable: 52,880 bytes in 631 blocks
==2130== suppressed: 0 bytes in 0 blocks
==2130== Reachable blocks (those to which a pointer was found) are not shown.
==2130== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==2130==
==2130== For lists of detected and suppressed errors, rerun with: -s
==2130== ERROR SUMMARY: 228733 errors from 15 contexts (suppressed: 0 from 0)

MNN在1.2.0版本有严重内存泄漏，在1.2.9版本进行测试，MNN修复部分问题，例如在ImageProcess转化的内存泄漏已经修改掉。

详细见：严重内存泄漏 · Issue #1018 · alibaba/MNN · GitHub

li三河
关注
  • 1
    点赞
  • 踩
  • 11
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Valgrind ARM(aarch64) 交叉编译、移植与使用
HZHejo的博客
05-10 3864
Valgrind是一款用于内存调试、内存泄漏检测以及性能分析、检测线程错误的软件开发工具。 Valgrind 是运行在Linux 上的多用途代码剖析和内存调试软件。主要包括Memcheck、Callgrind、Cachegrind 等工具，每个工具都能完成一项任务调试、检测或分析。可以检测内存泄露、线程违例和Cache 的使用等。Valgrind 基于仿真方式对程序进行调试，它先于应用程序获取实际处理器的控制权，并在实际处理器的基础上仿真一个虚拟处理器，并使应用程序运行于这......
valgrind工具的交叉编译及使用
qq_34744658的博客
06-19 505
valgrind在arm上的交叉编译和使用方法
内存泄漏检测工具Valgrind交叉编译
mrhjlong
11-20 402
内存泄漏检测工具Valgrind交叉编译。
arm linux下交叉编译valgrind工具进行内存泄露检测和性能分析
Audio and Video Development
06-23 7707
C/C++等底层语言在提供强大功能及性能的同时，其灵活的内存访问也带来了各种纠结的问题。如果crash的地方正是内存使用错误的地方，说明你人品好。如果crash的地方内存明显不是consistent的，或者内存管理信息都已被破坏，编译器不能发现这些问题，.运行时才能捕获到这些错误并且还是随机出现的，那就比较麻烦了。当然，祼看code打log是一个办法，但其效率不是太高，尤其是在运行成本高或重现概率
valgrind简介以及在ARM上交叉编译运行
蠢萌
04-19 8443
valgrind简介以及在ARM上交叉编译运行参考博客：https://blog.csdn.net/dengcanjun6/article/details/54958359参考博客：https://blog.csdn.net/longbei9029/article/details/78626004?locationNum=1&amp;fps=1参考博客：https://blog.csdn.net/...
内存泄漏，valgrind移植到arm64的完整记录
weixin_42163707的博客
09-02 912
嵌入式平台中内存泄漏的查找
valgrind交叉编译，检测内存泄漏、越界访问、野指针访问实验
sun007700的专栏
12-20 481
【代码】valgrind检测内存泄漏、越界访问、野指针访问实验。
交叉编译Valgrind
Reasonss的博客
12-15 1437
交叉编译Valgrind 参考https://blog.csdn.net/qq_34743935/article/details/105682653 参考https://www.valgrind.org/downloads/ 1.Valgrind 1.1 下载valgrind 官网 http://valgrind.org/downloads/ 下载源码包 tar xvf valgrind-3.15.0.tar.bz2 cd valgrind-3.15.0 apt-get install automa
LED照明
汽车以太网和SOA
02-15 4105
LED照明
HarmonyOS和OpenHarmony区别联系
Jason_Lee155的博客
07-23 776
刚开始接触鸿蒙开发的时候经常看到HarmonyOS和OpenHarmony频繁的出现在文章和文档之中，那么这两个名词分别是什么意思，他们之间又有什么联系呢？
OpenHarmony 开发
简简单单Onlinezuozuo
07-23 188
OpenHarmony 对于所有中国开发者而言，可谓是非常熟悉。据官方数据统计，截至 2024 年 6 月 30 日，OpenHarmony 社区已经累计超过 7900 名贡献者，共 70 家共建单位，产生 37 万多个 PR ，2.6 万多个 Star ，8.3 万多个 Fork ，59 个 SIG。
Linux初学基本命令
最新发布
yuan20010401的博客
07-25 285
1、rm 文件名称 删除多个文件多个目录需要用空格 删除根目录（rm -rf /*）1、touch 文件名字 用于linux创建文件 创建多个目录需要用空格隔开。2、mkdir 目录名称 用于创建文件夹 创建多个嵌套文件夹需要用/隔开。1、cp 当前文件 其他目录名称 拷贝文件夹需要在最后 -r。退出不保存时按Esc+:q!1、ls 查看当前目录下面的文件或者文件夹。2、more 文件名称 查看文件更多内容。1、mv 原文件路径 目标文件路径。退出保存时按Esc + :wq。
Linux 常用命令分类及示例
简介
07-25 833
【代码】Linux 常用命令分类及示例。
2024-07-24 Linux C語言使用inotify进行文件变化检测
海月汐辰
07-24 335
inotify。
记一次Linux应急响应全过程
无问社区的博客
07-24 461
本文来源无问社区，更多实战内容，渗透思路尽在无问社区场景说明：某客户的应用服务器对外开放22、80、8080端口。2021年3月28日，运维收到主机CPU性能告警，且通过流量设备监测到主机有外联矿池的行为。请对被入侵主机进行应急分析，还原完整攻击场景。
linux上导出数据库
weixin_43652507的博客
07-24 315
linux上导出数据库 MySQL、PostgreSQL、SQLite、MongoDB
【Linux】一些基本指令
weixin_73914025的博客
07-25 756
在学习操作系统的时候，我们应该要清楚操作系统是什么。操作系统是一款进行软硬件资源管理的软件。如果没有操作系统，即使是有一台好的电脑配有一套好的鼠标和键盘，我们也无法使用这台电脑。所以我们也就知道了为什么要进行软硬件资源管理，目的就是为我们使用机器提供了良好的服务。我们在《Linux的环境搭配中》提到了云服务器的使用，为了方便学习，我在Linux的学习中，将会使用云服务器来进行学习。在上面提到的那片文章中，我们提到了Xshell，我们在每次打开Xshellssh (用户名)@(公网IP)
Linux-管道与输入输出重定向
weixin_57370131的博客
07-24 248
【代码】Linux-管道与输入输出重定向。
valgrind在arm-linux上交叉编译
10-08
在ARM-Linux上交叉编译Valgrind需要以下步骤： 1. 获取Valgrind源代码：首先，你需要从Valgrind的官方网站下载Valgrind的源代码包。 2. 安装交叉编译工具链：在你的开发机上安装适用于ARM架构的交叉编译工具链。这...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值