Add support to VSCode WSL remote about openimagedebugger HOT 10 CLOSED

Hi @binfsuc, I haven't tested debugging with VSCode + WSL. My guess is that VSCode is not configured to use the same gdb binary as the one from WSL.

Can you share all the project files from this C++ demo, please? (CMake-related files, source code and launch.json)

from openimagedebugger.

Hi @binfsuc, I haven't tested debugging with VSCode + WSL. My guess is that VSCode is not configured to use the same gdb binary as the one from WSL.

Can you share all the project files from this C++ demo, please? (CMake-related files, source code and launch.json)
Thank you. If it is what you said, how should I modify it

from openimagedebugger.

Hi @binfsuc if you can share them as files and/or text it gets easier for me to help :)

from openimagedebugger.

@brunoalr ok ，this is all file

myprojects.zip

from openimagedebugger.

Thanks! I will try to reproduce it later and let you know.

from openimagedebugger.

ok
my ./gdbinit

run python3 /path/to/OpenImageDebugger/oid.py --test

from openimagedebugger.

is there any progress?

from openimagedebugger.

I was able to reproduce the issue.

The more detailed error message I got is

&"warning: GDB: Failed to set controlling terminal: Operation not permitted\n"
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

[OpenImageDebugger] No clients connected to OpenImageDebugger server

But I don't know how to solve this. Sorry.

On the other hand, I tested debugging via the command line and it works fine on Windows 10 + WSL2 + MobaXterm's X11 server. I would recommend using OID via the command line, since right now we don't have much time to focus on specific IDEs. Feel free to contribute, though :)

from openimagedebugger.

I also did one final test, in the same setup (Windows 10 + WSL2 + MobaXterm's X11 server) I installed vscode inside WSL and I can confirm it works.

from openimagedebugger.

Another test: I was able to get access to a Windows 10 22H2 with WSLg support and managed to get OID to work when connecting to a WSL remote on VSCode running on the host machine. Make sure you source oid.py correctly, for example via ~/.gdbinit.

from openimagedebugger.