-
-
Notifications
You must be signed in to change notification settings - Fork 489
ATL-1150: Bumped the cortex-debug to 0.3.10.
#267
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
Conversation
Signed-off-by: Akos Kitta <kittaakos@typefox.io>
CCing @fstasi to share how to update a VS Code extension in the new IDE.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Seems straightforward...I can write some lines in a doc about this.
@ubidefeo
ubidefeo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have ways to test this one for current lack of hardware.
Also it would require a custom configuration.
The change is clearly gonna bring in a new version of this extension which does not seem to have bug-fixes over 0.3.10.
Be aware that soon we'll have to update to 0.3.12 since now they're in pre-release.
This adds
A new runToEntryPoint configuration property to replace runToMain allowing the actual entry point name to be configured
which will allow us to set setup() as our point of entry for debug 👍🏼
Signed-off-by: Akos Kitta kittaakos@typefox.io