-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging Restart Fails With Azure Sphere Projects #212823
Comments
Please let me know if you'd like a virtual walkthrough |
The C++ debug adapter doesn't set |
It looks like you register your own debug adapter type, and resolve it to cppdbg in your provider, is that right? |
I don't think it does. Should it be? |
Yes this is right |
No, it just enables a different mode for restarting and I'm checking which path it goes down. |
I was thinking about where the problem could be, and I came across a bug here #212991 and I think it might fix your issue, but I'm not sure. Our Insiders releases are paused for the Build conference, so this won't be in an Insiders until around next Thursday. You can try then, or build the vscode repo if you want to try it earlier. |
@roblourens thanks, I'll try it out when it releases. I'm not in a rush |
@roblourens I tried the insiders release and the issue seems to be fixed! When would this be updated in the main vscode btw? |
Thanks for confirming. We will release VS Code this week |
Does this issue occur when all extensions are disabled?: N/A (extensions are necessary to repro)
Steps to Reproduce:
Note: You cannot reproduce this without an Azure Sphere device so I recorded this video (Microsoft internal).
a. "launch: property 'program' is missing or empty" notification pops up on bottom right, but you can see that this property was provided in the original launch configuration.
This is the Azure Sphere configuration provider: configurationProvider.ts - Repos (azure.com). Line 548 is where we start debugging. Our code isn't touched again after hitting restart.
This is a screenshot comparing the project's launch.json, the initial launch configuration given to the C/C++ extension and the launch configuration given to the C/C++ extension on restart:
The text was updated successfully, but these errors were encountered: