microsoft / microsoft/vscode-cpptools
Progress picker not showing the remote progresses
Open
Nobody has claimed this yet.
debugger
Feature Request
- 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: Windows 10, 19044.1348
- VS Code Version: 1.62.3
- C/C++ Extension Version: 1.7.1
- Other extensions you installed (and if the issue persists after disabling them):
- A clear and concise description of what the bug is.
When specifying a remote address in launch.json, like"miDebuggerServerAddress": "192.168.35.2:6000", and settingrequestTypetoattach, the progress picker shown is for local processes. We need the remote processes instead (with a command likeinfo os processesfor gdb).
To Reproduce
Steps to reproduce the behavior:
- Setup a GDB server on a remote machine
- Add a local launch file, that specifies
miDebuggerServerAddress, withrequestTypeset toattach. - Start debugging. Expecting to see a progress picker for a remote machine,
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 by reproducing the attach flow with a launch.json configuration using miDebuggerServerAddress and requestType set to attach. Trace how the progress picker selects local processes, then investigate the GDB info os processes query; done means the picker shows remote processes for a remote GDB server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100