microsoft / microsoft/vscode-cpptools
Copy Value in C++ debugger copies value incorrectly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Environment
Version: 1.91.1 (user setup)
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:06:49.809Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.19045
Bug Summary and Steps to Reproduce
Bug Summary: it's impossible to copy the full value of a variable in debugger variables window. Current "Copy value" functionality displays only 1-3 fields and clamps all the value, which defeats all point of this feature.
This is required for comparing values between different debugger runs, and copying each field by hand is not a sustainable approach
Repro:
- Create a struct in code with 5+ fields, some of them nested
- Execute the program and break at a line where a variable of this struct is inspectable in the debugger variables
- Right click the variable in the debugger variables and select Copy Value
- Paste the value and inspect the result
Expected outcome: full value
Actual outcome: clamped value like {myField1={myField2=mystring myId=empty myData=MapCount=??? ArrayCount=??? } ...}
The result should be the full value
Debugger Configurations
inapplicable
Debugger Logs
inapplicable
Other Extensions
No response
Additional Information
No response
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
Reproduce the issue with a C++ struct containing nested fields, then trace the Copy Value action from the debugger variables window. Done means copying and pasting a variable produces its full nested value rather than a clamped representation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100