https://bugs.kde.org/show_bug.cgi?id=356174
--- Comment #15 from Daniel Trebbien <dtrebb...@gmail.com> --- Looking through the sources of the release_35 and release_36 branches, I see that LLDB 3.5 and 3.6 do not support the target.xml or target definition file ways of specifying register information. See ProcessGDBRemote::BuildDynamicRegisterInfo(): http://llvm.org/svn/llvm-project/lldb/branches/release_35/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp http://llvm.org/svn/llvm-project/lldb/branches/release_36/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp LLDB 3.7 is the first to add this support: http://llvm.org/svn/llvm-project/lldb/branches/release_37/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp I think that to get this working with LLDB 3.5 and 3.6, the embedded gdbserver would need to respond to 'qRegisterInfo XX' packets. 'qRegisterInfo' is specific to LLDB. It is documented here: http://llvm.org/svn/llvm-project/lldb/trunk/docs/lldb-gdb-remote.txt Adding support for 'qRegisterInfo' would entail using an XML parser in the embedded server which can build up the XML target description (resolving the <xi:include>s if any), and then process the <reg> elements. Would adding a dependency on an XML parser be out of the question? Preferably libxml2. -- You are receiving this mail because: You are watching all bug changes.
