Debugging QML/C++ application in Qt Creator
-
wrote on 27 Oct 2010, 04:21 last edited by
bq.
Chetan, you are using 4.7.0, right?yes as of now I'm on 4.7.0, but will try to get 4.7.1 from git today and revert if debugging works with that
-
wrote on 28 Oct 2010, 18:21 last edited by
Ok
Thanks -
wrote on 29 Oct 2010, 11:13 last edited by
I'm having serious issues trying to download the 4.7.1 from repository :( ... unsuccessful past 2 days, keeps disconnecting or timing out and just aborts. will try again over weekend.
meanwhile, saw "this video ":http://www.youtube.com/watch?v=LD360rT7zkA&fmt=22 on youtube
-
wrote on 6 Nov 2010, 03:18 last edited by
finally got to the master branch without issues, the qml observer works fine as shown in the youtube video but not able to debug qml apps properly ... still trying further
-
wrote on 6 Nov 2010, 03:59 last edited by
I guess we have to wait for more stable release of this feature. Keep getting this error when I try to debug qml ...
Maybe some Troll can throw more light on this dump from the debugger log...
@
&"warning: QDeclarativeDebugServer: Connection established\n"
QDeclarativeDebugServer: Connection established&"\n"
sQmlJSDebugger: Connected to debug service 'QDeclarativeObserverMode'.
sQmlJSDebugger: Connected to debug service 'JSDebugger'.
sQmlJSDebugger: connected.
s
sQmlJSDebugger: Not connected to debug service 'JSDebugger'.
sQML Debugger connected.
dNOTE: ENGINE RUN AND INFERIOR RUN OK
dState changed from InferiorRunOk(10) to InferiorRunRequested(9).
dState changed BY FORCE from InferiorRunOk(10) to InferiorRunOk(10).
dNOTE: INFERIOR RUN OK
dState changed from InferiorRunRequested(9) to InferiorRunOk(10).
dState changed BY FORCE from InferiorRunOk(10) to InferiorRunOk(10).
eQmlJSDebugger: Error: (-1) Unknown error
sQmlJSDebugger: connected.
@Also found this strange message:
@
set substitute-path C:/qt-greenhouse/Trolltech/Code_less_create_more/Trolltech/Code_less_create_more/Troll/4.6/qt C:/qt/chetan-chetans-qt-master/chetans-qt
set substitute-path C:/iwmake/build_mingw_opensource C:/qt/chetan-chetans-qt-master/chetans-qt
@
Code has some hardcoded paths to qt-greenhouse :) -
wrote on 8 Nov 2010, 19:24 last edited by
Sadly, as it´s a very usefull feature...
-
wrote on 8 Nov 2010, 19:26 last edited by
I will try to do the same at home later, on my Linux machine, to see if I get a better result.
-
@chetankjain: I'm pretty sure QtCreator doesn't contain any references to qt-greenhouse :)
Anyhow, the debugger log looks indeed strange: What happens is that a connection to the client program was established, and both services (QDeclarativeObserverMode, JSDebugger) are found. However, afterwards the JSDebugger becomes unavailable again. This could happen e.g. because the QmlEngine on the client side is destroyed ... Can you tell exactly with which QtCreator version / Qt branch this happened? Or could you try with finalized 4.7.1 and latest QtCreator 2.1 ? Preferably as a bug report at bugreports.qt.nokia.com. Thanks in advance!
-
wrote on 18 Nov 2010, 18:16 last edited by
[quote author="kkoehne" date="1290067334"]@chetankjain: I'm pretty sure QtCreator doesn't contain any references to qt-greenhouse :)
Anyhow, the debugger log looks indeed strange: What happens is that a connection to the client program was established, and both services (QDeclarativeObserverMode, JSDebugger) are found. However, afterwards the JSDebugger becomes unavailable again. This could happen e.g. because the QmlEngine on the client side is destroyed ... Can you tell exactly with which QtCreator version / Qt branch this happened? Or could you try with finalized 4.7.1 and latest QtCreator 2.1 ? Preferably as a bug report at bugreports.qt.nokia.com. Thanks in advance!
[/quote]Hi Koehne, thanks for the reply.
yes the latest creator doesn't have any references to qt-greenhouse, its cleaned up now :)I tried on the final Qt 4.7.1 and Creator 2.1 itself. I'll log a bug
-
wrote on 19 Nov 2010, 20:18 last edited by
Hello,
I logged a bug about the original post.
http://bugreports.qt.nokia.com/browse/QTCREATORBUG-3148I receive a similar error (same error about connecting to server, but not the same message). I can replicate the error in two environments.
-
wrote on 21 Nov 2010, 04:01 last edited by
thanks jpasion, will update my comments there too
-
wrote on 28 Jan 2011, 02:52 last edited by
Good posts.Looking forward to QML debugger problems fixed.