microsoft / microsoft/debug-adapter-protocol
DAP Overview diagram for debuggers configure information only when the debuggee is about to start running.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 173
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 2
Description
The existing sequence diagram for a hypothetical GDB debug adapter works for some LLDB adapters, but not for others.
As per the overview page "Some debuggers are able to deal with this information very early, even before the debuggee is known; other debuggers accept this information only when the debuggee is about to start running." there are two ways of what I personally would call the start-up sequence.
Attached is a diagram for the second start-up sequence to cater for the "other debuggers accept this information only when the debuggee is about to start running."
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
Locate the DAP overview page and its existing sequence diagram for a hypothetical GDB debug adapter. Compare that diagram with the attached init-launch_2 image, then add the second startup sequence for debuggers that accept configuration only when the debuggee is about to start running; done means the overview documents both sequences clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100