microsoft / microsoft/vscode-cpptools
GDB Debugging Optimization: don't request Call Stack or Variables if window pane is minimized
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
Hi, I work on a fairly large repository and I notice that using GDB (cppdbg) with vscode always requests Call Stack and Variables information, which makes stepping through each line very slow. Can the cppdbg plugin not ask gdb for the Call Stack and Variables on every step if I minimize those window panes in the VSCode UI? (or alternatively have a setting to not eagerly load those)
Thanks
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 tracing how the cppdbg plugin requests GDB Call Stack and Variables data while stepping in VSCode. Check how the Call Stack and Variables panes' minimized state is exposed, then define done as avoiding those requests when the panes are minimized or providing a setting for non-eager loading. No specific files or tests are identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100