Describe the bug
Maybe this bug is pwndbg related and not qiling fault, but still worth to ask, when i use the remote gdb debugging with qiling and I connect with pwmdbg, the debugger works but the context is fucked up like in the screenshot:

Sample Code
from qiling import *
from qiling.arch.arch import QL_ARCH
if __name__ == "__main__":
ql = Qiling(["rootfs/hello.arm"], "rootfs")
ql.debugger = "gdb:127.0.0.1:9999"
ql.run()
Expected behavior
Pwndbg should just work fine
Additional context
The infinite loop seems to happen when pwndbg looks for binary memory mappings
Describe the bug
Maybe this bug is pwndbg related and not qiling fault, but still worth to ask, when i use the remote gdb debugging with qiling and I connect with pwmdbg, the debugger works but the context is fucked up like in the screenshot:
Sample Code
Expected behavior
Pwndbg should just work fine
Additional context
The infinite loop seems to happen when pwndbg looks for binary memory mappings