I finally just decided to let LLDB run until it finished what ever it wanted to do. After consuming 7.65GB worth of RAM QtCreator was able to finally show me the variables. What do I need to report back to QtBug reports to get this looked at? It really breaks the ability to debug our codes. This was with LLDB version lldb-310.2.37 on OS X 10.8.5 (Xcode 5.1.1 tooling). I also tried LLDB 3.6 on Ubuntu 14.04 and while the memory load did not happen, LLDB spun for a bit then just crashes.
Thanks Mike Jackson On Aug 31, 2015, at 10:45 AM, Michael Jackson <[email protected]> wrote: > We are trying to use the LLDB debugger under OS X 10.10.5 with Xcode 6.4 for > our project. When using the QtCreator 3.5 release and attempting to stop at a > break point LLDB spins up to 100% CPU and eventually uses all the memory on > the machine (About 8 GB). I eventually have to force quit LLDB and basically > can not debug. The version of LLDB that comes with Xcode 6.4 is 330.0.48. > > Has anyone else seen this problem with QtCreator? If I generate the same > project as an Xcode project then I have no problems stopping at breakpoints > and no memory issues. > > Thanks > Mike Jackson > BlueQuartz Software _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
