microsoft / microsoft/vscode-cpptools
Show the process ID in the call stack on Windows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Not sure if the same process ID is applicable to Linux/Mac -- I could check, but I mostly want it for Windows.
I originally filed this on VS Code, but they said: "showing the process ID in the CALL STACK view as part of the session label or thread label is the recommended way (since there is no other place where to show it and since VS Code knows nothing about processes).".
It's available when debugging with Visual Studio 2022.
When I initially use the C/C++ debugger to attach to a process, it shows the process ID in the dropdown, but then I can't remember it and then I need to check later on which process ID I'm attached to and it doesn't show me in the UI (e.g. there are 3 such processes running and I want to make sure I'm attached to the one using 100% CPU and not one of the other 2).
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
The issue names no files, tests, or entry points. Start by locating the Windows attach and call-stack/session-label handling in the extension, then check how the existing process selection is represented. Done means the attached process ID is visible in the relevant Call Stack UI and the behavior is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript, vscode
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100