

If you need a console window to operate your application, for example because it accepts console input from the user, go to Projects > Run Settings and select the Run in terminal check box. Start Internal mode is the default start mode for most projects, including all projects using a desktop Qt version and plain C++ projects. Post-mortem to debug crashed processes on Windows.Core to debug crashed processes on Unix.Attach to debug processes already started and running outside Qt Creator, either locally or on a remote machine.Start External to start and debug processes without a proper Qt Creator project setup, either locally or on a remote machine.Start Internal to debug applications developed inside Qt Creator such as a Qt based GUI application.The debugger can run in the following modes: If the current project is a QML application using C++ plugins, a "mixed" QML/C++ engine will be started, with the C++ parts being handled by GDB and GDB server remote debugging.Ĭhange the run configuration parameters (such as Run in Terminal) in the run settings of the project, or select options from the Debug > Start Debugging menu to select other modes of operation. So if the current project is set up as a C++ application using the MinGW toolchain targeting desktop Windows, the GDB engine will be started in Start Internal mode. In general, F5 and the Start Debugging of Startup Project button are set up in a way to start the operating mode that is commonly used in a given context. Some of the modes are only available for a particular operating system or platform. The debugger plugin can run the native debuggers in various operating modes depending on where and how the debugged process is started and run. Launching the Debugger in Different Modes

Note: Starting a C++ program in the debugger can take a long time, typically in the range of several seconds to minutes if complex features are used. For more information, see Specifying GDB Settings. gdbinit file on startup check box in GDB settings. gdbinit file on debugger startup, select the Load.

For more information, see Specifying Debugger Settings. When using GDB or CDB as debug backend, you can specify additional commands to execute before and after the backend and debugged program are started or attached in Tools > Options > Debugger > GDB and CDB. The debugger then takes over and starts the program with suitable parameters. To debug the program without deploying it, select Debug > Start Debugging > Start Debugging Without Deployment. Qt Creator checks whether the compiled program is up-to-date, and rebuilds and deploys it if the Build before deploying field is set to build the whole project or the application to run and the Always deploy before running check box is selected in the Build and Run options. To start an application from an open project under the control of a debugger, select the ( Start Debugging of Startup Project) button or press F5.
