Unable to debug Android App (Windows + Qt Creator 12 + LLDB)

[CodesInChaoss]

here is what I did
I uninstalled the app with
adb uninstall com.your.package

just as advised in https://stackoverflow.com/questions/49148823/c-c-debugger-does-not-work-on-android-studio-3-0-1

(Android Studio issues 2018)

Now, the app got deployed again, this time crashing no more... BUT....

1. all my breakpoints in the initial sequence were OMITTED
2. the app kept spinning for like 10 seconds before everything froze (presumably debugger kicking in)
3. after (2-3 MINUTES) debugger attached and the app froze in what looked to me as a random ASM line (not related to my code). Those lines are related to android.os.perfdebug

Now my breakpoints are hit.

So I guess my questions are:

• how to make the app actually WAIT for the debugger to attach ? It's like with QT Creator 10 Community Addition and GDB instead of LLDB that was normal and anticipated.
• how to prevent breakpoints in some random to me places from firing ? I presume some exception in android-level performance counters related to graphics
• how to make it all faster - 2-3 minutes for the debugger to kick in? come on

[CodesInChaoss]

I've triple checked that 'wait for debugger' is checked on my Android device.

1. the app launches
2. it shows a white bar that it's waiting for debugger to attach>
   at this point in console it would say

I System.out: Debugger has connected
I System.out: waiting for debugger to settle...
I System.out: waiting for debugger to settle...
I System.out: debugger detached?

3. the app KEEPS RUNNING for (5-10 seconds) after which it freezes.
4. during that period NO BREAKPOINTS would ever be hit
5. during that time Creator keeps showing that it's connecting.
6. Creator would connect after 2-3 minutes.
   At which point in console it would say

CONNECT: success adb://pbx4mn555hi7ojyx:5039 platform: remote-android TrueW AudioTrack: restartIfDisabled(304): releaseBuffer() track 0x7e628ce800 disabled due to previous underrun, restarting

Running latest Creator (commercial license). 5.15.16

[CodesInChaoss]

It keep 'breaking' in some random looking ASM code. (but I know these are from lldb "android.os.perfdebug.PerfDebugMonitorImpl" for the most of it).
Now it doesn't even show the source file location.
It doesn't output any info, what kind of a signal caused this, nothing.

How to proceed?

My breakpoints are hit as well.

[CodesInChaoss]

@CodesInChaoss
I've managed to see stack:" "

How do I stop QT Creator 12 breaking at this location even once a second

[CodesInChaoss]

Tried adding an exception to LLDB through custom settings to avoid this 'namespace' to no avail.

[CodesInChaoss]

@CodesInChaoss

My QT Creator just crashed and all my Kit settings are gone... it's all way too ridiculous.

[Ronel_qtmaster]

@CodesInChaoss Have you enabled USB debugging on your phone?

[CodesInChaoss]

@Ronel_qtmaster that's a joke right

[CodesInChaoss]

@Ronel_qtmaster
I'll also give you one: no, I've enabled debugging on my TV and Fridge instead.

[Ronel_qtmaster]

@CodesInChaoss Check if it is working with GDB as well before drawing conclusions

[CodesInChaoss]

@Ronel_qtmaster

I'm not drawing conclusions in regards to performance of LLDB since I've used LLDB manually in projects not involving QT already.

What kind of conclusions do you have on mind the situation is depicted in detail already.

[Ronel_qtmaster]

@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?

[CodesInChaoss]

@Ronel_qtmaster

Everything comes with defaults delivered by QT Creator 12, clean install of Windows.

[Ronel_qtmaster]

@CodesInChaoss LLDB is for linux, use GDB for windows
check this https://doc.qt.io/qtcreator/creator-debugger-engines.html

[CodesInChaoss]

@Ronel_qtmaster

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 87f1315dfbea7c137aa2e6d362dbb457e388158d

[CodesInChaoss]

As 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:

[Ronel_qtmaster]

@CodesInChaoss Do you mean that you have installed lldb with the online installler?

[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]

This post is deleted!

[CodesInChaoss]

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.