Unable to debug Android App (Windows + Qt Creator 12 + LLDB)
-
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
-
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
116/169