Is there a good Valgrind substitute for Windows?

R

38

210

I was looking into Valgrind to help improve my C coding/debugging when I discovered it is only for Linux - I have no other need or interest in moving my OS to Linux so I was wondering if there is a equally good program for Windows.

Restrictive answered 5/1, 2009 at 15:37 Comment(2)

What kinds of debugging are you looking to do? Valgrind is quite a rich toolset, and the answers below point in all kinds of directions. With an emphasis on memory leak/allocation debugging. – Riarial 28/8, 2009 at 8:43

Maybe you can test the code on a virtual Linux machine inside your Windows, just when you need to check it. you can share the development folder between the virtual and non-virtual machine. that is, if the code is portable enough. – Cordellcorder 1/10, 2009 at 9:27

A

29

Some more good commercial tools:

Apprehension answered 5/1, 2009 at 17:19 Comment(2)

Purify: venerable but still useful, as shown by how many changes of corporate ownership it has survived! – True 5/1, 2009 at 17:48

Insure++ takes forever to instrument your code, and forever to execute your code at runtime. – Darees 9/8, 2010 at 15:12

D

117

As jakobengblom2 pointed out, valgrind has a suit of tools. Depending which one you are talking about there are different windows counter parts. I will only mention OSS or free tools here.

1. MemCheck:

Dr. Memory. It is a relatively new tool, works very well on Windows 7. My favorite feature is that it groups the same leaks' allocation stacks in the report.

http://code.google.com/p/drmemory/

