GDB: cannot connect to server while rizin can

[boborjan2]

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

And no comm in wireshark.

Additional context

[boborjan2]

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]

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

[boborjan2]

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

Thx, I updated description accordingly.

[boborjan2]

seemingly very similar or duplicate of #3277

[andreas-jonsson]

Running Cutter 2.3.4 Flatpak build on Debian shows the same issue.
I have a custom GDB stub and I can't see any connection attempt at all. It just freezes.

Is there a workaround for this? If not, do anyone know of a previous version that did work?

[wargio]

i think is also due flatpak not allowing doing debug.

[andreas-jonsson]

i think is also due flatpak not allowing doing debug.

Hmm.. I will check that.
But I would assume outgoing connections are not a problem.

[wargio]

that is true. sorry i misread the messages.

[duckfromdiscord]

seemingly very similar or duplicate of #3277

Thank you for the mention. I'll keep an eye on this issue