Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
Qt Creator 5.0.3, Qt Creator 6.0.0-beta2
-
None
-
Arch LInux with 5.14 kernel
QtCreator 5.0.3/6.0.0-beta2
NDK 21.3.6528147, also tried with 20.1.5948944, 22.1.7171670
Qt 5.15.2
I am targeting Android 11 on official image, and Android 11 on real device.
-
-
d154388f2 (10.0)
-
2022wk32FOQtforAndroid, 2022wk34FOQtforAndroid, 2022wk36FOQtforAndroid, 2022wk38FOQtforAndroid, 2022wk40FOQtforAndroid, 2022wk42FOQtforAndroid, 2023wk02FOQtforAndroid, 2022wk44FOQtforAndroid, 2022wk46FOQtforAndroid, 2022wk48FOQtforAndroid, 2022wk50FOQtforAndroid, 2022wk52FOQtforAndroid, 2023wk04FOQtforAndroid, 2023wk06FOQtforAndroid
Description
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 add Component.onCompleted block in the QML side with a log, it is working as expected and I can even hit a breakpoint there.
I have attache some logs from debugger window. I have tried to update/downgrade QtCreator, NDK, gdb, python, but without any significant changes.
Attachments
Issue Links
- relates to
-
QTCREATORBUG-28141 When debugging on an android device, the default debugger stops at qml breakpoints but not at C++ breakpoints
-
- Closed
-
Gerrit Reviews
For Gerrit Dashboard: QTCREATORBUG-26592 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
464276,4 | Android: add "threads" command for jdb settelment | 10.0 | qt-creator/qt-creator | Status: MERGED | +2 | 0 |