I have also used UMDH( http://support.microsoft.com/kb/268343 ) and found it quiet useful and easy to setup. It works from Win2000 to Win7.

AppVerifier is a must have swissknife for windows native code developers, its "memory" checker does similar job http://msdn.microsoft.com/en-us/library/dd371695%28v=vs.85%29.aspx

2. Callgrind:

My favorite is verysleepy ( http://www.codersnotes.com/sleepy ) It is tiny but very useful and easy to use.

If you need more features, AMD CodeAnalyst™ Performance Analyzer is free: http://developer.amd.com/documentation/videos/pages/introductiontoamdcodeanalystperformanceanalyzer.aspx

Windows Performance Analysis tools is free from Microsoft, not very easy to use but can get the job done if you are willing to spend the time. http://blogs.microsoft.co.il/blogs/sasha/archive/2008/03/15/xperf-windows-performance-toolkit.aspx Download: http://msdn.microsoft.com/en-us/performance/cc752957

3. Massif:

Similar(not quite exact match) free tools on windows are:

VMMap from sysinternals : http://technet.microsoft.com/en-us/sysinternals/dd535533

!heap command in windbg : http://hacksoflife.blogspot.com/2009/06/heap-debugging-memoryresource-leak-with.html

4. Cachegrind:

Above mentioned Windows Performance Tools has certain level of L2 cache miss profiling capability but not quite as good and easy to use as Cachegrind.

5. DRD:

Haven't found anything free and as powerful on Windows yet, the only free tool for windows I can find that is slightly close is the "lock" checker in AppVerifier: http://msdn.microsoft.com/en-us/library/dd371695%28v=vs.85%29.aspx

Dentalium answered 5/7, 2011 at 9:13 Comment(1)

There's also gperftools (formerly Google PerfTools). It's not a valgrind replacement (what is really) but it has a new malloc, cpu profiler, heap profiler and checker. Worth a look as it's support on Linux and Windows (inc Mingw) and other unices. – Synchronize 13/2, 2012 at 17:29

F

31

Why not use Valgrind + Wine to debug your Windows app? See http://wiki.winehq.org/Wine_and_Valgrind

(Chromium uses this to check the Windows version for memory errors; see build.chromium.org and look at the experimental or memory waterfalls, and search for wine.)

There's also Dr. Memory, see dynamorio.org/drmemory.html

Fructificative answered 31/1, 2010 at 19:41 Comment(2)

Because then you wouldn't be debugging a Windows app - you'd be debugging a Linux app. – Culhert 4/2, 2010 at 21:15

No need to recompile in Wine. Just transfer your .exe and .pdb over to a Linux box. And you wouldn't be debugging a Linux app; you're debugging your exact Windows app. – Fructificative 14/2, 2010 at 3:42

A

29

Some more good commercial tools:

Apprehension answered 5/1, 2009 at 17:19 Comment(2)

Purify: venerable but still useful, as shown by how many changes of corporate ownership it has survived! – True 5/1, 2009 at 17:48

Insure++ takes forever to instrument your code, and forever to execute your code at runtime. – Darees 9/8, 2010 at 15:12

H

15

For Visual C++, try Visual Leak Detector. When I used it, it detected a memory leak from a new call and returned the actual line in source code of the leak. The latest release can be found at http://vld.codeplex.com/.

Hutchings answered 30/8, 2009 at 13:16 Comment(2)

It does not seem to work for me. I even tried creating a simple project that did basically nothing other than to allocated some memory and not free it. VLD did not detect it. :-| – Corinecorinna 25/8, 2010 at 0:18

@Corinecorinna inc. I had the same problem in VS2010... Using the newest version of VLD solved my problem – Argilliferous 7/4, 2011 at 16:46

F

14

Development environment for Windows you are using may contain its own tools. Visual Studio, for example, lets you detect and isolate memory leaks in your programs

Fluoridate answered 5/1, 2009 at 16:40 Comment(6)

It is of very little practical use. It will log the filename/linenumber for offending allocations, but it's only informative if you call malloc directly. When using new/delete, it will unhelpfully pinpoint new.h as the "offending" code. – Ticino 9/4, 2009 at 10:33

It works correctly for me, pointing the right line even new/delete are used. – Recline 22/4, 2009 at 18:33

But will it work if a library function allocates? E.g. strdup. – Tricksy 14/12, 2009 at 6:21

The Debug CRT, which is what you are trying to describe is useful for C code. Getting it to work for C++ code is more problematic. – Darees 9/8, 2010 at 15:11

Valdrind does a lot more then find memory leaks, I mainly use it to find use of freed and uninitialized stack and heap memory which can be incredibly hard to debug otherwise. – Distil 10/8, 2011 at 9:28

@Ticino Visual Leak Detector (vld.codeplex.com) provide full callstack for each memory leak with minimal souce code changes. Check example on site – Southwester 19/4, 2012 at 22:59

N

14

i would like to list some tool , hope will be useful

read this article for more detail

Purify
Bounds Checker
Coverity (basically its a code analyzer but, it will catch memory leak in static )
Glow Code
dmalloc
ccmalloc
NJAMD
YAMD
Valgrind
mpatrol
Insure++

Nanice answered 1/10, 2009 at 13:59 Comment(0)

F

13

Try DUMA

Farwell answered 28/8, 2009 at 1:16 Comment(0)

I

12

There is Pageheap.exe part of the debugging tools for Windows. It's free and is basically a custom memory allocator/deallocator.

See http://support.microsoft.com/kb/286470

Ingunna answered 9/4, 2009 at 5:37 Comment(2)

Pageheap/gflags have helped me get to the bottom of some nasty heap corruption problems. – Cassidy 23/6, 2010 at 10:51

I found gflags + gdb (from mingw) helpful in diagnosis. – Advocate 30/10, 2012 at 21:5

I

8

In combination with Visual Studio I generally use Visual Leak Detector or simply _CrtDumpMemoryLeaks() which is a win32 api call. Both are nothing fancy but they get the job done.

Illdisposed answered 1/10, 2009 at 9:45 Comment(0)

J

6

I had the chance to use Compuware DevPartner Studio in the past and that was really good, but it's quite expensive. A cheaper solution could be GlowCode, i just worked with a 5.x version and, despite some problems in attaching to a process i needed to debug, it worked quite well.

Jubilee answered 5/1, 2009 at 15:50 Comment(1)

Expensive yes. It paid back in one weekend, just using the profiler piece. – Willumsen 5/1, 2009 at 20:16

R

6

I've been loving Memory Validator, from a company called Software Verification.

Rubi answered 5/1, 2009 at 15:58 Comment(0)

K

5

Viusual Studio can help detecting memory leaks itself. See Microsoft Visual C++ Tips and Tricks -> "Memory Leaks" section. See also this post in SO

Although real tracing is only possible with the Team Edtion of Visual Studio.

Koblick answered 1/10, 2009 at 9:16 Comment(0)

R

4

See the "Source Test Tools" link on the Software QA Testing and Test Tool Resources page for a list of similar tools.

I've used BoundsChecker,DevPartner Studio and Intel V-Tune in the past for profiling. I liked V-Tune the best; you could emulate various Intel chipsets and it would give you hints on how to optimize for that platform.

Runin answered 5/1, 2009 at 15:53 Comment(0)

C

3

How about the Purify?

Cultured answered 1/10, 2009 at 9:4 Comment(2)

Not really free... but I guess you could find a test license for testing purposes. – Inhume 1/10, 2009 at 9:7

Dead link as of 2011-02-04 for BoundsChecker. – Forbade 4/2, 2011 at 22:15

S

3

Does Jochen Kalmbach's Memory Leak Detector qualify?

PS: The URL to the latest version is buried somewhere in the article's comment thread.

Smythe answered 3/3, 2010 at 9:42 Comment(0)

T

3

LeakDiag, UMDH, App Verifier, DebugDiag, are all useful tools to improve robustness of code and find memory leaks.

Tricksy answered 19/4, 2010 at 11:38 Comment(0)

V

3

The Boost Test library can detect memory leaks.

Vanadium answered 2/7, 2010 at 7:8 Comment(0)

C

3

Try Intel's Inspector XE product which can help you detect both memory and threading issues: http://software.intel.com/en-us/articles/intel-inspector-xe/

Cargian answered 21/2, 2012 at 19:57 Comment(0)

F

2

Perhaps CodeSnitch would be something you're after? http://www.entrek.com/codesnitch.html

Freiman answered 5/1, 2009 at 15:56 Comment(0)

A

2

If you are developing with Borland/CodeGear/Embarcadero C++ Builder, you could use CodeGuard.

Achlamydeous answered 15/7, 2009 at 22:4 Comment(0)

C

2

More or less all Profilers include checking for memory leaks and show you the stack when the memory was allocated.

I can recommend Intels Parallel Inspector. Simple to use and no recompilation needed. The trial version runs for 30 days.

GlowCode and AtromatedQA also include such capabilites. They all offer free trials.

Compuware DevPartner (aka BoundsChecker) in Contrast needs a slowed down "instrumentation" recompile and the application also runs slower when checking for errors. And BoundsChecker can not work with 64 Bit evsrions at all. We gave up on that tool.

Currey answered 1/10, 2009 at 9:32 Comment(2)

I'd defintitely recommend glowcode. I've used it in the past to find an memory leak within a dll being called by my app. – Superorder 1/10, 2009 at 9:35

There were complaints of major slowdowns while using DevPartner at my last workplace. They do everything to avoid using it because of how slow it would be. – Addieaddiego 1/10, 2009 at 12:44

C

2

The best tool I ever used is DevPartner BoundsChecker - it's not free but it has an evaluation period.

Cockatrice answered 1/10, 2009 at 10:23 Comment(0)

C

2

Another memory tool for your list: Memory Validator.

Not free, but nowhere near as expensive as Purify or Boundschecker.

Committeewoman answered 2/4, 2010 at 13:57 Comment(0)

R

2

If you're not afraid of mingw, here are some links (some might work with MSVC)... http://betterlogic.com/roger/?p=1140

Repeat answered 9/8, 2010 at 14:15 Comment(0)

C

2

We are just completing a Memory Safety checking tool for Windows, that handles GCC and Micrsoft Visual C (not C++ yet), and are looking for Beta testers.

EDIT June 12, 2011: Not Beta anymore, now production for GCC and Microsoft Visual Studio C.

Cato answered 6/4, 2011 at 10:56 Comment(0)

S

2

I found this SF project today:

http://sourceforge.net/p/valgrind4win/wiki/Home/

They are porting valgrind to Windows. Probably in several years we will have a reliable valgrind on windows.

Sportswear answered 5/6, 2012 at 9:17 Comment(0)

P

1

Check out this question: Is there a good Valgrind substitute for Windows? . Though general substitute for valgrind is asked, it mainly discusses memory leak detectors and not race conditions detections.

Patagium answered 1/10, 2009 at 9:7 Comment(0)

F

1

Definitely Purify! I've used that to analyze some massive code bases (>3,000 kSLOC) and found it to be excellent.

You might like to look at this list at Wikipedia.

By the way, I've found memwatch to be useful. Thanks Johan!

Farrica answered 1/10, 2009 at 9:11 Comment(0)

P

1

I used Insure++ which does excellent job in finding c++ memory leaks/corruptions and many other bugs like uninitialized variables, pointer errors, strings etc., It also does visual "Code coverage" and run time memory usage etc.. which give more confident on your code.. You can try it for trail version..

Peckham answered 1/10, 2009 at 9:42 Comment(0)

R

1

You might want to read what Mozilla is doing regarding memory leaks. One tool in their toolbox is the Hans Boehm garbage collector used as memory leak detector.

Roughandready answered 1/10, 2009 at 11:41 Comment(0)

T

1

You can give a try to RuntimeChecker trial ot to IBM Purify trial..

A free solution would be to use the following code in Visual Studio:

#ifdef _DEBUG
#define new DEBUG_NEW
#endif

Just write this in the top of all your cpp files. This will detect memory leaks of your application whenc stopping debug run and list them in the output window. Double clicking on a memory leaks line will higlight you the line where memory is allocated and never released. This may help you : http://www.flipcode.com/archives/How_To_Find_Memory_Leaks.shtml

Twinge answered 1/10, 2009 at 12:15 Comment(0)

P

1

The user-mode dump heap (UMDH) utility works with the operating system to analyze Windows heap allocations for a specific process. That's a pretty good tool for free from Microsoft. Here is a mini tutorial "How to use Umdh.exe to find memory leaks".

Phloem answered 1/10, 2009 at 18:20 Comment(0)

Y

1

The free tool DebugDiag will help find memory and handle leaks.

You don't need to augument your program for DebugDiag to work.

http://www.microsoft.com/downloads/details.aspx?FamilyID=28BD5941-C458-46F1-B24D-F60151D875A3&displaylang=en

Although it is not the easiest or most intuitive program to use! Make sure you google for tutorials and instructions on how to use it.

Yahrzeit answered 15/3, 2010 at 10:36 Comment(0)

T

1

You can take a look to the article Design and Implementation of an In-Game Memory Profiler in the book "Game Programming Gems 8".

It shows how to implement a low overhead semi-intrusive real-time memory profiler, source code provided in the CD-ROM.

enter image description here

Transudation answered 21/7, 2011 at 3:33 Comment(0)

B

1

Clang supports the Address Sanitizer plugin (-faddress-sanitizer option), which can pretty much detect most bugs that Valgrind can find (does not support detection of uninitialised memory reads and memory leaks yet though). See this page for a comparison against Valgrind and other similar tools. An official Windows port is currently in progress, see Windows ASan port.

I attempted to build it myself on Windows a couple of months ago and gave up, see my related question. Things may have changed for the better now if you want to give it another go.

Benzyl answered 24/9, 2012 at 0:32 Comment(0)

R

0

Just an idea, you could also implement a memory allocator and track all calls to malloc and free. However this might be too much for some projects.

Radiobiology answered 6/2, 2011 at 16:58 Comment(1)

That's how most games do it. But it's a huge undertaking and a lot of instrumentation. – Gideon 29/11, 2011 at 8:59

M

0

Parasoft Insure++ has always been reliable:

http://www.parasoft.com/jsp/products/insure.jsp?itemId=63

Mayday answered 5/4, 2011 at 20:31 Comment(0)

D

0

Finding Memory leak in C++ Application on Windows

Dynamite answered 9/8, 2012 at 11:25 Comment(0)

Recommended topics

Hot tags