Unable to debug Android App (Windows + Qt Creator 12 + LLDB)
-
@CodesInChaoss After 4 minutes have passed
wrote on 25 Feb 2024, 13:16 last edited by@CodesInChaoss exactly same stuff as on Windows, with an offiial Qt sample app
-
@CodesInChaoss exactly same stuff as on Windows, with an offiial Qt sample app
wrote on 25 Feb 2024, 13:23 last edited byLLDB 'works' only in arm not aaarch64 and on same grounds as gdb. debugging is not possible due to all the sigfaults and delays
-
LLDB 'works' only in arm not aaarch64 and on same grounds as gdb. debugging is not possible due to all the sigfaults and delays
wrote on 25 Feb 2024, 13:34 last edited by -
wrote on 25 Feb 2024, 13:46 last edited by CodesInChaoss
So we are now running both Linux and Windows 11.
We are having mobile devices from multiple brands targeting API 31.
The problem is reproducible with QT sample apps.
anyone? QT?
- Qt 5.15.16
- QT Creator 12 (the online installer does NOT give us access to older builds)
- evaluated both GDB and LLDB both local and remote
- attempting to debug Qt official Clock sample app
- we've tried targeting 32 and 64bit ABIs
These are all brand new fresh installations of Windows 11 and Ubuntu.
-
So we are now running both Linux and Windows 11.
We are having mobile devices from multiple brands targeting API 31.
The problem is reproducible with QT sample apps.
anyone? QT?
- Qt 5.15.16
- QT Creator 12 (the online installer does NOT give us access to older builds)
- evaluated both GDB and LLDB both local and remote
- attempting to debug Qt official Clock sample app
- we've tried targeting 32 and 64bit ABIs
These are all brand new fresh installations of Windows 11 and Ubuntu.
wrote on 25 Feb 2024, 14:06 last edited byno luck either.
By the way, can anyone tell me why API 31 ABI Clang compilers are missing?
-
no luck either.
By the way, can anyone tell me why API 31 ABI Clang compilers are missing?
wrote on 25 Feb 2024, 14:10 last edited byok I know, 31 API compilers are only within NDK 25
-
ok I know, 31 API compilers are only within NDK 25
wrote on 25 Feb 2024, 14:31 last edited by CodesInChaoss
compiler settings looking GOOD, right? -
compiler settings looking GOOD, right?wrote on 25 Feb 2024, 14:46 last edited by CodesInChaossFolks really counting on you as otherwise wev'e got to spend 4K EURO on a yearly license from QT for them to at least offer us a helpful hand.... just trying to debug the sample Clock app....
-
Folks really counting on you as otherwise wev'e got to spend 4K EURO on a yearly license from QT for them to at least offer us a helpful hand.... just trying to debug the sample Clock app....
wrote on 25 Feb 2024, 23:26 last edited byIs anyone here actually using QT 5.15.16 (the latest commercial version from the 5x branch) ?
All segmentation faults appear on 4 distinct Android 13-14 devices I've tried.
On android 10 there are no segmentation faults. BUT debugging either does not work at all in most cases OR why by chance when it kick-in at all then this happens after a delay lasting minutes after the app has long launched and been executing code. ONCE today it happened that a breakpoint hit fist line in main FIRST time in a week and that happened on Android 10.
-
Is anyone here actually using QT 5.15.16 (the latest commercial version from the 5x branch) ?
All segmentation faults appear on 4 distinct Android 13-14 devices I've tried.
On android 10 there are no segmentation faults. BUT debugging either does not work at all in most cases OR why by chance when it kick-in at all then this happens after a delay lasting minutes after the app has long launched and been executing code. ONCE today it happened that a breakpoint hit fist line in main FIRST time in a week and that happened on Android 10.
wrote on 26 Feb 2024, 06:34 last edited by -
Having read through this thread, I must say: Sorry! I understand your frustration and feel your pain.
This issue is a bug, and not related to a local configuration problem. Thanks a lot for your patience and effort in trying alternatives and troubleshooting.I have been observing and reproducing Qt Creator landing in the disassembler since November 2023. Rremote debugging on Android is complex - I haven't been able to pin it to a specific reason. This needs more attention, I fully agree. I'll channel it internally and keep you posted.
I trust you understand that this is not a trivial matter. It may take a little while, until it's nailed down and solved.
-
wrote on 26 Feb 2024, 08:28 last edited by CodesInChaoss
Plain and simple - on which configuration would 5.15.16 debugging work with an Android device.
We would buy and invest into the VERY EXACT configuration.
Exact mobile device/ OS, PC setup, QT Version.
We would also pay for the hint to anyone who provides an effective solution. Payment today.
-
wrote on 26 Feb 2024, 08:32 last edited by CodesInChaoss
Axel, thank you yet still - we've got a client base which expects us to have the development rolling.
Kindly please advise on what configuration we would be able to use 5.15.16 with an Android setup, we would just like to be able to debug.
If we wouldn't be able to have 5.15.16 working then kindly PLEASE advise which QT version in the 5.X branch to use.
I'm having one developer rolling back to QTC 11 without avail through QTC 10,. he's now o QTC8
We would like to use Qt 5.15.16 with all the bug fixes, the very reason why we bought into QT commercial license to begin with, is that possible?
Please. Thank you so much -
wrote on 26 Feb 2024, 08:39 last edited by CodesInChaoss
@Axel-Spoerl
Are you / is Qt able to provide us with a working VM/ docker image on which debugging with Qt 5.15.16 would work. Or is that asking too much?We can pay. Money is NOT an issue.
-
@Axel-Spoerl
Are you / is Qt able to provide us with a working VM/ docker image on which debugging with Qt 5.15.16 would work. Or is that asking too much?We can pay. Money is NOT an issue.
wrote on 26 Feb 2024, 09:43 last edited by@Axel-Spoerl how is 5.15.16 support / Qt Creator
when considering debugging from Apple M2? -
so since Android SDK with API 31 EMPLOYS Java class version 61 objects for its components this IMPLIES a requirements for JDK version 17.
QT ... kindly update your docs?
wrote on 26 Feb 2024, 11:29 last edited by TomZ@CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):
QT ... kindly update your docs?
Please note that Qt has an actual jira bugtracker. https://bugreports.qt.io/ I expect that direct actionable issues you find are better traceable there.
-
Plain and simple - on which configuration would 5.15.16 debugging work with an Android device.
We would buy and invest into the VERY EXACT configuration.
Exact mobile device/ OS, PC setup, QT Version.
We would also pay for the hint to anyone who provides an effective solution. Payment today.
wrote on 26 Feb 2024, 11:33 last edited by@CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):
We would also pay for the hint to anyone who provides an effective solution. Payment today.
you might want to contact kdab.com with such questions. I think they have the most expertise in such matters. And they are simply a commercial company so it should be a relatively simple question to get such a service.
-
@CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):
We would also pay for the hint to anyone who provides an effective solution. Payment today.
you might want to contact kdab.com with such questions. I think they have the most expertise in such matters. And they are simply a commercial company so it should be a relatively simple question to get such a service.
Since the OP refers to a commercial license, there is commercial support available.
The root cause could be unrelated to Qt, but Qt Creator should at least come up with a meaningful error message.
Landing in the disassembler, instead of the debugger for no obvious reason (which I can reproduce on openSuSE Linux and Windows) is likely a bug in Qt and needs to be fixed.I have worked around it in some cases by throwing a lot of
qDebug()into the pie. Those are always printed correctly. Such immediate workarounds and some deeper troubleshooting are available with commercial support. -
Since the OP refers to a commercial license, there is commercial support available.
The root cause could be unrelated to Qt, but Qt Creator should at least come up with a meaningful error message.
Landing in the disassembler, instead of the debugger for no obvious reason (which I can reproduce on openSuSE Linux and Windows) is likely a bug in Qt and needs to be fixed.I have worked around it in some cases by throwing a lot of
qDebug()into the pie. Those are always printed correctly. Such immediate workarounds and some deeper troubleshooting are available with commercial support.wrote on 26 Feb 2024, 12:05 last edited by CodesInChaossAs of now we are on the "Start Up License for 600$ per seat" and as we've learned the hard way it does not include Technical Support.
All we want is to debug......
Can anyone advise on a setup which would allow for debugging (QT 5.15.16 and Android API 31)
Or at least tell us if we would be able to work from an Apple Sillicon setup? We would like to avoid porting the entire app to Qt 6 as of now... we simply want to debug that's all.
we've tried the official sample apps to no avail. we use fresh installs of windows and linux.
-
As of now we are on the "Start Up License for 600$ per seat" and as we've learned the hard way it does not include Technical Support.
All we want is to debug......
Can anyone advise on a setup which would allow for debugging (QT 5.15.16 and Android API 31)
Or at least tell us if we would be able to work from an Apple Sillicon setup? We would like to avoid porting the entire app to Qt 6 as of now... we simply want to debug that's all.
we've tried the official sample apps to no avail. we use fresh installs of windows and linux.
wrote on 26 Feb 2024, 12:10 last edited by CodesInChaossSo to be on-point, which latest
- QT Creator version
- QT 5.* branch
- Windows/Linux version
triplet
could be used to debug say an official 'clock' app targeting Android API 31 (min required by play store as of now). We would go from there. That's all we want to know.
And if Windows/Linux can't be used then would Mac and apple silicon/iOS coupling be any better? We would then work on mac and simply recompile for Android
134/169