Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't debug remote binary while source code in a different machine #13225

Open
iCore-034 opened this issue Feb 3, 2025 · 2 comments
Open

Can't debug remote binary while source code in a different machine #13225

iCore-034 opened this issue Feb 3, 2025 · 2 comments
Labels
bug debugger help wanted Can be fixed in the public (open source) repo.

Comments

@iCore-034
Copy link

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

Copy link

github-actions bot commented Feb 5, 2025

Thank you for reporting this issue. We’ll let you know if we need more information to investigate it. Additionally, if you're working with GDB/LLDB, please note that the code is open source at https://github.com/microsoft/MIEngine/wiki/Contributing-Code . Your contributions are always welcome and appreciated.

@github-actions github-actions bot added the help wanted Can be fixed in the public (open source) repo. label Feb 5, 2025
@xgdgsc
Copy link

xgdgsc commented Feb 7, 2025

#13219

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug debugger help wanted Can be fixed in the public (open source) repo.
Projects
None yet
Development

No branches or pull requests

3 participants