microsoft / microsoft/vscode-cpptools
Debug active TU source (similar to debug active file, but check which source file is associated with active header)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Issue Type: Feature Request
Situation :
You are debugging a header, with a testfile. You set breakpoints in the header and trigger a debug on testfile. Now currently, when you restart debugging, it picks the current header you are viewing and attempts to start compiling and debugging it, but it can't because its a header that doesn't have a main.
Request :
The restart option remembers from which file the debugger was triggered, so we don't have to re-navigate to the file manually and then trigger the debugger from there.
Extension version: 1.7.1
VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:40:02.816Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No
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
No files, tests, or entry points are named in the issue. Start by tracing the restart-debugging flow and how the active header is associated with the source file that launched debugging; done means restarting from a header uses that associated source file instead of attempting to compile the header.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100