-
Notifications
You must be signed in to change notification settings - Fork 218
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
Improve messages for unknown breakpoints and watchpoints. (#1282) #1283
Conversation
5ad3fc7
to
2570e98
Compare
Continuous integration failure on Linux does not seem to be related to this pull request:
|
I'm taking a look at this, something within infrastructure changed or that endpoint it pulls from is dead and we need to use a different machine. |
…1282) The C/C++ extension does not support all the features of GDB breakpoints and watchpoints, so users may need to set breakpoints via "-exec break ..." in the DEBUG CONSOLE, and similarly for watchpoints via "-exec watch ...". When these are hit, include the available information in the exception message.
2570e98
to
e251975
Compare
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.
Otherwise looks good to me.
Here is the ResourcesStrings.Designer.cs that VS generates: |
Otherwise LGTM |
2910f81
to
b27dbd0
Compare
Thanks, I put that in the pull request. |
@gregg-miskelly Thanks for reviewing and helping me with the internationalization. |
No problem. Thanks for taking the time to submit this PR! |
The C/C++ extension does not support all the features of GDB breakpoints and watchpoints, so users may need to set breakpoints via
-exec break ...
in the DEBUG CONSOLE, and similarly for watchpoints via-exec watch ...
. When these are hit, include the available information in the exception message instead of just "Unknown breakpoint" or "Unknown watchpoint". Fixes #1282.The new behaviour for unknown breakpoints and unknown watchpoints (respectively) is shown in the screenshots below.