DavidSpickett wrote:
> So you could simulate a remote with the required register names, like in
> lldb/test/API/functionalities/gdb_remote_client/TestXMLRegisterFlags.py and
> tests that use MockGDBServerResponder. LLDB might get confused if it's a name
> the client doesn't expect to ever see but in theory it should work as long as
> you're providing the required registers as well.
Today I was using qemu-aarch64 usermode emulation and it provides a bunch of
control registers. It has the same weird layout that your downstream example
has:
```
cp_regs:
ID_AA64PFR1_EL1 = 0x2000000000000000
ID_AA64PFR2_EL1_RESERVED = 0x0000000000000000
ID_AA64PFR3_EL1_RESERVED = 0x0000000000000000
SCTLR = 0x38e8c5cf00040000
```
So you could use those names with a fake AArch64 target for the test.
https://github.com/llvm/llvm-project/pull/188049
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
