microsoft / microsoft/vscode-cpptools
Watch window does NOT show vector data correctly in Google Test debug session.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Environment
- OS and version: Ubuntu 24.04
- VS Code: 1.91.1
- C/C++ extension: 1.21.4
- OS and version of remote machine (if applicable):
- GDB / LLDB version: GNU gdb (Ubuntu 15.0.50.20240403-0ubuntu1) 15.0.50.20240403-git
Bug Summary and Steps to Reproduce
Bug Summary:
This does NOT happen in Console application debug session:
Does this issue occur when all extensions are disabled?: Yes/No
Steps to reproduce:
- In this environment...
- With this config...
- Do '...'
- See error...
Debugger Configurations
launch.json and/or tasks.json are not used in my workspace
Debugger Logs
launch.json is not used in my workspace.
Other Extensions
No response
Additional Information
https://github.com/microsoft/vscode/issues/224119
https://github.com/matepek/vscode-catch2-test-adapter/issues/439
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 source files, entry points, or tests are named. Start by reviewing the linked VS Code and Catch2 adapter issues, then reproduce the watch-window behavior with the stated Ubuntu, VS Code, C/C++ extension, and GDB versions in a Google Test debug session and compare it with a console debug session. Done means the vector data displays correctly in the affected session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- devtools, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100