You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'd like to be able to set a watchpoint to break the program anytime a specific variable changes.
Describe the solution you'd like
I'd like to be able to right-click on a variable, either in a watch view or code, and choose to set a watchpoint(or data-breakpoint in Visual Studio lingo).
Alternatively, something similar to Visual Studio's Debug->New Breakpoint->Data Breakpoint->Type in the symbol would also work.
Describe alternatives you've considered
I don't think I have any good alternatives. We don't have enough pins to use an external debugger. It is possible to set watchpoints using plain GDB, but I like the ability to view source is VSCode. I've looked at the various breakpoint options but they all appear to be instruction-breakpoint related.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
[Feature Request]: ability to set watchpoint on variables
[Feature Request]: ability to set watchpoint on variables (VSC-1583)
Jan 30, 2025
Is your feature request related to a problem? Please describe.
I'd like to be able to set a watchpoint to break the program anytime a specific variable changes.
Describe the solution you'd like
I'd like to be able to right-click on a variable, either in a watch view or code, and choose to set a watchpoint(or data-breakpoint in Visual Studio lingo).
Alternatively, something similar to Visual Studio's Debug->New Breakpoint->Data Breakpoint->Type in the symbol would also work.
Describe alternatives you've considered
I don't think I have any good alternatives. We don't have enough pins to use an external debugger. It is possible to set watchpoints using plain GDB, but I like the ability to view source is VSCode. I've looked at the various breakpoint options but they all appear to be instruction-breakpoint related.
The text was updated successfully, but these errors were encountered: