microsoft / microsoft/debug-adapter-protocol
Provide stack frame change events
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 173
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 2
Description
It seems there is currently no event (or reverse request) defined in the DAP to inform clients of a change in the currently active stack frame. Allowing for such communication between the debugger and the client listening to DAP events will make it easier to keep debugger/IDE state in sync.
For example, in implementing a C++ DAP extension I would like to support GDB up/down commands in the Debug Console to change the currently active stack frame in the IDE. Today, it seems the only support the DAP has for rendering a change in the currently active stack frame is when the client initiates a StackTraceRequest or when a user clicks on a specific frame in the IDE.
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 by reviewing the DAP protocol definitions around StackTraceRequest and the existing event or reverse-request patterns. Define how clients learn that the active stack frame changed after debugger commands such as GDB up/down, and verify that the communication keeps debugger and IDE state synchronized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100