Disconnect3d

@Erebua just to be sure, you installed pwndbg inside the qemu system image, right? If you have direct steps how to reproduce ur case I'd appreciate that

@Erebua https://github.com/pwndbg/pwndbg/pull/1107 may have fixed your cause, but I still haven't been able to reproduce it so I can't really check

Wait, how exactly are u running all this? How do u run the qemu-system? Can u give commands for that? The `vmmap` u showed is a bit weird: that's what...

@Erebua since this is not anymore about a recursion error, can you provide all necessary information to reproduce your issue in a new one and I will close this one?

Yup, I totally agree. I would be happy to merge a PR that fixes this problem.

@caprinux probably finding appropriate symbols by yourself and setting it via GDB's add-symbol-file (which is super clunky as u need to create a .c file, compile it etc).

Can you share the binary?

This works for me on the latest dev version: ``` pwndbg> version Gdb: 12.0.90 Python: 3.10.4 (main, Jun 29 2022, 12:14:53) [GCC 11.2.0] Pwndbg: 1.1.0 build: e7b4515 Capstone: 4.0.1024 Unicorn:...

We are currently running `isort`, `black` and `pyflake8`. I think we can close this for now. https://github.com/pwndbg/pwndbg/blob/d4850beecc8825308d24a5c371e9fa7147898c3b/.github/workflows/lint.yml#L27-L33

Can it be that this specific binary did not have debug info for that type? What if you used u16 explicitly in Rust code?