Details
Description
When starting a debug session, if the Qt debug information files are not installed, a warning is shown in the form of a pop-up window. If a breakpoint was hit while the pop-up is open, after closing the pop-up the source editor still looks the same as if no debug session is running. Other parts of the UI also did not transition to debug mode, e.g. the call stack is not shown.
Pre-conditions
- Qt installation without debug info files
Steps
- Create a project (e.g. Widgets template, CMake, Qt 6.2.4 MSVC2019 64bit)
- Set a breakpoint in main.cpp
- Start debug session
Expected
- Breakpoint is hit
- UI transitions to debug mode, including:
- Source code editor shows execution stopped at breakpoint
- Call stack lists the main() function as current context
Actual
- Pop-up opens with warning about Qt debug info files
- At the same time, the breakpoint is hit
- This is apparent from the state of the "run in debug" button
- Hovering the mouse over this button shows a tooltip with "Continue CDB for <project>"
- Parts of the UI appear to have not transitioned to debug mode, even after closing the pop-up. For example:
- Source code does not show the stopped execution point
- The call stack is not shown
Notes
- It's possible to manually "refresh" the UI by switching to the "#1" thread and then back to "#0", after which the UI correctly shows the debug session information.