Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
Qt Creator 8.0.0
-
None
Description
Used versions
Used Qt version: Qt 6.3.0 from SDK installer
Used test program: qtquickcontrols2.zip, with breakpoints in main.cpp:11 and main.qml:19
Involved C++ debuggers:
- NDK 21.3: GDB 8.3.0
- NDK 22.1: LLDB 11.0.5
- NDK 23.1: LLDB 12.0.8
Test matrix
Row | QtC version (7.0,8.0) |
NDK version (21.3,22.1,23.1) |
Host OS (Win,Linux) |
Device Type arch |
C++ debugging (✔️,❌) |
QML debugging (✔️,❌) |
QML profiling (✔️,❌) |
Notes |
---|---|---|---|---|---|---|---|---|
1 | 7.0 | 21.3 | Win | armeabi-v7a | ✔️ | ✔️ | ✔️ | - |
2 | 7.0 | 21.3 | Win | arm64-v8a | ✔️ | ✔️ | ✔️ | |
3 | 7.0 | 21.3 | Win | x86_64 | ✔️ | ✔️ | ✔️ | |
4 | 7.0 | 21.3 | Linux | arm64-v8a | ? | ? | ? | - |
5 | 7.0 | 21.3 | Linux | x86_64 | ✔️ | ✔️ | ✔️ | - |
6 | 7.0 | 22.1 | Win | armeabi-v7a | ✔️ | ✔️ | ✔️ | Sometimes: On exit breaks on definiton of class whose functions has a breakpoint |
7 | 7.0 | 22.1 | Win | arm64-v8a | ✔️ | ✔️ | ✔️ | - |
8 | 7.0 | 22.1 | Win | x86_64 | ✔️ | ✔️ | ✔️ | - |
9 | 7.0 | 22.1 | Linux | arm64-v8a | ? | ? | ? | - |
10 | 7.0 | 22.1 | Linux | x86_64 | ✔️ | ✔️ | ✔️ | - |
11 | 7.0 | 23.1 | Win | armeabi-v7a | ❌ | ❌ | ✔️ | - |
12 | 7.0 | 23.1 | Win | arm64-v8a | ❌ | ❌ | ✔️ | - |
13 | 7.0 | 23.1 | Win | x86_64 | ✔️ | ✔️ | ✔️ | |
14 | 7.0 | 23.1 | Linux | arm64-v8a | ? | ? | ? | - |
15 | 7.0 | 23.1 | Linux | x86_64 | ❌ | ✔️ | ✔️ | |
16 | 8.0 | 21.3 | Win | armeabi-v7a | ✔️ | ✔️ | ✔️ | Continuing after C++ breakpoint is sometimes disabled |
17 | 8.0 | 21.3 | Win | arm64-v8a | ✔️ | ✔️ | ✔️ | |
18 | 8.0 | 21.3 | Win | x86_64 | ✔️ | ✔️ | ✔️ | |
19 | 8.0 | 21.3 | Linux | arm64-v8a | ? | ? | ? | - |
20 | 8.0 | 21.3 | Linux | x86_64 | ❌ | ✔️ | ✔️ | - |
21 | 8.0 | 22.1 | Win | armeabi-v7a | ✔️ | ✔️ | ✔️ | |
22 | 8.0 | 22.1 | Win | arm64-v8a | ✔️ | ✔️ | ✔️ | |
23 | 8.0 | 22.1 | Win | x86_64 | ✔️ | ✔️ | ✔️ | |
24 | 8.0 | 22.1 | Linux | arm64-v8a | ? | ? | ? | - |
25 | 8.0 | 22.1 | Linux | x86_64 | ✔️ | ✔️ | ✔️ | - |
26 | 8.0 | 22.1 | macOS | arm64-v8a | ✔️ | ✔️ | ? | - |
27 | 8.0 | 23.1 | Win | armeabi-v7a | ❌ | ✔️ | ✔️ | |
28 | 8.0 | 23.1 | Win | arm64-v8a | ❌ | ✔️ | ✔️ | |
29 | 8.0 | 23.1 | Win | x86_64 | ✔️ | ✔️ | ✔️ | |
30 | 8.0 | 23.1 | Linux | arm64-v8a | ? | ? | ? | - |
31 | 8.0 | 23.1 | Linux | x86_64 | ❌ | ✔️ | ✔️ | |
32 | 8.0 | 23.1 | macOS | arm64-v8a | ❌ | ✔️ | ? |
How to prepare tests
In order to be sure that all components for a row in the test matrix are set up correctly, it makes sense to prepare as much as possible.
I create shortcuts for all combinations of QtC and NDK versions:
The shortcuts have a command line like this: <qtcbinary> -settingspath c:\temp\testmatrix_7.0_23.1 -noload UpdateInfo <testproject>
So, that each shortcut has its own settings directory. Then, each shortcut is executed once, and the default NDK and, a suitable default kit is selected.
Run tests
Have for example https://git.qt.io/playground/qtcreator-bug-snippets/-/tree/master/QTCREATORBUG-25030 checked out, and git clean -dxf the repository before each test matrix row.
Repeat the C++ debugging test at least twice per test row (without in-between cleaning of the repo).
Note for Qt Creator 7.0: Set QML debugging and profiling to Enabled in the Build Settings.
Attachments
Issue Links
- relates to
-
QTCREATORBUG-30330 Inform the user of incompatible Android SDK - NDK pairs in the preferences.
- Reported
- mentioned in
-
Page Loading...