microsoft / microsoft/vscode-cpptools
Debugging callstack window: show information like thread id, and current function
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Type: Debugger
So I have to click through all the callstacks of each thread in order to find out what's happening. With 20 threads, this becomes a huge chore. Can we postfix the test_trajectory headers with extra information like the callstack's current function? Similar to what your counterparts do in Visual Studio 2019
Describe the bug
- OS and Version: Linux
- VS Code Version: 1.43.0
- C/C++ Extension Version: 0.26.3
- Other extensions you installed (and if the issue persists after disabling them):
- A clear and concise description of what the bug is.
To Reproduce
Run gdb with a program that uses several threads, and set a breakpoint. Then look at the callstack window.
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 reproducing the issue with GDB, a multi-threaded program, and a breakpoint, then inspect how the debugger callstack window labels each thread and frame. Compare the current headers with the Visual Studio 2019 example. Done means the headers expose useful details such as thread IDs and the current function for each callstack.
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
- 35/100