DavidSpickett wrote: Usually we're adding registers to lldb and lldb-server at the same time so the test would debug a program that initialises those registers to a given pattern. I don't think there's anything wrong with making lldb aware of what other stubs send though, so there's no need to change lldb-server.
To test this you can create a fake server that returns these registers. `lldb/test/API/functionalities/gdb_remote_client/TestXMLRegisterFlags.py` is the most extensive example of that but you can find more minimal ones too. `MockGDBServerResponder` is the key class. lldb will I presume, ignore the registers without the changes in this PR, and show them when the changes are included. You can put the test in that same folder in fact, and there is already a YAML program file that should be enough. In your responder you can return whatever data you want for the registers. I usually return `register number + 1` for each register. https://github.com/llvm/llvm-project/pull/214034 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
