I'd like to take it on because the gdb helpers often go bonkers when inspecting more complex data structures. Guess that's more due to limitation on the aged gdb and it's gdb/mi. As there are two ways to integrate lldb my question to you is which one you prefer.
1. Integrating the lldb api (LLDB.frame). (Which is obviously an IPC engine and code for that already exists. Unfortunately the host/guest ipc code is quite outdated. At least in the master branch) 2. Integrating the python interface. (just like the current gdbengine does right now). Hey, maybe I could even reuse some of the scripts there. Whaddaya say? greetz, mike p.s.: I already got the 2. version as far as launching the executable and halting at a break point :) On Aug 22, 2012, at 9:32 AM, <[email protected]> wrote: > > Michael Seydl wrote: >> Just wanted to know if LLDB support is still on the radar. Is anyone >> actively working on this? > > It is on the radar, but nobody is actively working on it. > > I compile (or try to compile) LLDB it every two or three months on Linux. > Last time it went well, but I got immediate crashes when attempting to do > anything with it (that was "standalone", outside Creator). > > I understand that LLDB is primarily targeted at (or, rather, its current > developers > are primarily targeting) Mac and it works better there, but replacing GDB by > LLDB _on Mac only_ does not sound like a big advantage from a Qt Creator > point of view (not to mention that someone would have to do the work). > > Andre' _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
