Dominik Czarnota writes:
> Hi,
>
> We need the `qqemu.Pid` packet only for the QEMU system part in order
> to figure out the page tables and to do it efficiently.
Page tables of QEMU itself or the page tables for the guest its managing?
> We do have a fallback to using `monitor info mem` but it
Hi,
We need the `qqemu.Pid` packet only for the QEMU system part in order to
figure out the page tables and to do it efficiently. We do have a fallback
to using `monitor info mem` but it is slow, (iirc) doesn't provide all the
necessary information and (iirc) isn't implemented on all architectures
Dominik 'Disconnect3d' Czarnota writes:
> This patch adds support for the `qqemu.Pid` packet to the qemu
> gdbstub which can be used by clients to get the QEMU process PID.
>
> This is useful for plugins like Pwndbg [0] or gdb-pt-dump in order to
> inspect the QEMU process memory through the /pro
This patch adds support for the `qqemu.Pid` packet to the qemu
gdbstub which can be used by clients to get the QEMU process PID.
This is useful for plugins like Pwndbg [0] or gdb-pt-dump in order to
inspect the QEMU process memory through the /proc/self/{maps,mem}
interfaces. Without this feature,
