Workaround needed for debugging on Android in 5.3.2
-
wrote on 6 Oct 2014, 19:39 last edited by
I am running Windows 8.1 and enabling mixed QML/C++ debugging like suggested in https://bugreports.qt-project.org/browse/QTCREATORBUG-13006 does not help.
It does not show "gdb timeout" dialog but does not allow to set breakpoints or press pause.
Is there any other workaround?
This is Debugger Log Viw:
t23:30:11.906 [5ms]
I/Qt JAVA ( 7255): DEBUGGER: got pong /data/local/tmp/qt/debug-pong-org.qtproject.example.btscanner
t23:30:11.929 [23ms]
I/Adreno-EGL( 7255): <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: ()
t23:30:11.929
I/Adreno-EGL( 7255): OpenGL ES Shader Compiler Version: E031.24.00.08+13
t23:30:11.929
I/Adreno-EGL( 7255): Build Date: 03/28/14 Fri
t23:30:11.930 [1ms]
I/Adreno-EGL( 7255): Local Branch: 0328_AU200_patches
t23:30:11.930
I/Adreno-EGL( 7255): Remote Branch:
t23:30:11.930
I/Adreno-EGL( 7255): Local Patches:
t23:30:11.930
I/Adreno-EGL( 7255): Reconstruct Branch:t23:30:12.076 [146ms]
D/OpenGLRenderer( 7255): Enabling debug mode 0
t23:30:12.099 [23ms]
D/OpenGLRenderer( 7255): GL error from OpenGLRenderer: 0x502
t23:30:12.101 [2ms]
E/OpenGLRenderer( 7255): GL_INVALID_OPERATIONt23:30:12.214 [113ms]
D/Qt ( 7255): fontdatabases\basic\qbasicfontdatabase.cpp:239 (static QStringList QBasicFontDatabase::addTTFile(const QByteArray&, const QByteArray&, QSupportedWritingSystems*)): FT_New_Face failed with index 0 : 90t23:31:11.824 [59610ms]
sQML Debugger: No application output received in time, trying to connect ...t23:31:15.828 [4004ms]
sQML Debugger: No application output received in time, trying to connect ...t23:31:19.824 [3996ms]
sQML Debugger: No application output received in time, trying to connect ...And it continues so forever.
-
wrote on 14 Oct 2014, 09:57 last edited by
Update. The Android debugger bug appears on another developer's PC (Windows 7 x64).
The bug is in Qt Creator itself, not in the framework:
Qt Creator 3.1.1 (from Qt 5.3.0) works even with newer Qt 5.3.2 and latest Android NDK/SDK.
The bug is NOT fixed in Qt Creator 5.2.2 from Oct 13rd (http://download.qt-project.org/official_releases/qtcreator/3.2/3.2.2/)