Unable to debug Android App (Windows + Qt Creator 12 + LLDB)
-
@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.
@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?
@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.
@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.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.
-
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.
So 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
-
So 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
We do not have time for bugs to be solved so hopefully there's there's some setup which WOULD work?
-
We do not have time for bugs to be solved so hopefully there's there's some setup which WOULD work?
Gents, we've just tried debugging a latest QT 6.6.2 API mobile app on Android 33 API mobile device..... breakpoints do not work, what the heck is up with Qt?
-
Gents, we've just tried debugging a latest QT 6.6.2 API mobile app on Android 33 API mobile device..... breakpoints do not work, what the heck is up with Qt?
That's what we get when attempting to debug a sample 'cofee machine' QT 6.6 app on Android.
-
That's what we get when attempting to debug a sample 'cofee machine' QT 6.6 app on Android.
@CodesInChaoss I had a spin on Qt 6.6.2 with Qt Creator 12 for Android and saw the same problem with a simple qt example. Will take a detailed look at the issue. Qt 5.15.2 was used in my previous run. It seems a lot of things have been changed in QT for Android build. Unluckily, the newer Qt Creator is not compatible with the old project.
-
@CodesInChaoss I had a spin on Qt 6.6.2 with Qt Creator 12 for Android and saw the same problem with a simple qt example. Will take a detailed look at the issue. Qt 5.15.2 was used in my previous run. It seems a lot of things have been changed in QT for Android build. Unluckily, the newer Qt Creator is not compatible with the old project.
Yeah.. folks.. but tell you what....
We've been also using 5.15.2 previously for our project along with the Community version of Qt.
As you can imagine, a bit frustrated I was, so we bought a brand new Macbook with M2.
Everything works out of the box.
(..) with a damn Android VM.. even no need to attach a phone... the Android VM works crazy fast. Breakpoints keep spinning... no errors.... no assembly shit... no exceptions.. with out own project........
I'll give it a try with real device later on.
But presumably... all Qt user and development base moved to Apple hardware as of recent...
Spend 7 days from dawn till dusk fighting with Windows and Linux.
Buy a Macbook with M2 and have everything resolved.
I mean... breakpoints ARE not hitting within main(), but other than that? it's f*** PERFECT.
as if 100 bugs have been fixed. it simply works as it SHOULD.
Breakpoitns can be dynamically inserted, removed, these fire each time.
but yet again... not as soon as in main()
-
Yeah.. folks.. but tell you what....
We've been also using 5.15.2 previously for our project along with the Community version of Qt.
As you can imagine, a bit frustrated I was, so we bought a brand new Macbook with M2.
Everything works out of the box.
(..) with a damn Android VM.. even no need to attach a phone... the Android VM works crazy fast. Breakpoints keep spinning... no errors.... no assembly shit... no exceptions.. with out own project........
I'll give it a try with real device later on.
But presumably... all Qt user and development base moved to Apple hardware as of recent...
Spend 7 days from dawn till dusk fighting with Windows and Linux.
Buy a Macbook with M2 and have everything resolved.
I mean... breakpoints ARE not hitting within main(), but other than that? it's f*** PERFECT.
as if 100 bugs have been fixed. it simply works as it SHOULD.
Breakpoitns can be dynamically inserted, removed, these fire each time.
but yet again... not as soon as in main()
@CodesInChaoss
Thats good news, glad to hear!
May I ask you, which constellation works on the Mac?
Android SDK / NDB / ABI, Qt Creator & Qt Version?
That will help us to narrow down the issue and fix it asap.
Thanks in advance - and I hope you'll get some rest after 168 sleepless hours ;-) -
Yeah.. folks.. but tell you what....
We've been also using 5.15.2 previously for our project along with the Community version of Qt.
As you can imagine, a bit frustrated I was, so we bought a brand new Macbook with M2.
Everything works out of the box.
(..) with a damn Android VM.. even no need to attach a phone... the Android VM works crazy fast. Breakpoints keep spinning... no errors.... no assembly shit... no exceptions.. with out own project........
I'll give it a try with real device later on.
But presumably... all Qt user and development base moved to Apple hardware as of recent...
Spend 7 days from dawn till dusk fighting with Windows and Linux.
Buy a Macbook with M2 and have everything resolved.
I mean... breakpoints ARE not hitting within main(), but other than that? it's f*** PERFECT.
as if 100 bugs have been fixed. it simply works as it SHOULD.
Breakpoitns can be dynamically inserted, removed, these fire each time.
but yet again... not as soon as in main()
@CodesInChaoss I also moved from a Windows device to a MacBook Pro M1 Arm64 device. (I only had to change the keyboard to mimic Windows/Linux experience).
The best part is that you get a Arm64 Android VM, which is the aarch64 architecture that most Arm Android devices use.
Most likely the VM is faster than any Android Phone you can buy, since the Apple silicon is faster than what Qualcomm is putting out there (for now).
-
We've bought the 'cheap' startup license or I recall 600USD per year per person.
Now, it does not come with technical support (as it tuned out).
As we've learned the hard way that is.
Now, I've forced GDB manually to neglect any segmentation faults (!!!) and Sig33s (..) by typing the custom arguments to QT Creator by hand as copy-pasting would result it to CRASH.
Now I'm able to debug.. I'm not disturbed by QT's internal segmentation faults... I presume? correct me if I'm wrong
@CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):
We've bought the 'cheap' startup license or I recall 600USD per year per person.
Now, it does not come with technical support (as it tuned out).The Small Business License is $499 per year per developer.
On QtWS23 there was an announcement from Qt Keynotes about some improvements in 2024: same price, higher revenue possible and - if I remember right - up to 5 tech support issues.
got an info, that this will be published in march or so. -
Yeah.. folks.. but tell you what....
We've been also using 5.15.2 previously for our project along with the Community version of Qt.
As you can imagine, a bit frustrated I was, so we bought a brand new Macbook with M2.
Everything works out of the box.
(..) with a damn Android VM.. even no need to attach a phone... the Android VM works crazy fast. Breakpoints keep spinning... no errors.... no assembly shit... no exceptions.. with out own project........
I'll give it a try with real device later on.
But presumably... all Qt user and development base moved to Apple hardware as of recent...
Spend 7 days from dawn till dusk fighting with Windows and Linux.
Buy a Macbook with M2 and have everything resolved.
I mean... breakpoints ARE not hitting within main(), but other than that? it's f*** PERFECT.
as if 100 bugs have been fixed. it simply works as it SHOULD.
Breakpoitns can be dynamically inserted, removed, these fire each time.
but yet again... not as soon as in main()
@CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):
But presumably... all Qt user and development base moved to Apple hardware as of recent...
That hardware uses the ARMv8.6-A instruction set, which is what you'll find in most phones too. At least Android, I have no clue about iOs.
Which basically means that you're no longer debugging inside an (CPU) emulator, but basically doing it natively. And indeed I can understand that solves a host of issues.
I'm quite happy for you that this makes you're life a lot easier!
@ekkescorner said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):
On QtWS23 there was an announcement
As someone that hasn't been in contact with sales since the Trolltech / Nokia days, I'm curious if customers "inform" Qtio about which platform they develop on. My thinking here is that if they have an actual insight into the revenue-stream for Android, management can calculate the profit/loss of paying a(nother) developer to in-house work on Android and actually use this stuff. Dogfooding and fixing issues.
I mean, issues like QTBUG-121561 are clearly the result of devs not having enough time for this stuff. It literally is the result of a bugfix being reverted and the old bug showing up again.
This thread shows similarly that dogfooding is not happening, unless Qt devs have no need to run a debugger. -
@CodesInChaoss I also moved from a Windows device to a MacBook Pro M1 Arm64 device. (I only had to change the keyboard to mimic Windows/Linux experience).
The best part is that you get a Arm64 Android VM, which is the aarch64 architecture that most Arm Android devices use.
Most likely the VM is faster than any Android Phone you can buy, since the Apple silicon is faster than what Qualcomm is putting out there (for now).
True.
Just wanted to update you folks that debugging latest real hardware Android devices from MacOS is impossible as well.
I ended up having the very same issues as on Windows.
Sigfaults and straight-into-assembly experience.
For now the best thing we came up with is debugging on Android Simulator running atop of M2.. but for now we cannot get around UDP data exchange limitations as our app uses UDT which runs atop of UDP and we are unable to maintain connectivity.
haven't managed to run on iOS simulator as well due to some strange error throwing which I would repost soon.
-
True.
Just wanted to update you folks that debugging latest real hardware Android devices from MacOS is impossible as well.
I ended up having the very same issues as on Windows.
Sigfaults and straight-into-assembly experience.
For now the best thing we came up with is debugging on Android Simulator running atop of M2.. but for now we cannot get around UDP data exchange limitations as our app uses UDT which runs atop of UDP and we are unable to maintain connectivity.
haven't managed to run on iOS simulator as well due to some strange error throwing which I would repost soon.
@CodesInChaoss
I fully understand, that the Android debugging issue at hand is frustrating. The only thing I can assure is that we are busily working to stabilize it again. You may want to look at the bugreport for some updates.Switching Ndk versions does change the debug behavior, so there is likely an external dependency as well. 25.1.8937393 has brought me a small improvement over 25.2...., albeit not a solution. It'll be helpful to know, which SDK / Ndk and Qt Creator versions are running on the M2 you have mentioned.
As regards your iOS simulator issue, feel free to post a separate thread and tag me. I've got a working environment here. Maybe I can help troubleshooting.
Software Engineer
The Qt Company, Oslo -
@CodesInChaoss
I fully understand, that the Android debugging issue at hand is frustrating. The only thing I can assure is that we are busily working to stabilize it again. You may want to look at the bugreport for some updates.Switching Ndk versions does change the debug behavior, so there is likely an external dependency as well. 25.1.8937393 has brought me a small improvement over 25.2...., albeit not a solution. It'll be helpful to know, which SDK / Ndk and Qt Creator versions are running on the M2 you have mentioned.
As regards your iOS simulator issue, feel free to post a separate thread and tag me. I've got a working environment here. Maybe I can help troubleshooting.
@Axel-Spoerl Just tested a simple group box example.
QtCreator 12.0.2
Ubuntu 22.04
Qt 6.6.2
JDK-17
NDK 21 or 25
Device: Samsung tablet A-8 with Android 13Problem 1: break into disassembler binary with JDK 17. The test case runs fine without breakpoints.
Problem 2: JDK 11 is not supported anymore. If JDK 11 and Qt 5.15.2 are applied, NDK can not be set-up. For Android 13, JDK 11 is the right selection. -
@Axel-Spoerl Just tested a simple group box example.
QtCreator 12.0.2
Ubuntu 22.04
Qt 6.6.2
JDK-17
NDK 21 or 25
Device: Samsung tablet A-8 with Android 13Problem 1: break into disassembler binary with JDK 17. The test case runs fine without breakpoints.
Problem 2: JDK 11 is not supported anymore. If JDK 11 and Qt 5.15.2 are applied, NDK can not be set-up. For Android 13, JDK 11 is the right selection.
