Andre, that works, thank you!
2014-09-28 20:58 GMT+04:00 André Pönitz <apoen...@t-online.de>:
> On Sun, Sep 28, 2014 at 06:30:46AM +0400, Dmitrii Volosnykh wrote:
> > Hi,
> >
> > I am unable to debug C++ code using LLDB on Mac OS X (10.9.5). Xcode
> 6.0.1
> > Command Line Tools are installed. I use latest Qt 5.3.2 release with the
> > corresponding QtCreator 3.2.1. The compiler in the toolchain is:
> >
> > $ clang --version
> > Apple LLVM version 6.0 (clang-600.0.51) (based on LLVM 3.5svn)
> >
> > $ lldb --version
> > lldb-320.4.124.10
> >
> > I build 64bit code. Debugging C++ is enabled in the Run configuration.
> > It just hangs at about 2/5 of the overall length of progress bar.
> >
> > Can't figure out what I am missing. Yes, I've cloned default kit and set
> > the debugger to LLDB.
> >
> > Any info on how to make debugging possible is highly appreciated.
>
> The LLDB threading startup requirements have changed, causing the
> previously used command sequence to hang. The issue has been addressed
> in both Qt Creator 3.2 and master branch.
>
> The patch touches one file with python code, you could apply it
> locally without waiting for the next release. The relevant part is:
>
> --- a/share/qtcreator/debugger/lldbbridge.py
> +++ b/share/qtcreator/debugger/lldbbridge.py
> @@ -667,8 +667,9 @@ class Dumper(DumperBase):
> def runEngine(self, _):
> + self.prepare()
> s = threading.Thread(target=self.loop, args=[])
> s.start()
>
> - def loop(self):
> + def prepare(self):
> error = lldb.SBError()
> listener = self.debugger.GetListener()
>
> @@ -710,5 +711,7 @@ class Dumper(DumperBase):
> self.report('pid="%s"' % self.process.GetProcessID())
> self.reportState("enginerunandinferiorrunok")
>
> + def loop(self):
> event = lldb.SBEvent()
> + listener = self.debugger.GetListener()
> while True:
>
> Andre'
>
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
