Unable to debug Android App (Windows + Qt Creator 12 + LLDB)
-
@CodesInChaoss maybe you are using LLDB the wrong way with qt.
Also, have you checked if it is the right version for your Qt version?
How have you first of all added lldb in qt? which versiion of lldb are using?wrote on 20 Feb 2024, 09:57 last edited byEverything comes with defaults delivered by QT Creator 12, clean install of Windows.
-
Everything comes with defaults delivered by QT Creator 12, clean install of Windows.
wrote on 20 Feb 2024, 10:00 last edited by Ronel_qtmaster@CodesInChaoss LLDB is for linux, use GDB for windows
check this https://doc.qt.io/qtcreator/creator-debugger-engines.html -
@CodesInChaoss LLDB is for linux, use GDB for windows
check this https://doc.qt.io/qtcreator/creator-debugger-engines.htmlwrote on 20 Feb 2024, 10:04 last edited by CodesInChaossyes I've seen this page already BUT it seems that recent versions of QT Creator enforce use of LLDB (also by default) on WIndows. There are tickets in Bug-Reports saying that they've 'transitioned'.
I've always worked with GDB on WIndows with QT Creator, but to all my surprise, after installation of QT Creator 12 (we've transitioned to Commercial License) LLDB was selected and enabled BY DEFAULT on all kits.
So I said to myself, ok - let's go. I knew LLDB was for mac since that's what we've been using for iOS deployment.
lldb version 11.0.5 clang revision 87f1315dfbea7c137aa2e6d362dbb457e388158d llvm revision 87f1315dfbea7c137aa2e6d362dbb457e388158d -
yes I've seen this page already BUT it seems that recent versions of QT Creator enforce use of LLDB (also by default) on WIndows. There are tickets in Bug-Reports saying that they've 'transitioned'.
I've always worked with GDB on WIndows with QT Creator, but to all my surprise, after installation of QT Creator 12 (we've transitioned to Commercial License) LLDB was selected and enabled BY DEFAULT on all kits.
So I said to myself, ok - let's go. I knew LLDB was for mac since that's what we've been using for iOS deployment.
lldb version 11.0.5 clang revision 87f1315dfbea7c137aa2e6d362dbb457e388158d llvm revision 87f1315dfbea7c137aa2e6d362dbb457e388158dwrote on 20 Feb 2024, 10:11 last edited by CodesInChaossAs far as I know, LLDB never (before) came pre-installed on Windows installations alongside with QT Creator, I think.
Now, on windows , all kits deployed by QT Creator , by default have this:
-
yes I've seen this page already BUT it seems that recent versions of QT Creator enforce use of LLDB (also by default) on WIndows. There are tickets in Bug-Reports saying that they've 'transitioned'.
I've always worked with GDB on WIndows with QT Creator, but to all my surprise, after installation of QT Creator 12 (we've transitioned to Commercial License) LLDB was selected and enabled BY DEFAULT on all kits.
So I said to myself, ok - let's go. I knew LLDB was for mac since that's what we've been using for iOS deployment.
lldb version 11.0.5 clang revision 87f1315dfbea7c137aa2e6d362dbb457e388158d llvm revision 87f1315dfbea7c137aa2e6d362dbb457e388158dwrote on 20 Feb 2024, 10:18 last edited by@CodesInChaoss Do you mean that you have installed lldb with the online installler?
-
@CodesInChaoss Do you mean that you have installed lldb with the online installler?
wrote on 20 Feb 2024, 10:18 last edited by CodesInChaoss@Ronel_qtmaster
Well it must have arrived with the online installer, yes, by default since I've used all the default tickers which go for Qt 5.15.16 -
@Ronel_qtmaster
Well it must have arrived with the online installer, yes, by default since I've used all the default tickers which go for Qt 5.15.16wrote on 20 Feb 2024, 10:25 last edited byThis post is deleted! -
@Ronel_qtmaster
Well it must have arrived with the online installer, yes, by default since I've used all the default tickers which go for Qt 5.15.16wrote on 20 Feb 2024, 10:26 last edited by CodesInChaossWhen I choose GDB rebuild the app none of the breakpoints are ever hit GDB reports version 8.3 ( installed by Qt I presume).
The effect with GDB is that the app waits for debugger, the app runs (the breakpoints I set are not hit - in main())
yes yes, it works I'm not a noob, the app has been tested by thousands already.
-
When I choose GDB rebuild the app none of the breakpoints are ever hit GDB reports version 8.3 ( installed by Qt I presume).
The effect with GDB is that the app waits for debugger, the app runs (the breakpoints I set are not hit - in main())
yes yes, it works I'm not a noob, the app has been tested by thousands already.
wrote on 20 Feb 2024, 10:34 last edited byIt's like I've had everything set up and running perfect but something made me update from QT Creator 10 (community edition) towards QT Creator 12 and here I am.
-
It's like I've had everything set up and running perfect but something made me update from QT Creator 10 (community edition) towards QT Creator 12 and here I am.
wrote on 20 Feb 2024, 10:37 last edited byseems as both LLDB and GDB come as part of Android SDK/NDK so these have been installed by QT Creator itself during Android bootstrapping (autonomous).
These things do not come as part of the Online Installer.
-
seems as both LLDB and GDB come as part of Android SDK/NDK so these have been installed by QT Creator itself during Android bootstrapping (autonomous).
These things do not come as part of the Online Installer.
wrote on 20 Feb 2024, 10:44 last edited by CodesInChaossCan anyone else confirm that we are STILL to be using GDB on Windows with QT creator when debugging Android apps, please?
I'm more than fine with just about anything that works.
-
seems as both LLDB and GDB come as part of Android SDK/NDK so these have been installed by QT Creator itself during Android bootstrapping (autonomous).
These things do not come as part of the Online Installer.
wrote on 20 Feb 2024, 10:47 last edited by@CodesInChaoss Qt does not install android sdk and ndk during update.You have to do that externelly so if you have updated Qt it might be possible that your ndk version is conflicting somewhere
-
@CodesInChaoss Qt does not install android sdk and ndk during update.You have to do that externelly so if you have updated Qt it might be possible that your ndk version is conflicting somewhere
wrote on 20 Feb 2024, 10:55 last edited bymy friend,
Above, for a couple of YEARS now.
And I've been using QT when nothing fancy like that was around trust me when I say.
-
my friend,
Above, for a couple of YEARS now.
And I've been using QT when nothing fancy like that was around trust me when I say.
wrote on 20 Feb 2024, 10:57 last edited by CodesInChaossI've been seeing lots and lots of deep sh** when it comes to QT... I've been deep down. Trust me when I say, it's all doomed but I love it but only because I'm a low-level type of a guy.. I can't possibly IMAGINE any typical developer using it. I simply cannot. Not for mobile. And not from WIndows.
-
I've been seeing lots and lots of deep sh** when it comes to QT... I've been deep down. Trust me when I say, it's all doomed but I love it but only because I'm a low-level type of a guy.. I can't possibly IMAGINE any typical developer using it. I simply cannot. Not for mobile. And not from WIndows.
wrote on 20 Feb 2024, 11:04 last edited byThis post is deleted! -
This post is deleted!
wrote on 20 Feb 2024, 11:06 last edited by CodesInChaossDear Ronel I'll tell you that I've even got GDB 'working' for me but it took quite a few ADB commands and manual creation of folders on my Android device, now tell, me is this a unified QT Multi-Platform Development framework?
How a typical developer is supposed to get around these issues?
Why LLDB set by default?
Now I know it's not QT support.
Anyway I'm still looking into making the android app actually not skip the initial breakpoints.
-
Dear Ronel I'll tell you that I've even got GDB 'working' for me but it took quite a few ADB commands and manual creation of folders on my Android device, now tell, me is this a unified QT Multi-Platform Development framework?
How a typical developer is supposed to get around these issues?
Why LLDB set by default?
Now I know it's not QT support.
Anyway I'm still looking into making the android app actually not skip the initial breakpoints.
wrote on 20 Feb 2024, 11:18 last edited byWhen running the app under GDB (Xiaomi device) I'm getting SigSegvs in a thread named "ScoutStat" asm code.
Anyone knows what this might be? It's not part of my app, the app runs fine.
-
When running the app under GDB (Xiaomi device) I'm getting SigSegvs in a thread named "ScoutStat" asm code.
Anyone knows what this might be? It's not part of my app, the app runs fine.
wrote on 20 Feb 2024, 11:25 last edited by CodesInChaossSo yeah.. so it seems that the signals received previously by LLDB (but QT was not showing ANY dialog-boxes) or the actual Signal Code, are in fact segmentation faults coming from something name 'Scout Stat' Anyone knows what this is?
-
So yeah.. so it seems that the signals received previously by LLDB (but QT was not showing ANY dialog-boxes) or the actual Signal Code, are in fact segmentation faults coming from something name 'Scout Stat' Anyone knows what this is?
wrote on 20 Feb 2024, 11:26 last edited byThat's not part of my code and something presumably operating as part of QT ?
-
That's not part of my code and something presumably operating as part of QT ?
wrote on 20 Feb 2024, 11:35 last edited by CodesInChaossOk folks so there's that MAGICAL
'scoutstat' thread, I have no idea what it is that is causing havoc.It must be something related to UI/rendering/UI interactions since the segmentation fault would be signaled only as a result of UI interactions/ UI animations/ preparations.
What's that and why the heck it's sig-faulting on meh
Not my code. And presumably not part of source code that arrive with QT pre-installed since QT does not bring me to these.
23/169