Unable to start debugging: How to attack the issue.
I am the owner for the device debugging efforts from the Visual Studio for Devices team. If you are hitting "Unable to start debugging" or any similar issue in F5 experience, please feel free to convey the information via MSDN feedback centre. While doing so try to provide as much information as possible.
BTW F5 e2e scenario contains three stages: connection to the device, deployment of the files and then starting the debugger.
What information is needed?
Sample Template for the diagnosis in the order of value.
The above information will ensure if it is a debugger specific issue or not. Now to the next stage
The more the information the resolution would be quicker. Then the next stage
Running the scenario by running the scenario using VSD Logging instructions and sending the logs to us. I would defer the details of this stage to a subsequent blog as this applies to any scenario in VSD and not specific to debugger.
Why does it happen?
Let me highlight the most common reasons for hitting the same.
if (QueryInstructionSetFunc != NULL) QueryInstructionSetFunc(PROCESSOR_QUERY_INSTRUCTION, &instructionSet);
and then verifying if the instructionset is present in Microsoft.TypeMaps.8.0.xsl.
The workaround here would be adding an equiavalent entry in the global datastore. However this needs be done with utmost care. So better backup the globa datastore before doing the same. We know one entry which is missing currently....84017153 during one of our customer interactions. More details on this in subsequent blogs.
and ensure that icordbg.dll is infact present at the given path.
The workaround here would be to do regsvr32 icordbg.dll. However this should not be the normal case and we would love to hear why you are hitting it for root cause analysis.