microsoft / microsoft/vscode-cpptools
When using 'dumpPath', 'program' is required yet unused
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: Windows
- VS Code: 1.93
- C/C++ extension: 1.21.6
Bug Summary and Steps to Reproduce
The program field is required yet unused when debugging
Steps to reproduce:
Create a debugger configuration that opens a .dmp file:
{
"name": "Open Dump File (Windows)",
"type": "cppvsdbg",
"request": "launch",
"dumpPath": "e:\crash.dmp",
"program": "unused field in case of opening dumps, that is required in the json",
"args": [],
"cwd": "${workspaceFolder}",
"environment": [],
},
This configuration works to open a dump, though as you can see program is not a requirement, yet the json requires it to be valid and allow the debugging.
Can this field be made optional in case dumpPath is filled in? (or at least add some note with the documentation of dumpPath)
Debugger Configurations
`
{
"name": "Open Dump File (Windows)",
"type": "cppvsdbg",
"request": "launch",
"dumpPath": "e:\crash.dmp",
"program": "unused field in case of opening dumps, that is required in the json",
"args": [],
"cwd": "${workspaceFolder}",
"environment": [],
},
### Debugger Logs
```shell
N/A
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
No implementation files or tests are named. Start by locating validation for cppvsdbg launch configurations involving dumpPath and program; done when dump configurations are accepted without program while ordinary launch configurations still require it, or the dumpPath documentation clearly explains the exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100