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

[CodesInChaoss]

@CodesInChaoss

the above helped

1. install dos2unix
2. cd android && dos2unix ./gradlew

(...)) f**** !

[CodesInChaoss]

@CodesInChaoss
at least now it compiled (..)

Now.. to debug.. over a network... DO I DARE?

[CodesInChaoss]

@CodesInChaoss

"could not determine debugger type"

Now what the heck is that

[CodesInChaoss]

https://stackoverflow.com/questions/75659675/qt-creator-could-not-determine-debugger-type-android-debugger

come one.... this has beeen YEARS AGO...

I've just f trying to DEBUG here....

[CodesInChaoss]

@CodesInChaoss ON Linux QT Creator 12 keeps toggling off and off and meessing up with debugger settings same as on Windows

[CodesInChaoss]

@CodesInChaoss

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.

[CodesInChaoss]

by the way the most recent issue was resolved by ```
apt install libncurses5

[CodesInChaoss]

@CodesInChaoss

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.....

[CodesInChaoss]

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

[CodesInChaoss]

@CodesInChaoss

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

[CodesInChaoss]

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

@CodesInChaoss

woaaah.... on one occasion we caught a single breakpoint.... with all the sigfaults flying by... same as on Windows

[CodesInChaoss]

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 all

[CodesInChaoss]

@CodesInChaoss

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

[CodesInChaoss]

@CodesInChaoss After 4 minutes have passed

[CodesInChaoss]

@CodesInChaoss exactly same stuff as on Windows, with an offiial Qt sample app

[CodesInChaoss]

@CodesInChaoss

LLDB 'works' only in arm not aaarch64 and on same grounds as gdb. debugging is not possible due to all the sigfaults and delays

[CodesInChaoss]

@CodesInChaoss

switched mobile devices, same shit on another mobile

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

[CodesInChaoss]

@CodesInChaoss

no luck either.

By the way, can anyone tell me why API 31 ABI Clang compilers are missing?