Detect Memory Corruption in Windows

Why not just run your app under the debugger in Visual Studio? When an exception occurs, the debugger will point to the line that faulted.

If you really want to use windbg, see here: http://windbg.info/doc/1-common-cmds.html[^]

There are two ways the way I see it. Run all your code through a debugger. Getting 100% code coverage is close to impossible, unless your code is fully test-driven. The other way is to set up code review with a couple of experienced programmers. My experience is that you can find error patterns, and identify not only problematic code, but also problematic programmers, guiding you to the hot spots that needs validation.
Edit: If you have a lot of code to go through, getting a static code anlysis software might be of great help.

There is no real panacea for finding memory corruptions, your best bet is to try to avoid 'raw' pointers

- Use stl containers to hold lists (vector, list etc)
- Wrap pointer use inside a class, and have check code all thru it, at least in debug (CString etc)
- Code reviews and test units

The debug libraries will do some work to find you exceeding your memory block, but they won't catch them all

Interestingly, the example you've quoted is not a memory corruption, it's you free'ing memory that hasn't been allocated

There are a couple of tools that track down code which is problematic with regard to memory corruption or similar, both at compile time, and at run time. I am using a commercial one which is quite good, but I've found it slows down both compilation and run time behaviour by an order of magnitude at least.

There are a few articles on this topic as well, try out any of these links:
Memory Leak detection in .NET
Windows Memory leak detection
Visual Leak Detector

You could also start windbg and look at the help file that comes with it. There is a lot of good information in there.

Or from a command prompt in the directory containing windbg, just type windbg /?

Hope that helps.