Unable to debug Android App (Windows + Qt Creator 12 + LLDB)
-
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.
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.
-
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.
This post is deleted! -
This post is deleted!
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.
-
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.
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.
-
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.
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?
-
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?
That'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 ?
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.
-
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.
also 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....
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.
-
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.
Turns 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'?
Loving the overall EXPERIENCE
-
Loving the overall EXPERIENCE
Do I DARE to tap the first button?
-
Do I DARE to tap the first button?
Why all my KIts' settings get WIPED OUT after the crash?
-
Why all my KIts' settings get WIPED OUT after the crash?
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?
-
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?
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...
-
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...
otherwise it would just remain stuck at ```
D libGRIDNEToken_arm64-v8a.so: QML Debugger: Waiting for connection on port 51672...forever -
otherwise it would just remain stuck at ```
D libGRIDNEToken_arm64-v8a.so: QML Debugger: Waiting for connection on port 51672...foreverI'm also getting segmentation faults in 'binder:X' threads on UI interactions.
Yet again, if I ignore these the app runs FINE.
ideas?
It's like tapping on an UI element is almost guaranteed to result in such a SigFault.
-
I'm also getting segmentation faults in 'binder:X' threads on UI interactions.
Yet again, if I ignore these the app runs FINE.
ideas?
It's like tapping on an UI element is almost guaranteed to result in such a SigFault.
@CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):
I'm also getting segmentation faults in 'binder:X' threads on UI interactions.
Yet again, if I ignore these the app runs FINE.
ideas?
It's like tapping on an UI element is almost guaranteed to result in such a SigFault.
The moment one pastes anything to
QT Creator crashed, Lo and Behold
On my way to reconfigure everything anew.
this feels like an early Alpha of some wanna-be development framework not something that has been around for many many years.
Something I paid for.
-
@CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):
I'm also getting segmentation faults in 'binder:X' threads on UI interactions.
Yet again, if I ignore these the app runs FINE.
ideas?
It's like tapping on an UI element is almost guaranteed to result in such a SigFault.
The moment one pastes anything to
QT Creator crashed, Lo and Behold
On my way to reconfigure everything anew.
this feels like an early Alpha of some wanna-be development framework not something that has been around for many many years.
Something I paid for.
@CodesInChaoss I am pretty sure that it is mostly related to the update process
-
@CodesInChaoss I am pretty sure that it is mostly related to the update process
yeah sure but for the fact I've wiped out everything QT related.
- QT has been wiped CLEAN the entire QT folder
- everything in AppData QT related WIPED clean as well.
- NDK/ SDK everything installed anew
- same stuff on a fresh VM (like I've explaiend)
