-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Windows 10 x64 support? #69
Comments
GDBFrontend doesn't support Windows but you can use it on WSL (Windows Subsystem for Linux). |
@rohanrhu Thank you. Sadly I cannot use WSL as I am building QEMU using MSYS64 so it generates Windows binaries. It is these I would like to debug. QEMU will not build on WSL. What is it that prevents operation on Windows? What is missing? |
GDB doesn't support background execution on Windows. You can run QEMU on WSL but I think it might not be able to use KVM on WSL. Another option, you can run GDBFrontend on WSL and connect to the Windows GDB that runs QEMU from WSL one. |
Can you confirm: you need GDB to run as a detached process but ideally you would know its PID so it can be closed/killed? |
https://sourceware.org/gdb/wiki/GDB%20Front%20Ends As you can see here, GDBFrontend doesn't use MI interface. GDBFrontend runs on a thread in GDB process. All of GF APIs use GDB APIs that must be called on GDB's main thread but since background execution is unavailable on Windows, your debugged process is blocking GDB's main thread; GF pushes callbacks to run them on main thread but when main thread is blocked by the debugged process while running, it is not possible to get them called when they must be. |
Looks very interesting. If it can help with my MSYS64/gcc debugging problem then A+++. Many thanks.
What have I missed here? What does
Tmux
do on Windows?The text was updated successfully, but these errors were encountered: