When writing software even the most experienced coder will create errors in the program. You want to be able to find and fix errors as quickly as possible. It would even be beneficial to do it during the development phase rather than waiting until later. Code syntax errors are easy to find because most of the time the compiler tells you what and where they are so you can fix them easily. But what about logical errors? How do you track down and fix errors that compile but aren't apparent yet until you run your program? Is there a better way to do it instead of using just log files and printfs all over your program? Well there is and we will explore what the latest versions of Visual Studio provide for us.

There are a few slides regarding detecting memory leaks using the Microsoft C run-time libraries.

Intended Audience: Beginner C/C++ developer with little or no experience working with the Visual Studio debugger. Knowledge of using the Visual Studio IDE is preferred. IDEs applicable are .NET 2003 and 2005.

I used to give this powerpoint presentation as a live event at the Game Institute. The information presented can be used however you want. If you're comfortable with using debugger present in Visual Studio or if you are using a different debugger altogether then this presentation is not for you.

Download (Power point slides converted to .pdf)