Unable to debug Android App (Windows + Qt Creator 12 + LLDB)
-
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.
-
eh.. it's been long since I've seen password field neither encrypted nor 'asterixed'...
-
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.
-
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.
-
no idea what it's about?
-
@CodesInChaoss it's f*** nightmare the QT experience coooome oonnnnn..
-
-
@CodesInChaoss
at least now it compiled (..)Now.. to debug.. over a network... DO I DARE?
-
-
come one.... this has beeen YEARS AGO...
I've just f trying to DEBUG here....
-
@CodesInChaoss ON Linux QT Creator 12 keeps toggling off and off and meessing up with debugger settings same as on Windows
-
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.
-
by the way the most recent issue was resolved by ```
apt install libncurses5 -
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.....
-
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
-
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
Pay attention... throwing in the very same thread as previously on Windows... in an official QT sample app, totally irrelevant to our app -
woaaah.... on one occasion we caught a single breakpoint.... with all the sigfaults flying by... same as on Windows
-
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 -
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
