Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
Qt Creator 8.0.0
-
None
-
Qt Creator 8.0.0
Based on Qt 6.3.1 (GCC 10.3.1 20210422 (Red Hat 10.3.1-1), x86_64)
Built on Jul 19 2022 07:57:43
From revision 5c341854e0
ubuntu 20.04 host, oppo android 11 device.
-
Android
-
d154388f2 (10.0)
Description
I can reproduce this with the 'heartrate game' demo, setting breakpoints in main.qml Component.onCompleted:' and in main.cpp line 16.
In 'Run settings' -> 'Debugger Settings', I have checked both 'Enable C++' and 'Enable QML'.
I got around this by: Manage kits -> debugger -> change from the default debugger from:
Android debugger (Multi ABI, NDK 23.1.7779620) LLDB
to:
Android debugger (Multi ABI, NDK 23.1.7779620) GDB
FYI, for more complex projects, once you change from LLDB to GDB, when you start debugging, you get lots of popup windows reporting SIG33, which is something android does. I ended up turning this off by:
edit -> preferences -> Debugger -> GDB -> uncheck the box labelled "Show a message box when receiving a signal".
Attachments
Issue Links
- relates to
-
-
- Reported
-
Gerrit Reviews
| For Gerrit Dashboard: QTCREATORBUG-28141 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 464268,1 | Android: use unix socket for lldb-server communication | 10.0 | qt-creator/qt-creator | Status: ABANDONED | +1 | 0 |
| 464276,4 | Android: add "threads" command for jdb settelment | 10.0 | qt-creator/qt-creator | Status: MERGED | +2 | 0 |