ITADN
hugsy/gef/Issues

[Bug] get-remote: can't interrupt remote qemu-user program

#1199Openmsaltini 创建于 2025-11-06
bugtriagestale
M
msaltinicommented
### GEF+GDB version ```shell GEF: (Standalone) Blob Hash(/home/parallels/.gef-2025.01.py): b8e6b38cd6f752a164f13da3330c976ff7d3c381 SHA256(/home/parallels/.gef-2025.01.py): bbaca32512575fbfd05ca40197214493e787d7caba6e3bd0cd6d157022a4ae1f GDB: 16.3 GDB-Python: 3.13 ``` ### Operating System Kali GNU/Linux Rolling ### Describe the issue you encountered I'm running an x86_64 program on my kali aarch64 vm using `qemu-amd64 -g 1234`. I have a working remote connection to the binary using `gef-remote --qemu-user localhost 1234`, I can set breakpoints and step through the binary. When I try breaking the program using Ctrl-C nothing happens except for the string `^C` getting printed in the gdb console. I checked the `remote interrupt-sequence` and it's set to `Ctrl-C`. ### Do you read the docs and look at previously closed issues/PRs for similar cases? Yes ### Architecture impacted - [ ] X86 - [ ] X64 - [ ] ARM - [x] ARM64 - [ ] MIPS - [ ] MIPS64 - [ ] PPC - [ ] PPC64 - [ ] RISCV ### Describe your issue. Without a proper reproduction step-by-step, your issue will be ignored. Provide a step-by-step to reproduce your issue. Terminal 1: `qemu-amd64 -g 1234 ./[bin_name]` Terminal 2: `gdb-multiarch ./[bin_name]`, `gef-remote --qemu-user localhost 1234`, `c`, `^C` ### Minimalist test case Use this field for a minimal code to compile and spot the issue: ```c // compile with gcc -fPIE -pic -o my_issue.out my_issue.c int main(){ return 0; } ``` You can also provide a Dockerfile if you prefer ### Additional context? - Screenshots - Callstack - Coredumps - If possible and useful, please upload the binary [bin.zip](https://github.com/user-attachments/files/23378154/bin.zip)
1 条评论