Optimized Debugging for Visual C++

 

When the compiler optimizes code, it repositions and reorganizes instructions. This results in more efficient compiled code. Because of this rearrangement, among other issues the debugger cannot always identify the source code that corresponds to a set of instructions.

 

Optimization can affect:

  • Local variables, which can be removed by the optimizer or moved to locations the debugger does not understand.
  • Positions inside a function, which are changed when the optimizer merges blocks of code.
  • Function names for frames on the call stack, which might be wrong if the optimizer merges two functions.
  • Optimized debugging is a feature which allows the user to debug optimized code better and address some of the issues mentioned above.

 

Your answers to this survey will help us make the right investments for future releases of Optimized Debugging for Visual C++. Completing this questionnaire should take about 5 minutes to finish.

 

If you have any questions, please feel free to contact Ankit Asthana at (aasthan@microsoft.com) at Microsoft.

 

Thank you for participating!


The Visual C++ team

 

 

The information you provide is entirely voluntary. If you do not wish to provide us with any information, please disregard this survey. By filling out and returning this survey, you agree that we can use, disclose, reproduce, or otherwise distribute your feedback at the aggregated level. Your personal information will remain confidential. Please check http://privacy.microsoft.com/en-us/default.aspx for Microsoft Privacy Statements.