[all-commits] [llvm/llvm-project] ba60d8: [lldb] Parse and display register field enums (#95...

[David Spickett via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: ba60d8a11af2cdd7e80e2fd968cdf52adcabf5a1
      https://github.com/llvm/llvm-project/commit/ba60d8a11af2cdd7e80e2fd968cdf52adcabf5a1
  Author: David Spickett <david.spickett at linaro.org>
  Date:   2024-06-27 (Thu, 27 Jun 2024)

  Changed paths:
    M lldb/include/lldb/Target/RegisterFlags.h
    M lldb/source/Core/DumpRegisterInfo.cpp
    M lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
    M lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.h
    M lldb/source/Plugins/RegisterTypeBuilder/RegisterTypeBuilderClang.cpp
    M lldb/source/Target/RegisterFlags.cpp
    M lldb/test/API/functionalities/gdb_remote_client/TestXMLRegisterFlags.py
    M lldb/unittests/Core/DumpRegisterInfoTest.cpp

  Log Message:
  -----------
  [lldb] Parse and display register field enums (#95768)

This teaches lldb to parse the enum XML elements sent by lldb-server,
and make use of the information in `register read` and `register info`.

The format is described in

https://sourceware.org/gdb/current/onlinedocs/gdb.html/Enum-Target-Types.html.

The target XML parser will drop any invalid enum or evalue. If we find
multiple evalue for the same value, we will use the last one we find.

The order of evalues from the XML is preserved as there may be good
reason they are not in numerical order.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications