microsoft / microsoft/vscode-cpptools
Add support for write memory from DAP
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Feature Request
This feature request was closed a while ago, awaiting VS Code core support: https://github.com/microsoft/vscode-cpptools/issues/509. I actually had thought this shipped, but forgot I was actually using the LLDB debugger rather than cppdbg for the native project I've been working on.
Since VS Code 1.64 in January of this year, VS Code supports DAP readMemory/writeMemory. If the C++ debugger returned memoryReferences for its variables and supported these calls, then users of the C++ tools extension would get a memory viewer and editor.
I implemented the support for this in VS Code, feel free to ping me here or on Teams if you have any questions or problems.
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 linked VS Code core issue and the DAP readMemory/writeMemory support described here, then trace how cppdbg exposes variables to determine where memoryReferences and the two calls belong. Done means the C++ debugger supports memory viewing and editing through VS Code; no repository files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100