resource leakage detection on Windows

最新推荐文章于 2025-03-09 04:37:19 发布

masterz

最新推荐文章于 2025-03-09 04:37:19 发布

阅读量1.2k

点赞数

CC 4.0 BY-SA版权

分类专栏： VC++2010 Debug 文章标签： linker compiler parallel profiling microsoft windows

本文链接：https://blog.youkuaiyun.com/masterz/article/details/6398574

VC++2010 同时被 2 个专栏收录

13 篇文章

订阅专栏

Debug

1 篇文章

订阅专栏

本文探讨了在Windows XP SP3上使用VC++本机应用程序进行资源泄漏调查的方法。通过使用多种工具如Intel Parallel Inspector 2011、Valgrind等，作者详细记录了遇到的问题及解决方案。还介绍了如何设置Intel C++ Compiler进行代码覆盖率分析。

Time frame: May 2011

Subject: Investigate resource leakage of a VC++ native application on Windows XP SP3.

DevPartner 10.5 - cause debuggee crash due to 0x80080003. After disabling certain features so that it only logs memory leaks, the debuggee does not crash, but hang up at exit.

Purify 7.0.1 cause debuggee exit abnormally, no memory leakage found.

Intel Parallel Inspector 2011 can only work inside VC++ 2008, so I have to open a solution, then start error inspection, browse to my executable and run. It is a little bit slow, but it did found some resource leakages. Some of the leakage has call stack, file name and line number information, but others only show "unkown". The callstack depth is only 2.

Intel Parallel Composer 2011 provides a code coverage tool - profmerge and codecov.exe.

Steps: enable "Instrument for Code Coverage" in Project properties -> General -> Code Coverage Build Options

Compiler and Environment Settings: Intel C++ Compiler (icl.exe)

Run program with "Hotspots - Where is my program spending time?"

Open C:/WINDOWS/system32/cmd.exe /E:ON /K ""C:/Program Files/Intel/Parallel Studio 2011/ips-vars.cmd" ia32 vs2008"

generate pgopti.dpi by this command: G:/workspace/testvld2/Debug>profmerge

G:/workspace/testvld2/Debug>codecov -prj testvld2

Intel(R) C++ Compiler XE 12.0.2.154 [IA-32]... (Intel C++ Environment)

1>Linking... (Intel C++ Environment)

1>ipo: error #11018: Cannot open X:/server/Base/

1>xilink: executing 'link'

1>LINK : fatal error LNK1181: cannot open input file 'X:/server/Base/.obj'

This is due to empty value in Base project Linker -> Advanced -> Import Library (/IMPLIB linker option). Set the value as: $(TargetDir)$(TargetName).lib, then rebuild is successful.

Valgrind is able to do memory checking and profiling on Linux.

Memory Validator is not compatible with Visual Leak Detector. It also reported incorrect source code position when executable is not built with VLD.

Maybe next time I'll try Microsoft tools if none of the above is working well.

Umdhtools.exe: How to use Umdh.exe to find memory leaks

Memory Leak Detection Using Windbg By Mayank Rai

Q177415 How to use Memory Pool Monitor (Poolmon.exe) to troubleshoot kernel mode memory leaks

Detect and Plug GDI Leaks in Your Code with Two Powerful Tools for Windows XP by Christophe Nasarre