https://bugs.kde.org/show_bug.cgi?id=339658
--- Comment #7 from RJVB <rjvber...@gmail.com> --- It does, at least to some extent but I'm tempted to say it works better for me on OS X than on Linux. I haven't tested it in depth and as far as I've run into issues it's hard to tell which are due to the newness of the plugin, which to the fact it leverages lldb-mi and which to it running on OS X. WHat I can tell is that it's slow (but so is Apple's own lldb from the cli, or even gdb on Linux; lots of data to load and parse I presume). I also encounter regular lldb-mi crashes even when I'm not doing anything (timeouts waiting for input from the plugin?) and sometimes I get an "unexpected reply" error from the plugin which then puts the debug session in some unknown state, obliging me to kill it. Building the lldb plugin does require building and installing lldb because Apple didn't always provide lldb-mi, and I think even now they don't ship the necessary headers and stuff with Xcode. Getting that lldb to function requires code-signing it, which for now requires some manual and painstakingly following of instructions. I'm hoping we can get that sorted out within MacPorts. The biggest hurdle to using this more frequently is the fact attaching to a running process doesn't work (rather, detecting of running processes doesn't work; the list remains empty). When I tried to launch and debug KDevelop itself in order to figure out where the "missing 'pt' translation dictionary" error came from I ended up with a debuggee session that was deadlocked somewhere in the initial steps of loading a QMake project. I ended up using Qt Creator, which does manage to attach to a running application. One thing that could be improved is automatic recognition of app bundle targets. Currently, it attempts to execute the .app directory instead of the bundle exec. That's stuff for a different ticket though. -- You are receiving this mail because: You are watching all bug changes.
