https://bugs.kde.org/show_bug.cgi?id=368603
--- Comment #11 from RJVB <rjvber...@gmail.com> --- I'll try tomorrow, but how do you handle the case where you cannot determine the version of a perfectly acceptable lldb-mi? Again, the user may not have much choice to install a patched lldb-mi (think users on OS X). As to using liblldb: this *is* the preferred way to write a GUI for lldb. Pretty sure it's how Xcode interfaces to the debugger; there's also a (commercial) GUI for lldb that almost certainly does the same thing. Let's be honest, it's the most direct way to control the debugger; rather than figuring out how to control an existing driver that's tailored for another kind of application you send exactly the commands you want, without having to parse text replies which may not be perfectly adequate for what you want. Best you can do in this aspect is ask on the lldb ML, to get an uptodate opinion and hopefuly also some feedback on how lldb-mi is perceived. When I asked I got a strong impression it was seen as a 2nd-class citizen that existed only for Eclipse and that would likely never evolve towards a full MI implementation. -- You are receiving this mail because: You are watching all bug changes.
