microsoft / microsoft/MIEngine
Specifying command line arguments to gdb.exe
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
I'm trying to connect to a third-party gdb.exe that needs command line arguments to tell it which flavor of target it will be dealing with. This cannot be specified after gdb has launched. I'm specifically trying to do this from VSCode with a launch.json configuration, but the issue applies to VS launching as well.
Adding arguments to "miDebuggerPath" causes an invalid path error.
If there isn't currently a mechanism to do so, the feature request would be to add something like "miDebuggerArgs" that get passed into gdb.exe when launched.
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
Start by tracing how launch.json handles miDebuggerPath when gdb.exe is started, and where the MIEngine launch configuration is translated into debugger process arguments. Verify how the VS Code and Visual Studio launch paths differ. Done means a separate argument setting can pass parameters to gdb.exe without treating them as part of the executable path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100