Version and Platform (required):
- Binary Ninja Version: 5.3.8940-dev
- OS: macOS (host) Linux (remote)
- OS Version: 14.2 (host) 24.04 (remote)
- CPU Architecture: M2 (host) x86_64 (remote)
- Local or Remote Debugging: remote
Bug Description:
I tried to attach to a gdbserver using an empty binary data view (New Binary Data action) and the debugger was unable to show me any memory of the target. This is likely because I'm using New Binary Data, as this does not replicate when using New Mapped Data. I got an error: [Analysis] Attempting to add function not backed by file: 0x784b95b84490 which I assume is of similar reason.
Steps To Reproduce:
- Start gdbserver on remote host, I used
gdbserver --attach --once stdio <pid>
- Binja > New
- Binja > Debugger > Connect to Remote Process
- Enter remote details
- Observe debugger attaches and cannot show memory
- In my case I also was presented Code Insight Map which was entirely unhelpful
Expected Behavior:
I expected to either be able to see the debugged binary's memory or to have an error message telling me to use Mapped Data or something.
Screenshots/Video Recording:

Binary:
No binary, because the whole bug is that I didn't open a binary to begin with