Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
None
-
Qt Creator 3.0.0-beta
-
Intel Core i7 Desktop
Ubuntu 13.04 64 bit
Qt 5.2.0 Beta 1
Qt Creator 3.0 Beta 1 (installed with Qt 5.2.0 Beta 1)
Compiler: "GCC (x86 64 bit in /usr/bin)"
Debugger: "System GDB at /usr/bin/gdb"
-
0910a577f4d12eea4a099c989bd58f1dee6c88db
Description
Steps to reproduce:
1.Install Qt 5.2.0 Beta 1. Make sure to select QtCreator during the installation process.
2. Open QtCreator 3.0 and configure it with the Qt 5.2.0 Desktop kit.
3. Create a new Qt Quick 2 application.
4. In main.qml add an onClicked signal handler to the button and do something like log a message to the console.
5. Set a breakpoint in the onClicked signal handler.
6. Build and Debug the app.
7. Click on the button in the running app.
Expected Results:
-Debugger should break at the breakpoint in the onClicked signal handler.
Actual Results:
-Debugger does NOT stop at the breakpoint.
-Log statement indicates the onClicked signal handler was executed.
NOTE: If I switch the kit to my Qt 5.1.1 install I am able to successfully hit breakpoints in QML using Qt Creator 3.0.
Attachments
Issue Links
- depends on
-
QTBUG-34394 QML debugging not working
- Closed
- is required for
-
QTBUG-33863 Issues to be fixed before Qt5.2 RC1 release
- Closed
- relates to
-
QTCREATORBUG-10528 Regression: "Could not connect to the in-process QML debugger" with Qt 4.7
- Closed