[Qt-creator] 4.10.1 release?
Denis Rouzaud
denis.rouzaud at gmail.com
Tue Oct 8 09:28:47 CEST 2019
Hi André,
Many thanks for your detailed answer.
I could not find anything more valuable than the raw dump of the debugger
https://gist.githubusercontent.com/3nids/7a709f8d0a301f6623fc5ed02d1f62a2/raw/7b144820ed14740ae611fda2a69e28836aa8f919/Qt%2520Creator%2520LLVM%2520debugger%2520does%2520not%2520stop%2520at%2520breakpoint
Let me know if you prefer that I open an issue.
Best wishes and thanks again,
Denis
Le lun. 7 oct. 2019 à 19:19, André Pönitz <apoenitz at t-online.de> a écrit :
> On Mon, Oct 07, 2019 at 03:11:13PM +0200, Denis Rouzaud wrote:
> > No need to apologize :)
> >
> > I have tried out the snapshot, but I guess I have another issue with my
> > setup as the debugger isn't stopping at breakpoints anymore.
> > I might have messed up with my Python installations in brew -- brew, I
> love
> > the idea, I hate it at every update ;)
>
> The Python installed by Brew is independent of the Python used by
> LLDB, which in turn is bundled with XCode.
>
> So unless there's some environment variable set or such, the Brew
> installation should not be responsible for what you see.
>
> Feel free to open a bugreport at bugreports.qt-project.org and attach the
> debugger log (contents of right pane of Windows->View ->Debugger Log)
> and/or send me that in private mail.
>
> Maybe some explanation is in order:
>
> Part of the issue here was that XCode/LLDB unexpectedly switched from
> Python 2 to Python 3. Most of the Python glue code Creator uses for
> interfacing the "native" debuggers (LLDB, GDB, CDB) actually works with
> both Python 2(.7) and and 3(.3+), but there have been a few items
> in LLDB-only code that were 2-only, as LLDB was so far 2-only.
>
> The second problem was that the event reporting of LLDB changed,
> de-railing the state tracking in the integration.
>
> What you report now ("starts, but breakpoints are not hit") was the
> state we've witnessed locally between fixing the first and the
> second part. This /could/ mean, that the fix for the second part
> was not sufficient for your setup.
>
> Andre'
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20191008/e8ed947e/attachment.html>
More information about the Qt-creator
mailing list