https://bugs.kde.org/show_bug.cgi?id=356174
--- Comment #10 from Daniel Trebbien <dtrebb...@gmail.com> --- (In reply to Philippe Waroquiers from comment #9) > Otherwise, valgrind gdbserver expects that the debugger knows the register > layout of x86 or amd64. I think that this is what is causing the problem; i.e. that unlike gdb, lldb does not have built-in knowledge of the x86 and amd64 architectures. On my system (OS X 10.11.1 and Core i7 with AVX support), the embedded gdbserver responds with qXfer:features:read+ and lldb retrieves the target.xml. In my case, the embedded gdbserver sends back amd64-avx-coresse.xml. When I comment out the <xi:include>s leaving just the <architecture>i386:x86-64</architecture> element, then I also see "frame #0: 0xffffffffffffffff" and `register read' says "error: invalid frame". I think that the solution is to always respond with qXfer:features:read+ and for the XML target descriptions to have the generic register information. I am looking at the LLDB sources, within source/Plugins/ABI, to see what the appropriate generic registers are for the different architectures. -- You are receiving this mail because: You are watching all bug changes.
