Skip to content
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

Debug Protocol: Data Breakpoints #38

Closed
jacdavis opened this issue Jun 23, 2016 · 5 comments
Closed

Debug Protocol: Data Breakpoints #38

jacdavis opened this issue Jun 23, 2016 · 5 comments

Comments

@jacdavis
Copy link

In order to the vscode protocol in VS, we would need support for data breakpoints in the protocol. These are currently a native only feature, but one of the most commonly requested features in managed (requiring clr changes).

The minimum fields would be

  1. threadid the databp applies to (optional)
  2. a data expression to be evaluated to an address
  3. The size of number of elements (limited by hardware, but other runtimes may not have this limitation.

The VS ui only supports data breakpoints when a value changes, but we do get asked for read data breakpoints sometimes.

@weinand weinand self-assigned this Jun 24, 2016
@weinand weinand added this to the backlog milestone Jun 24, 2016
@weinand
Copy link
Contributor

weinand commented Nov 20, 2017

his feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable.
Thanks for understanding and happy coding!

@gigimushroom
Copy link

why not add data breakpoint

@coderoid
Copy link

+1 on this issue, this will be hugely useful,

@igrr
Copy link

igrr commented Nov 15, 2018

Data breakpoints support would be quite useful for C code debugging. Please consider this for the next year's roadmap.

Including "watchpoint type" field (with possible values: read, write, access) would be great.

@weinand weinand reopened this Nov 15, 2018
@weinand weinand modified the milestones: Backlog, On Deck Nov 15, 2018
@weinand
Copy link
Contributor

weinand commented Nov 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants