Community
Participate
Working Groups
Build Identifier: 201009241320 Suspending a running Qt application via the Suspend button is not working. The running Qt application is not suspended. A result of this problem is, that setting breakpoints in a Qt application only possible if the application is suspended (i.e. if a breakpoint was hit). Setting a breakpoint while the application is running is not possible. Suspending non Qt C++ applications works fine. Because suspending a running application is essential for effective debugging I would set the severity to Major. Reproducible: Always Steps to Reproduce: 1. Start Qt application 2. Hit Suspend button
Can you post the traces from the console called 'gdb traces'? We may be able to see some output that may explain why the interrupt is not working.
How can I open the 'gdb traces' console? If I start debugging session I only have the gdb console and the application console.
(In reply to comment #2) > How can I open the 'gdb traces' console? If I start debugging session I only > have the gdb console and the application console. On the console view, there is a little TV icon with an arrow. Click on the arrow and you will see all available consoles, including 'gdb traces'
Created attachment 182930 [details] Screenshot of eclipse debugging session There is no 'gdb traces' console available.
(In reply to comment #4) > Created an attachment (id=182930) [details] > Screenshot of eclipse debugging session > > There is no 'gdb traces' console available. My console drop down does not look like yours at all. What Eclipse are you using?
Created attachment 182958 [details] Installed software on Eclipse Helios SR1 > My console drop down does not look like yours at all. What Eclipse are you > using? I'm using Eclipse Helios Service Release 120100917-0705. To make sure that the missing 'gdb traces' console is not related to my eclipse installation I just downloaded eclipse-cpp-helios-SR1-win32.zip from http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/helios/SR1/eclipse-cpp-helios-SR1-win32.zip. If I run this eclipse version, then there is also no 'gdb traces' console. Should I create a new bugzilla entry 'gdb traces console is missing'?
Created attachment 182967 [details] GDB trace console output for application start (In reply to comment #1) > Can you post the traces from the console called 'gdb traces'? We may be able > to see some output that may explain why the interrupt is not working. My co-worker has an Eclipse Helios SR1 with 'gdb traces' console. He did the trace for me and I attached his trace (gdbtrace.txt). The trace shows the complete application startup from the time the debug button was clicked till the moment the application main window appeared on screen. If we press the suspend button, nothing happens - no more output in the 'gdb traces' console. In my opinion this must be something related to Qt because it does not happen with non Qt applications. Maybe the Qt Windows implementation uses some signals that are required by the debugger? QtCreator also uses GDB but they must do something different because it is possible to suspend Qt applications in QtCreator. That means, if we debug the same application that produces the attached gdb trace output in QtCreator, then it is possible to suspend the application and to set breakpoints during running application. Any idea how the 'gdb traces' console disappeared on my eclipse? Any hidden switches or settings I missed?
