Hi Philippe,
On 9/27/22 13:13, Philippe Mathieu-Daudé wrote:
On Tue, Sep 27, 2022 at 12:09 PM Helge Deller wrote:
When the emulation stops with a hard exception it's very useful for
debugging purposes to dump the current guest memory layout (for an
example see /proc/self/maps) beside the CPU
Hi Helge,
On Tue, Sep 27, 2022 at 12:09 PM Helge Deller wrote:
>
> When the emulation stops with a hard exception it's very useful for
> debugging purposes to dump the current guest memory layout (for an
> example see /proc/self/maps) beside the CPU registers.
>
> The open_self_maps() function pr
When the emulation stops with a hard exception it's very useful for
debugging purposes to dump the current guest memory layout (for an
example see /proc/self/maps) beside the CPU registers.
The open_self_maps() function provides such a memory dump, but since
it's located in the syscall.c file, var
When the emulation stops with a hard exception it's very useful for
debugging purposes to dump the current guest memory layout (like
/proc/self/maps) beside the CPU registers.
The open_self_maps() function provides such a memory dump, but since
it's located in the syscall.c file various changes (a
