Re: [lldb-dev] LLDB using Valgrind's embedded gdbserver

2015-12-05 Thread Daniel Trebbien via lldb-dev
Hello Greg, Thank you very much for this explanation. It makes perfect sense to me now the reason for the crash at ABISysV_x86_64.cpp:485, and that supplying the generic register information will solve the problem. Testing out the following, the crash no longer occurs:

Re: [lldb-dev] LLDB using Valgrind's embedded gdbserver

2015-12-04 Thread Greg Clayton via lldb-dev
The issue is LLDB wants to know information in the registers in the register context regarding how they map to "generic" registers. For x86_64 this means: LLDB_REGNUM_GENERIC_PC -> rip LLDB_REGNUM_GENERIC_SP -> rsp LLDB_REGNUM_GENERIC_FP -> rbp LLDB_REGNUM_GENERIC_RA

[lldb-dev] LLDB using Valgrind's embedded gdbserver

2015-12-03 Thread Daniel Trebbien via lldb-dev
Hello, I am working on enhancing Valgrind's embedded gdbserver to allow LLDB to use it (https://bugs.kde.org/show_bug.cgi?id=356174 ). After adding support for 'qC' packets to the embedded gdbserver, LLDB is able to continue the halted program running under Valgrind; however, a short moment later