Unable to debug Android App (Windows + Qt Creator 12 + LLDB)
-
well we know very well BUT that's what QT recommends for 5.15.16, and we want simply to be able to debug above anything else.
wrote on 25 Feb 2024, 09:14 last edited byWe've now compiled OpenSSL 1.1.1 from sources , installed fired up QT Creator 12, the Android SDK autonomous installation process now commenced fine.. let us hope for the best.
Fingers crossed.
-
We've now compiled OpenSSL 1.1.1 from sources , installed fired up QT Creator 12, the Android SDK autonomous installation process now commenced fine.. let us hope for the best.
Fingers crossed.
wrote on 25 Feb 2024, 09:14 last edited by -
wrote on 25 Feb 2024, 09:15 last edited by
-
wrote on 25 Feb 2024, 09:19 last edited by
-
wrote on 25 Feb 2024, 09:21 last edited by
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
-
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
wrote on 25 Feb 2024, 09:24 last edited by
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.
-
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.
wrote on 25 Feb 2024, 09:38 last edited byeh.. it's been long since I've seen password field neither encrypted nor 'asterixed'...
-
eh.. it's been long since I've seen password field neither encrypted nor 'asterixed'...
wrote on 25 Feb 2024, 10:09 last edited byYet 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.
-
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.
wrote on 25 Feb 2024, 11:32 last edited byEven 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.
-
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.
wrote on 25 Feb 2024, 11:33 last edited byno idea what it's about?
-
no idea what it's about?
wrote on 25 Feb 2024, 11:36 last edited by@CodesInChaoss it's f*** nightmare the QT experience coooome oonnnnn..
-
@CodesInChaoss it's f*** nightmare the QT experience coooome oonnnnn..
wrote on 25 Feb 2024, 11:39 last edited by -
wrote on 25 Feb 2024, 11:40 last edited by
@CodesInChaoss
at least now it compiled (..)Now.. to debug.. over a network... DO I DARE?
-
@CodesInChaoss
at least now it compiled (..)Now.. to debug.. over a network... DO I DARE?
wrote on 25 Feb 2024, 12:32 last edited by -
wrote on 25 Feb 2024, 12:34 last edited by
come one.... this has beeen YEARS AGO...
I've just f trying to DEBUG here....
-
come one.... this has beeen YEARS AGO...
I've just f trying to DEBUG here....
wrote on 25 Feb 2024, 12:39 last edited by@CodesInChaoss ON Linux QT Creator 12 keeps toggling off and off and meessing up with debugger settings same as on Windows
-
@CodesInChaoss ON Linux QT Creator 12 keeps toggling off and off and meessing up with debugger settings same as on Windows
wrote on 25 Feb 2024, 12:46 last edited byI 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.
-
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
108/169