Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
5.12.3
-
4fea3ec29c9911522a379a01418394b5cad29ecc (qt/qtdeclarative/5.12)
Description
When using Connections inside QML and a debugger is attached then it will fail at runtime to access named signal arguments. This only happens if QML debugging is turned on in conjunction with attaching a debugger, every other combination is fine.
With the example attached, if it is failing then it will output:
10:55:48: Debugging starts 2019-04-24 10:55:54.374486+0200 untitled105[51047:4310884] QML debugging is enabled. Only use this in a safe environment. 2019-04-24 10:55:54.728405+0200 untitled105[51047:4310950] QML Debugger: Waiting for connection on port 63275... 2019-04-24 10:55:54.927688+0200 untitled105[51047:4310884] qrc:/main.qml:15: ReferenceError: textArg is not defined 2019-04-24 10:55:55.175851+0200 untitled105[51047:4310945] MessageTracer: Falling back to default whitelist 10:55:57: Debugging has finished
whereas when it works it will output:
11:10:02: Debugging starts 2019-04-24 11:10:08.080371+0200 untitled105[54077:4321504] QML debugging is enabled. Only use this in a safe environment. 2019-04-24 11:10:08.380209+0200 untitled105[54077:4321565] QML Debugger: Waiting for connection on port 63663... 2019-04-24 11:10:08.906772+0200 untitled105[54077:4321504] [qml] arg: this is some text 2019-04-24 11:10:08.906878+0200 untitled105[54077:4321504] [qml] textArg: this is some text 2019-04-24 11:10:09.147792+0200 untitled105[54077:4321560] MessageTracer: Falling back to default whitelist 11:10:10: Debugging has finished
This is introduced by change c9e6251cc8dfcf002f64b07e48dd68b7edd3f630 in qtdeclarative (according to a git bisect)
Attachments
Issue Links
- is duplicated by
-
QTBUG-76118 in debug mode reference errors in QML Connections
- Closed
-
QTBUG-75803 qml ReferenceError: sInfo is not defined when debugging
- Closed
-
QTBUG-76075 C++ signal > QML slot = ReferenceError (Qt5.12.3)
- Closed