Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.8.0, 5.9
-
Windows 10 64 bit
MSVC2015 64 bit
cdb 10.0
-
f261a534cc96d41cee15462795844116887bd99a
Description
- Create a Qt Quick Application project in Qt Creator.
- In the project's QML file, add some JavaScript with a failing condition:
I have:MainForm { anchors.fill: parent mouseArea.onClicked: { console.log(qsTr('Clicked on background. Text: "' + textEdit.text + '"')); if (textEdit.text == "key") console.log("Unlocked"); } }
- Put a breakpoint into the first line of this JavaScript.
- Run the application in the debugger and let it stop at the breakpoint.
- Step forward twice.
Creator will indicate that you stepped into the line with the second log although this line is not being executed.
Stepping should only reach lines that are being executed.
It seems like the debugger will always indicate being stopped at the last line of the block. If you add another line after the second log (outside the "if"), the debugger will step to this instead.
Attachments
Issue Links
- relates to
-
QTBUG-59204 When debugging QML in Qt Creator it is possible that doing a step over will put the cursor on a line that it will not actually invoke
- Closed
For Gerrit Dashboard: QTBUG-59774 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
190276,3 | V4: Set correct source locations for jumps out of conditionals | 5.9 | qt/qtdeclarative | Status: MERGED | +2 | 0 |