[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 --- Comment #16 from Philippe Waroquiers --- (In reply to Daniel Trebbien from comment #15) > 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

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 Daniel Trebbien changed: What|Removed |Added Attachment #95906|0 |1 is obsolete|

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 --- Comment #14 from Daniel Trebbien --- (In reply to Philippe Waroquiers from comment #13) > On debina8/x86, when using --vgdb-shadow-registers=yes, valgrind gdbserver > reports > qXfer:features:read+; > but lldb 3.5.0 does not

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 --- Comment #15 from Daniel Trebbien --- 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

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 --- Comment #10 from Daniel Trebbien --- (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

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 Daniel Trebbien changed: What|Removed |Added Attachment #95898|0 |1 is obsolete|

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 --- Comment #9 from Philippe Waroquiers --- An additional note: on x86 linux, valgrind gdbserver only reports the Xfer:features:read+ supported if --vgdb-shadow-registers=yes is given. On amd64 linux,

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 --- Comment #5 from Daniel Trebbien --- I contacted Apple Developer Relations about the crash and they informed me that unlike gdb, lldb does not have an initial target definition set, and relies on the gdbserver to tell it which

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 Philippe Waroquiers changed: What|Removed |Added CC|

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 --- Comment #3 from Daniel Trebbien --- The two patches allow LLDB 3.4, 3.5, and 3.6 to debug using the embedded gdbserver on an Ubuntu 14.04.3 'Trusty Tahr' system. The crash on Mac has the following backtrace: ``` Thread 5