Click here to Skip to main content
12,078,742 members (49,572 online)
Click here to Skip to main content
Add your own
alternative version


309 bookmarked

10+ powerful debugging tricks with Visual Studio

, 18 Apr 2012 CPOL
Rate this:
Please Sign up or sign in to vote.
The article describes 10 sime-saving debugging techniques available in Visual Studio


Debugging is a major part of the development lifecycle. Sometimes challenging, sometimes puzzling, sometimes annoying, one for sure - it is unavoidable for any not-so-trivial program. The progress of debugging tools over the last years has made many debugging tasks much easier and less time-consuming.

This article summarizes ten debugging tricks and techniques that can save you a lot of time when using Visual Studio. 

1. Hover mouse to evaluate expression 


Debugging can be challenging. Stepping through a function to understand what went wrong, looking through the call stack to see where did that value come from... In either case adding watch expressions or looking through a list of locals can take quite a time. However, things get easier if you just point your mouse at a variable of interest. Moreover, classes and structures will be expanded with one click, allowing to find the field you need quickly and conveniently. 

2. Change values on-the-fly 

Debugger is much more than a tool for analyzing crashes and wierd behavior. Many bugs can be prevented by stepping through a freshly written function and checking that it behaves as expected. Sometimes you are curious "would the function behave correctly if this condition was true?". And in most cases it does not mean changing the code and restarting. Just hover the mouse over a variable, double-click at the value and type in the new one!

3. Set next statement


One typical debugging scenario is analyzing why does a function call fail by going through the function step-by-step. And what do you do when you've just discovered that a function called another function that returned an error? Restart debugging? There's a better idea: just drag the yellow statement marker to the line you want to be executed next, like the function that has just failed, and then simply step in. Simple, isn't it?

4. Edit and continue

Debugging a complex program, or a plugin? Found an error, but don't want to lose time stopping, rebuilding and restarting again and the function is called too often to use the previous trick each time? No problem, just fix the bug in-place and continue stepping. Visual Studio will modify your program and continue debugging with no need to restart.

Beware, though. Edit-and-continue has a bunch of known limitations. First, it won't work for 64-bit code. If it refuses to work for your C# app, go to project settings, Build page, then select "x86" as Platform Target. Don't worry, the Platform Target for the Release configuration is separate from the debug one and can still be "Any CPU".

Second, the edit-and-continue changes should be local, i.e. within one method. If you change the method signature, add new methods or classes, you'll have to restart the app, or undo the changes to continue. Changing methods containing lambda expressions implies modifying the auto-generated delegate classes and thus prevents continuing.

5. A convenient watch window 

Probably, every modern debugger has a watch window. However, what's really cool about the Visual Studio one is how easy you can add and remove variables there. Just click at the empty line, type your expression and press Enter. Or simply press delete button to remove an expression that is no longer needed. 

Moreover, the information you can get from the watch window is not limited to "normal" variables. You can enter $handles to track the amount of handles opened by your application (and find leaks easier), $err to see the error code of the last function (and then use Tools->Error Lookup to get a meaningful description), or @eax (@rax for 64-bit code) to see the register containing the return value of a function.

6. Annotated disassembly

Optimizing the performance of the critical parts of your program can be much easier using the interactive disassembly mode. Visual Studio shows you the instructions corresponding to every line of your code and allows running the code step-by-step, as well as setting breakpoints at arbitrary locations. And, of course, the expression evaluation and modification will work just like for the C++ code.

7. Threads window with stacks 

 Debugging multi-threaded applications can be painful. Or it can be fun. Depends on your debugger. One really nice feature of Visual Studio 2010 is the stack view in the threads window. You can get a convenient overview of all your threads and navigate through their call stacks directly from the window.

8. Conditional breakpoints


If you're trying to reproduce a rare event and getting too many false positives with your breakpoints, you can easily make them conditional! Simply specify the condition for a breakpoint and Visual Studio will automatically ignore the breakpoint when the condition does not hold.

9. Memory window


Some bugs are caused by incorrect structure definitions, missing alignment attributes, etc. Seeing the raw memory contents simplifies locating and fixing those bugs. Visual Studio features a convenient memory window that can interpret the values as 8/16/32/64-bit numbers, as well as floating-point numbers and allows changing them on-the-fly by simply typing the new values over the old ones like in a text editor. 

