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

GDB: cannot connect to server while rizin can #3350

Open
1 task
boborjan2 opened this issue May 30, 2024 · 4 comments
Open
1 task

GDB: cannot connect to server while rizin can #3350

boborjan2 opened this issue May 30, 2024 · 4 comments
Labels
BUG Debug Issues related to the Debug component of Cutter

Comments

@boborjan2
Copy link

boborjan2 commented May 30, 2024

Environment information

  • Operating System: Win11/Linux
  • Cutter version: Version 2.3.4-HEAD-209c26b
  • Obtained from:
    • [] Built from source
    • [x ] Downloaded release from Cutter website or GitHub
    • Distribution repository
  • File format:
    PE32 or other

Describe the bug
This works:
rizin.exe -d gdb://172.21.208.1:1235
(I verified by wireshark. RSP comm between rizin and mingw gdbserver running on Win11, started with a PE32 file by:
gdbserver 172.21.208.1:1235 bin/api_test.exe. gdbserver can be connected using gdb, r2, rizin)

However, when I load the target.exe in Cutter and then connect to the very same gdbserver, I get a popup and Cutter gets nonresponsive. Wireshark shows no communication to the gdbserver.
I tried to not load the exe as well, but it is not clear to me whether it is supported.

Cutter gets frozen when using gdbserver.

To Reproduce
Start a gdbserver and connect to it with Cutter.

Expected behavior

Cutter is able to connect to a gdbserver rizin can access.

Screenshots

image

And no comm in wireshark.

Additional context

@boborjan2
Copy link
Author

I tried the same in Linux (WSL). I can connect to the gdbserver via gdb in wsl prompt (gdb->target remote 172.21.208.1:1235), comm is visible in wireshark. Cutter started from the very same terminal however just displays the same popup, gets unresponsive and needs to be terminated with kill -9.

@karliss karliss added BUG Debug Issues related to the Debug component of Cutter labels May 30, 2024
@karliss
Copy link
Member

karliss commented May 30, 2024

Was able to obtain similar result by running everything on Linux.

@boborjan2
Copy link
Author

Was able to obtain similar result by running everything on Linux.

Thx, I updated description accordingly.

@boborjan2
Copy link
Author

seemingly very similar or duplicate of #3277

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG Debug Issues related to the Debug component of Cutter
Projects
None yet
Development

No branches or pull requests

2 participants