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.
+2
A:
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.
Manuel
2009-01-05 15:50:44
Expensive yes. It paid back in one weekend, just using the profiler piece.
EvilTeach
2009-01-05 20:16:41
+2
A:
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.
Patrick Cuff
2009-01-05 15:53:58
A:
Perhaps CodeSnitch would be something you're after? http://www.entrek.com/codesnitch.html
Alex Fort
2009-01-05 15:56:00
+1
A:
I've been loving Memory Validator, from a company called Software Verification.
stevex
2009-01-05 15:58:22
+9
A:
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
dmityugov
2009-01-05 16:40:50
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.
2009-04-09 10:33:56
It works correctly for me, pointing the right line even new/delete are used.
Rodrigo
2009-04-22 18:33:56
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.
C Johnson
2010-08-09 15:11:33
Purify: venerable but still useful, as shown by how many changes of corporate ownership it has survived!
Norman Ramsey
2009-01-05 17:48:43
Insure++ takes forever to instrument your code, and forever to execute your code at runtime.
C Johnson
2010-08-09 15:12:16
+5
A:
There is Pageheap.exe part of the debugging tools for Windows. It's free and is basically a custom memory allocator/deallocator.
pspda5id
2009-04-09 05:37:22
Pageheap/gflags have helped me get to the bottom of some nasty heap corruption problems.
the_mandrill
2010-06-23 10:51:02
A:
If you are developing with Borland/CodeGear/Embarcadero C++ Builder, you could use CodeGuard.
Vince
2009-07-15 22:04:30
+4
A:
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://dmoulding.googlepages.com/vld.
tgs_stdio
2009-08-30 13:16:23
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. :-|
Synetech inc.
2010-08-25 00:18:02
+3
A:
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
Dan Kegel
2010-01-31 19:41:39
I'll install linux and valgrind and wine and recompile my whole project in wine, that REALLY make sense
Eric
2010-02-04 20:20:13
Because then you wouldn't be debugging a Windows app - you'd be debugging a Linux app.
John Dibling
2010-02-04 21:15:45
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.
Dan Kegel
2010-02-14 03:42:38
Exactly, its better to use the real thing than a lame clone :D Love valgrind.
mathepic
2010-10-21 20:23:07
A:
Does Jochen Kalmbach's Memory Leak Detector qualify?
PS: The URL to the latest version is buried somewhere in the article's comment thread.
Vulcan Eager
2010-03-03 09:42:00
+1
A:
LeakDiag, UMDH, App Verifier, DebugDiag, are all useful tools to improve robustness of code and find memory leaks.
Alex
2010-04-19 11:38:00
A:
If you're not afraid of mingw, here are some links (some might work with MSVC)... http://betterlogic.com/roger/?p=1140
rogerdpack
2010-08-09 14:15:51