10. Go To Definition

 One last feature to mention is not directly related to debugging, rather to exploring big projects. If you are trying to find a bug in some code you have not written yourself, having a quick answer to "what is this type" or "what does this function do" can save you a lot of time. And Visual Studio does this with ease via the Go To Definition command.  

11. Command Window 

 This eleventh trick has been suggested by chaau and it can indeed save you a lot of time. Visual Studio supports a Command Window that can be activated through the View->Other Windows->Command Window menu. Once active, you can type various commands to automate the debugging. For example, you can easily evaluate an MFC COleDateTime variable by running a simple command:

? dt.Format("%Y-%m-%d %H:%M:%S")  


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Ivan Shcherbakov
Founder Sysprogs UG (haftungsbescrhänkt)
Germany Germany
Ivan Shcherbakov is a cofounder of the Sysprogs UG (haftungsbeschränkt), the company developing custom software, drivers and firmware and delivering VisualGDB - a Visual Studio plugin that allows using Visual Studio to build applications with GCC and debug them with GDB.

The main goal of VisualGDB is to combine the time-saving Visual Studio debugging experience with the wide application range of GDB, such as Linux applications and Embeddeed firmware.

A special Android Edition of VisualGDB allows building and debugging native Android code with Visual Studio easily and smoothly.

You may also be interested in...

Comments and Discussions

QuestionEdit and Continue Pin
asit4u1111-Apr-12 4:01
memberasit4u1111-Apr-12 4:01 
AnswerRe: Edit and Continue Pin
Ivan Shcherbakov18-Apr-12 22:09
memberIvan Shcherbakov18-Apr-12 22:09 
QuestionAttaboy! Pin
DavidCrow10-Apr-12 6:39
memberDavidCrow10-Apr-12 6:39 
QuestionFantastic! Pin
Member 428961310-Apr-12 0:29
memberMember 428961310-Apr-12 0:29 
AnswerRe: Fantastic! Pin
Member 428961310-Apr-12 1:36
memberMember 428961310-Apr-12 1:36 
AnswerRe: Fantastic! Pin
Ivan Shcherbakov18-Apr-12 22:10
memberIvan Shcherbakov18-Apr-12 22:10 
GeneralExcellent Pin
Suchi Banerjee, Pune8-Apr-12 23:36
memberSuchi Banerjee, Pune8-Apr-12 23:36 
QuestionNew with 2010: Sticky Hover watches Pin
Steve Wellens6-Apr-12 17:28
memberSteve Wellens6-Apr-12 17:28 
In VS 2010, when you hover and get a watch popup, you can click the thumb tack and have it persist. There are several options, the coolest, you can fix it to the page or the window (it will scroll with the window or stay frozen).
Steve Wellens

QuestionEdit and Continue (EnC) Pin
Igor Okulist4-Apr-12 18:06
memberIgor Okulist4-Apr-12 18:06 
AnswerRe: Edit and Continue (EnC) Pin
Igor Okulist18-Apr-12 12:56
memberIgor Okulist18-Apr-12 12:56 
AnswerRe: Edit and Continue (EnC) Pin
Ivan Shcherbakov18-Apr-12 22:08
memberIvan Shcherbakov18-Apr-12 22:08 
Questionnice Pin
CIDev4-Apr-12 4:01
memberCIDev4-Apr-12 4:01 
SuggestionCommand Window Pin
chaau3-Apr-12 14:15
memberchaau3-Apr-12 14:15 
GeneralRe: Command Window Pin
Ivan Shcherbakov4-Apr-12 10:17
memberIvan Shcherbakov4-Apr-12 10:17 
GeneralRe: Command Window Pin
Alexis.P17-Apr-12 7:39
memberAlexis.P17-Apr-12 7:39 
GeneralThumbs up!! Pin
Thiago Calil3-Apr-12 13:59
memberThiago Calil3-Apr-12 13:59 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web02 | 2.8.160212.1 | Last Updated 18 Apr 2012
Article Copyright 2012 by Ivan Shcherbakov
Everything else Copyright © CodeProject, 1999-2016
Layout: fixed | fluid