Unable to debug Android App (Windows + Qt Creator 12 + LLDB)
-
I've triple checked that 'wait for debugger' is checked on my Android device.
- the app launches
- 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?- the app KEEPS RUNNING for (5-10 seconds) after which it freezes.
- during that period NO BREAKPOINTS would ever be hit
- during that time Creator keeps showing that it's connecting.
- 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, restartingRunning latest Creator (commercial license). 5.15.16
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.
-
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
I've managed to see stack:"
"How do I stop QT Creator 12 breaking at this location even once a second
-
@CodesInChaoss
I've managed to see stack:" "How do I stop QT Creator 12 breaking at this location even once a second
Tried adding an exception to LLDB through custom settings to avoid this 'namespace' to no avail.
-
Tried adding an exception to LLDB through custom settings to avoid this 'namespace' to no avail.
My QT Creator just crashed and all my Kit settings are gone... it's all way too ridiculous.
-
My QT Creator just crashed and all my Kit settings are gone... it's all way too ridiculous.
@CodesInChaoss Have you enabled USB debugging on your phone?
-
@CodesInChaoss Have you enabled USB debugging on your phone?
@Ronel_qtmaster that's a joke right
-
@CodesInChaoss Have you enabled USB debugging on your phone?
@Ronel_qtmaster
I'll also give you one: no, I've enabled debugging on my TV and Fridge instead. -
@Ronel_qtmaster
I'll also give you one: no, I've enabled debugging on my TV and Fridge instead.@CodesInChaoss Check if it is working with GDB as well before drawing conclusions
-
@CodesInChaoss Check if it is working with GDB as well before drawing conclusions
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.
-
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.
@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 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?Everything 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.
@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.htmlyes 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 87f1315dfbea7c137aa2e6d362dbb457e388158dAs 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 87f1315dfbea7c137aa2e6d362dbb457e388158d@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?
@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.16This 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.16When 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.
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.
-
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.
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.
