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

[CodesInChaoss]

@CodesInChaoss

[CodesInChaoss]

@CodesInChaoss

so we've downloaded by hand; looking good;

but

The Kits... not so much...

[CodesInChaoss]

Restarting QT Creator help for the kits to properly initialize:

now the only warning is that a device is missing.. well because it's missing as of now

[CodesInChaoss]

@CodesInChaoss

We've got a single Multi-Abi kit, let's look inside

same settings as on Windows.

we would switch compiler to aarch64, which we believe should be by default by now. Few 32 bit devices around.

Now the question.. on Linux... we should be after LLDB correct? not gdb

it's the freedom oriented realm where all the Linux level latest goodies are expected to shine, right?

Let the Microsoft burdens be upon us no more.

Fingers crossed.

let's try to debug.

[CodesInChaoss]

@CodesInChaoss

eh.. it's been long since I've seen password field neither encrypted nor 'asterixed'...

[CodesInChaoss]

Yet another bug

Subversion sub-system would recognize that the 'svn' command might not be available and indicate in red.

When subversion is installed on system it would be red no more... but QT Creator 12 would still deem the sub-version NOT TO BE CONFIGURED.

No error message. 'svn' in red NO MORE.

only once user provided an explicit absolute path would Creator assume SVN to be configured and shown the -subversion- sub-menu in Tools.

[CodesInChaoss]

Even on Linux, after a single restart of the machine the Debugger settings within of a Kit - these were GONE.

haven't tried to debug yet.

[CodesInChaoss]

@CodesInChaoss

no idea what it's about?

[CodesInChaoss]

@CodesInChaoss it's f*** nightmare the QT experience coooome oonnnnn..

[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