Unable to debug Android App (Windows + Qt Creator 12 + LLDB)
-
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.
-
Ok 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.
wrote on 20 Feb 2024, 11:39 last edited byalso getting lots of these on dialog-creations.. what the heck is going on here....
-
also getting lots of these on dialog-creations.. what the heck is going on here....
wrote on 20 Feb 2024, 11:41 last edited by CodesInChaossMy app works fine as long as I keep neglecting and going past all these SIGFaults and Sig33s
what's that?
I really wouldn't like to neglect segmentation faults my code or not.
Why am I seeing these now? With QT Creator 12 and not 10?
Looking forward to some guidance.
-
My app works fine as long as I keep neglecting and going past all these SIGFaults and Sig33s
what's that?
I really wouldn't like to neglect segmentation faults my code or not.
Why am I seeing these now? With QT Creator 12 and not 10?
Looking forward to some guidance.
wrote on 20 Feb 2024, 11:45 last edited byTurns out Sig33 is reserved signal issued by bionic hardware. anyone can confirm, safe to 'handle SIG33 nostop noprint'?
-
Turns out Sig33 is reserved signal issued by bionic hardware. anyone can confirm, safe to 'handle SIG33 nostop noprint'?
wrote on 20 Feb 2024, 11:49 last edited by
Loving the overall EXPERIENCE
-
Loving the overall EXPERIENCE
wrote on 20 Feb 2024, 11:50 last edited byDo I DARE to tap the first button?
-
Do I DARE to tap the first button?
wrote on 20 Feb 2024, 11:52 last edited byWhy all my KIts' settings get WIPED OUT after the crash?
-
Why all my KIts' settings get WIPED OUT after the crash?
wrote on 20 Feb 2024, 11:53 last edited byIt's like I'm debugging on V8 ABI, I need 64 bit compiler and QT Creator keeps reverting settings back to 32bit compiled actually messing up with my settings.
Now, how a regular developer is even to notice?
-
It's like I'm debugging on V8 ABI, I need 64 bit compiler and QT Creator keeps reverting settings back to 32bit compiled actually messing up with my settings.
Now, how a regular developer is even to notice?
wrote on 20 Feb 2024, 11:57 last edited byBy the time I reconfigured everything, it turns our Creator is unable to attach due to ADB being in an 'incompatible state. Thus I'm best off restarting the PC...
-
By the time I reconfigured everything, it turns our Creator is unable to attach due to ADB being in an 'incompatible state. Thus I'm best off restarting the PC...
wrote on 20 Feb 2024, 11:59 last edited byotherwise it would just remain stuck at ```
D libGRIDNEToken_arm64-v8a.so: QML Debugger: Waiting for connection on port 51672...forever
32/169