microsoft / microsoft/MIEngine
`stopAtEntry` and `launchCompleteCommand` ignored for GDB remote targets
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
MIEngine will ignore configuration parameters when connecting to a GDB server (either a literal gdbserver instance, or something else that implements that interface, like openocd). The default behaviour (stopAtEntry: true and launchCompleteCommand: exec-continue) is used regardless of user configuration.
This presents a major roadblock for using MIEngine-based tools (VSCode C/C++) for remote debugging, such as for embedded targets.
References:
#883
https://github.com/microsoft/vscode-cpptools/issues/3739
https://github.com/microsoft/vscode-cpptools/issues/2715
https://github.com/microsoft/vscode-cpptools/issues/978
https://github.com/microsoft/vscode-cpptools/issues/321#issuecomment-278635202
Contributor guide
No contributing guide indexed for this repository
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
Trace how stopAtEntry and launchCompleteCommand are handled when MIEngine connects to GDB remote targets, including gdbserver and openocd. Compare that path with the default behavior, then verify that user configuration is respected for remote debugging and check the related issues for expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100