-
Notifications
You must be signed in to change notification settings - Fork 1
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
orogen debugging configuration no longer works #73
Comments
Oh crap. |
Yes. My thoughts exactly. |
May, 2020 release notes mention "automatic debug configurations". It seems like generating a launch.json is not necessary anymore, the user only needs one if he/she wishes to tune/modify targets that are automatically generated by the extension (much like how the tasks API works). Sounds cool. Reference: microsoft/vscode#88230 microsoft/vscode#95835 |
Actually, I just debugged an orogen component. I start it with VSCode (didn't try to attach) |
Interesting... it didn't for me (was starting with vscode as well). I will try again later. What version are you on? |
1.47.0 |
I'm closing this, I've been debugging orogen components in the last few months, and can vouch it works. Feel free to reopen if you still have the problem. |
Apparently, overriding the "type" member is not allowed anymore
The text was updated successfully, but these errors were encountered: