jasonmolenda wrote: I thought we augmented the target.xml from the remote gdb stub via `ABI::AugmentRegisterInfo` -- adding eh_frame/dwarf register numbers that were not supplied by the stub, for instance -- but looking at AArch64 & x86, it looks like it's just adding the slice registers like w0 / x0 and eip / rip to the registers provided. Ideally the remote stub should only tell us, like, "I have a register x1 and I will use number 1 to refer to it" and we should know everything else, the size, default format, ABI register numberings for x1 from internal knowledge. In the beginning we had the model of "debugserver tells us everything about registers, lldb knows nothing built-in" but that was never going to work for wider interop and it didn't last long.
https://github.com/llvm/llvm-project/pull/143499 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
