Learn to use Visual Studio, Visual Studio Online, Application Insights and Team
Foundation Server to decrease rework, increase transparency into your application and increase the rate at which
you can ship high quality software throughout the application lifecycle
One of the areas that we have improved in VS2012 updates is dump debugging. In this post, I will explain dump debugging feature specific to the ARM architecture. We want to enable all developers who are building Windows Store applications targeting the Surface RT and other ARM devices.
Even though we had the live debugging support for apps targeting ARM from day one, dump debugging needed additional work that we were able to do post-RTM. Arm Dump debugging support allows developers to investigate crashes and other bugs that occur on the customer’s device.
As a first step to achieve this, we have enabled native debugging of ARM dumps in VS2012 Update 1.
(Update 1 of VS2012 opens ARM dump and has native debugging link available)
This support will be useful for all the developers out there writing native apps and games for Windows RT. This support will also help some developers with the apps that use mixed mode (both managed and native code). They will be able to debug the problems that originate from or in the native code.
To start debugging an ARM dump natively, follow these easy steps.
(After starting native debugging for an ARM dump, walking through call stack and source code)
You often need to save a dump in a tricky scenario when live debugging an app remotely on an ARM machine. This can be for any reason including performance issues, hangs or even a crash. When saving a dump for an ARM machine in a live debugging scenario, one inconvenience is to manually copy those dumps to the development machine for debugging purposes. This gets more painful when machines are not in close proximity to use a flash drive and copy the dump over.
To streamline this process, we have added a new feature in remote debugging. Now you are able to save a dump locally (where VS is installed) even when debugging an app on a remote machine.
This is not specific to ARM but folks developing apps for ARM would definitely benefit the most.
To use this feature, there is nothing new to learn. Same old steps with a slight change.
That is all in terms of dump debugging improvements for ARM.
As always, we want to hear your feedback. Feel free to leave your comments below, and for general debugger, profiler and IntelliTrace questions please use Diagnostics MSDN forum.