C++ Debugger refuse to work while QML does its job
-
Hi,
I am trying for several hours force debugger to work. I have cleaned my Qt/Android installation and started from scratch. I am using 64 bit Arch Linux with QtCreator 5.0.3 and Qt 5.15.2. Everything is up to date (08.11.2021).I am creating an empty CMake/QtQuick project and then run Debug build with it. What I expecting is that breakpoint at the beginning of a main function will be reached at some point, but that isn't happening.
If I addComponent.onCompleted
block in the QML side it is working as expected.Except that everytime little pop-up is shown - waiting for debugger, and I am able to interrupt and resume execution but that's it.
Here is debugger log with (I think) most interesting parts: https://pastebin.com/yPhim4Tv
I can post full log as well, if it will be requested.What I have already tired:
- look for similar issues on the SO, QtForum, ask Uncle Google
- add debug flags to compiler -
-g -ggdb -O3
- use default/custom/minimal set of options for gdb/gdb extended
- change system link
/usr/bin/python
to point to python2 instead of python3 - use system QtCreator instead of official one (also 5.0.3 but GCC and Qt versions are newer)
- use 6.0.0-beta2 QtCreator
- use older NDK (20.1.5948944) and newer one (22.1.7171670, 23.1.7779620 and 23.0.7599858) - current one is 21.3.6528147. With older nothing changes. New ones (23) fail to produce package (there is no
arm-linux-androideabi-strip
binary in the toolchain directory) - reboot both PC and Android device
- use x86_64 emulator with official Android system image
Only clue I have is this issue with python script execution, but I have no idea where to go next with that. I want to ask if anyone had similar problems or would like to give me a hint what to do next?
Thank you. -
Hi Jarek, did you figure this out? I have the same issue.
-
this might help you: https://forum.qt.io/topic/131886/hit-c-breakpoints-on-android