In Visual Studio 2013 Update 2 and also in the earlier CTP releases of Visual Studio 2015, we released a memory diagnostic tool that allowed developers to take heap snapshots of their application and then examine the heap contents upon terminating their application. The initial release supported viewing managed and native objects in the heap, and ...
In Visual Studio 2015 we’ve introduced two improvements to the C++ debugging experience to address pain points that we’ve heard from you. Improved startup performance when launching applications (F5), and reduced the chance functions called from the Watch or Immediate windows deadlocking. Improved startup performance on F5 W...
In Visual Studio 2015 we’ve introduced two improvements to the C++ debugging experience to address pain points that we’ve heard from you. Improved startup performance when launching applications (F5), and reduced the chance functions called from the Watch or Immediate windows deadlocking. Improved startup performance on F5 Whe...
The past two releases of Visual Studio have evolved the Natvis format to allow developers to easily visualize their debug data inside the VC++ expression evaluator. The first Visual Studio “14” CTP provides a new way for native developers to consume and manage their Natvis debug visualizers. In response to requests from Visu...
In Update 2 for Visual Studio 2013, memory diagnostic tools were added for Windows Store and Windows Phone that enable developers to monitor live memory consumption and take heap snapshots of their applications for further analysis. The Visual Studio team is extending the existing tools to work for Windows Desktop applications in the next maj...
In Update 2 for Visual Studio 2013, memory diagnostic tools were added for Windows Store and Windows Phone that enable developers to monitor live memory consumption and take heap snapshots of their applications for further analysis. The Visual Studio team is extending the existing tools to work for Windows Desktop applications in the next maj...
It is quite common to have a program stopped in the debugger due to a crash or assertion caused by an object being in a bad state, and to track down the problem, you need to figure out how it got that way. In many cases, the call stack of the object's creation can provide valuable clues, but trying to get that call stack can be a significant chore....
A few days ago, we called out some of the great debugging topics on the Microsoft Developer Network (MSDN) Library. Here are some excellent resources outside of the MSDN Library (in no particular order except the last one): If you know of additional resources, add them to the comments (or send them to me, [email protected])&...
The MSDN Library is a rich source of information about Microsoft products and technologies including Visual Studio and Visual C++. This post calls out some of the great code debugging topics available for Visual C++ native code developers.The best starting point for (re)visiting debugging topics is the Debugger Roadmap. It contains links to many di...
Windows 8.1 and Visual Studio 2013 come with improvements for exception reporting in the platform and the debugger which will make it easier for native Windows Store App developers to diagnose errors in their applications. In this post, I’ll discuss a few of those improvements that are available in Visual Studio 2013 and show the differences ...
