[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 1/3] target/riscv: Tell gdbstub the correct number of CSRs
|
From: |
Jonathan Behrens |
|
Subject: |
Re: [PATCH v3 1/3] target/riscv: Tell gdbstub the correct number of CSRs |
|
Date: |
Tue, 8 Oct 2019 10:01:47 -0400 |
On Tue, Oct 8, 2019 at 5:54 AM Bin Meng <address@hidden> wrote:
>
> On Tue, Oct 8, 2019 at 8:15 AM Jonathan Behrens <address@hidden> wrote:
> >
> > If the number of registers reported to the gdbstub code does not match the
> > number in the associated XML file, then the register numbers used by the
> > stub
> > may get out of sync with a remote GDB instance.
>
> I am not sure how to trigger the out of sync issue. Do you know how?
Try applying the next patch in the series without this one. Attempting
to access the priv register will return E14 because GDB will think
that priv has register number 309 (since the last register with an
assigned regnum is fcsr=68 and then none of the 240 CSRs have assigned
numbers) while the GDB stub will think that the number is 4165 (=33 +
36 + 4096).