microsoft / microsoft/vscode-cpptools
Can't debug remote binary while source code in a different machine
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Type: Bug
New version of extention doesn't allow debug remote binary file while source code is located on local machine.
There is even no logging info, debug jush doesn't start.
Problem linked with the newest extention version 1.23.5
Extension version: 1.22.11
VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.26100
Modes:
Remote OS version: Linux x64 3.10.0-862.el7.x86_64
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 7 4800H with Radeon Graphics (16 x 2895) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 15.42GB (7.72GB free) |
| Process Argv | --crash-reporter-id 50debbdf-1321-493b-a62a-25689b39e7fe |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | SSH: build_server_127 |
| OS | Linux x64 3.10.0-862.el7.x86_64 |
| CPUs | Intel(R) Xeon(R) Silver 4310 CPU @ 2.10GHz (48 x 2699) |
| Memory (System) | 93.35GB (44.71GB free) |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dwnewjupyter:31046869
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
iacca1:31171482
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
hdaa2157:31222309
copilot_t_ci:31222730
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
The report names no source files, entry points, or tests. Start by reproducing remote debugging over the VS Code SSH setup with the reported Windows and Linux environments, and first resolve the conflicting extension versions (1.23.5 versus 1.22.11). Done means the remote binary starts debugging against local source, with useful logging if it still fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100