[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/2] gdbstub: Set current_cpu for memory read write
|
From: |
Peter Maydell |
|
Subject: |
Re: [PATCH 1/2] gdbstub: Set current_cpu for memory read write |
|
Date: |
Mon, 28 Mar 2022 09:09:47 +0000 |
On Mon, 28 Mar 2022 at 03:10, Bin Meng <bmeng.cn@gmail.com> wrote:
> IMHO it's too bad to just ignore this bug forever.
>
> This is a valid use case. It's not about whether we intentionally want
> to inspect the GIC register value from gdb. The case is that when
> single stepping the source codes it triggers the core dump for no
> reason if the instructions involved contain load/store to any of the
> GIC registers.
Huh? Single-stepping the instruction should execute it inside
QEMU, which will do the load in the usual way. That should not
be going via gdbstub reads and writes.
-- PMM