microsoft / microsoft/debug-adapter-protocol
Allow setting of mode also for function breakpoints
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 173
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 2
Description
Some debuggers (e.g. LLDB) can create function breakpoints in multiple different modes (software/hardware). At the moment DAP can not express this as the FunctionBreakpoint type is missing the mode parameter present on other breakpoint types.
Was there some specific reason for not allowing the mode on the FunctionBreakpoint?
Is there some other, standard way that mode of function breakpoint can be passed to the DA?
If both of the above are false please consider adding the mode parameter onto the FunctionBreakpoint type
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the DAP FunctionBreakpoint type and compare it with the other breakpoint types that already expose mode. Determine whether software or hardware mode can be represented there without conflicting with the existing protocol, then update the protocol definition so function breakpoints can carry mode. Done means the requested mode is expressible for function breakpoints and the behavior is documented by the protocol.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100