microsoft / microsoft/vscode-cpptools
customLaunchSetupCommands does not work with ARM targets due to arch
Open
Nobody has claimed this yet.
debugger
embedded
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Bug type: Debugger
Describe the bug
- OS and Version:
- VS Code Version:
- C/C++ Extension Version:
- Other extensions you installed (and if the issue persists after disabling them):
- A clear and concise description of what the bug is.
On Windows trying to use customLaunchSetupCommands to configure a target launch on an embedded arm device I am getting the error message "Unable to start debugging. Specified argument was out of the range of valid values. PArameter name: arch".
This needs a cross compile project to repro and some setup for the embedded debugger. I have some projects that can be shared for the repro.
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 with the customLaunchSetupCommands handling in the C/C++ extension and reproduce the issue on Windows using a cross-compiled embedded ARM project and debugger setup. Done means the custom launch commands start debugging without the invalid "arch" argument error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- devtools, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100