Unable to debug Android App (Windows + Qt Creator 12 + LLDB)
-
I CANT DEBUG SHIT.
IT"S NOT RELATED TO MY APP.
I"VE JUST TRIED DEBUGGING AND DEPLOYG SAMPLE CLOCK APPLICATION>
BREAKPOINTS DO NOT WORK.
WJHAT DO I DO.
wrote on 25 Feb 2024, 12:49 last edited byby the way the most recent issue was resolved by ```
apt install libncurses5 -
by the way the most recent issue was resolved by ```
apt install libncurses5wrote on 25 Feb 2024, 13:00 last edited byWith the sample CLOCK app by QT.... from LINUX...
Remote LLDB debugging doesn't work at all (QT 5.15.16, QT Creator 12) and with GDB... I get all the regular shit I used to get on windows... same sig faults........ with the sample clock app.....
-
With the sample CLOCK app by QT.... from LINUX...
Remote LLDB debugging doesn't work at all (QT 5.15.16, QT Creator 12) and with GDB... I get all the regular shit I used to get on windows... same sig faults........ with the sample clock app.....
wrote on 25 Feb 2024, 13:01 last edited byLike you may see folks above.. we rather know what we are doing... we resolve all the missing depandancies on the fly.. we switch operating systems on the fly.. it's all SHIT
-
Like you may see folks above.. we rather know what we are doing... we resolve all the missing depandancies on the fly.. we switch operating systems on the fly.. it's all SHIT
wrote on 25 Feb 2024, 13:04 last edited bysee above.. analogclock, sig fauls... LLDB doesn't kick in at all... GDB after significant delay. and sigfaults from QT internals running on android... Redmi 12 Pro targetting Android SDK 31 all according to the min requirements now on play store
-
see above.. analogclock, sig fauls... LLDB doesn't kick in at all... GDB after significant delay. and sigfaults from QT internals running on android... Redmi 12 Pro targetting Android SDK 31 all according to the min requirements now on play store
wrote on 25 Feb 2024, 13:05 last edited by@CodesInChaoss
Pay attention... throwing in the very same thread as previously on Windows... in an official QT sample app, totally irrelevant to our app -
@CodesInChaoss
Pay attention... throwing in the very same thread as previously on Windows... in an official QT sample app, totally irrelevant to our appwrote on 25 Feb 2024, 13:09 last edited bywoaaah.... on one occasion we caught a single breakpoint.... with all the sigfaults flying by... same as on Windows
-
woaaah.... on one occasion we caught a single breakpoint.... with all the sigfaults flying by... same as on Windows
wrote on 25 Feb 2024, 13:11 last edited byit's impossible to place a breakpoint in main (even though there's a dedicated option in Debug sub-menu).
GDB debugging delayed, sig faults all around.
can't get LLDB debugging to work at all -
it's impossible to place a breakpoint in main (even though there's a dedicated option in Debug sub-menu).
GDB debugging delayed, sig faults all around.
can't get LLDB debugging to work at allwrote on 25 Feb 2024, 13:14 last edited bywith LLDB on Linux it's same as on Windows.
app (the sample Clock app by Qt ) keep running for 2-3 minutes already, while the "Launching dbeugger" thing keeps showing.
Now, it's on latest Ubuntu
-
with LLDB on Linux it's same as on Windows.
app (the sample Clock app by Qt ) keep running for 2-3 minutes already, while the "Launching dbeugger" thing keeps showing.
Now, it's on latest Ubuntu
wrote on 25 Feb 2024, 13:16 last edited by@CodesInChaoss After 4 minutes have passed
-
@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.
125/169