Setting Up Debugger
The main debugger settings are associated with the kit you build and run your project with. To specify the debugger and compiler to use for each kit, select Tools > Options > Build and Run > Kits.
You need to set up the debugger only if the automatic setup fails, because the native debugger is missing (as is usually the case for the CDB debugger on Windows, which you always must install yourself) or because the installed version is not supported (for example, when your system contains no, or an outdated version of GDB and you want to use a locally installed replacement instead).
Note: If you need to change the debugger to use for an automatically detected kit, you can Clone the kit and change the parameters in the clone. Make sure to select the cloned kit for your project.
If the debugger you want to use is not automatically detected, select Tools > Options > Build & Run > Debuggers > Add to add it.
Note: To use the debugging tools for Windows, you must install them and add the Symbol Server provided by Microsoft to the symbol search path of the debugger. For more information, see Setting CDB Paths on Windows.
This section explains the options you have for debugging C++ code and provides installation notes for the supported native debuggers. It also applies for code in other compiled languages such as C, FORTRAN, Ada.
For more information on the debugger modes, see Launching the Debugger in Different Modes.
Supported Native Debugger Versions
Qt Creator supports native debuggers when working with compiled code. On most supported platforms, the GNU Symbolic Debugger GDB can be used. On Microsoft Windows, when using the Microsoft tool chain the Microsoft Console Debugger CDB, is needed. On macOS, the LLDB debugger can be used. Basic support for LLDB is also available on Linux, but it is restricted by LLDB's capabilities there, and considered experimental.
The following table summarizes the support for debugging C++ code:
|Linux||GCC, ICC||GDB, LLDB (experimental)|
|macOS||GCC, Clang||LLDB, FSF GDB (experimental)|
|Windows/MSVC||Microsoft Visual C++ Compiler||Debugging Tools for Windows/CDB|
Supported GDB Versions
Starting with version 3.1, Qt Creator requires the Python scripting extension. GDB builds without Python scripting are not supported anymore and will not work. The minimum supported version is GDB 7.5 using Python version 2.7, or 3.3, or newer.
For remote debugging using GDB and GDB server, the minimum supported version of GDB server on the target device is 7.0.
Supported CDB Versions
All versions of CDB targeting platforms supported by Qt are supported by Qt Creator.
Supported LLDB Versions
The LLDB native debugger has similar functionality to the GDB debugger. LLDB is the default debugger in Xcode on macOS for supporting C++ on the desktop. LLDB is typically used with the Clang compiler (even though you can use it with GCC, too).
On macOS you can use the LLDB version delivered with Xcode or build from source. The minimum supported version is LLDB 320.4.
On Linux, the minimum supported version is LLDB 3.8.
Installing Native Debuggers
Check the table below for the supported versions and other important information about installing native debuggers.
|GDB||On Windows, use the Python-enabled GDB versions that is bundled with the Qt package or comes with recent versions of MinGW. On most Linux distributions the GDB builds shipped with the system are sufficient. You can also build your own. Follow the instructions in Building GDB. Builds of GDB shipped with Xcode on macOS are no longer supported.|
|Debugging tools for Windows||To use the CDB debugger, you must install the Debugging tools for Windows. You can download them from Download and Install Debugging Tools for Windows.|
Note: Visual Studio does not include the Debugging tools needed, and therefore, you must install them separately.
The pre-built Qt for Windows makes use of the library if it is present on the system. When manually building Qt Creator using the Microsoft Visual C++ Compiler, the build process checks for the required files in
It is highly recommended that you add the Symbol Server provided by Microsoft to the symbol search path of the debugger. The Symbol Server provides you with debugging informaton for the operating system libraries for debugging Windows applications. For more information, see Setting CDB Paths on Windows.
|Debugging tools for macOS||The Qt binary distribution contains both debug and release variants of the libraries. But you have to explicitly tell the runtime linker that you want to use the debug libraries even if your application is compiled as debug, as release is the default library.|
If you use a qmake based project in Qt Creator, you can set a flag in your run configuration, in Projects mode. In the run configuration, select Use debug version of frameworks.
|LLDB||We recommend using the LLDB version that is delivered with Xcode 5.|
Mapping Source Paths
To enable the debugger to step into the code and display the source code when using a copy of the source tree at a location different from the one at which the libraries were built, map the source paths to target paths:
- Select Tools > Options > Debugger > General > Add.
- In the Source path field, specify the source path in the debug information of the executable as reported by the debugger.
- In the Target path field, specify the actual location of the source tree on the local machine.
Setting CDB Paths on Windows
To obtain debugging information for the operating system libraries for debugging Windows applications, add the Symbol Server provided by Microsoft to the symbol search path of the debugger:
- Select Tools > Options > Debugger > CDB Paths.
- In the Symbol Paths group, select Insert.
- Select the directory where you want to store the cached information.
Use a subfolder in a temporary directory, such as
- Select OK.
Note: Populating the cache might take a long time on a slow network connection.
To use the Source Server infrastructure for fetching missing source files directly from version control or the web, enter the following string in the Source Paths field:
Setting up FSF GDB for macOS
- To create a key for signing FSF GDB, select Keychain Access > Certificate Assistant > Create a Certificate:
- In the Name field, input fsfgdb to replace the existing content.
- In the Certificate Type field, select Code Signing.
- Select the Let me override defaults check box.
- Select Continue, and follow the instructions of the wizard (use the default settings), until the Specify a Location For The Certificate dialog opens.
- In the Keychain field, select System.
- Select Keychain Access > System, and locate the certificate.
- Double click the certificate to view certificate information.
- In the Trust section, select Always Trust in the When using this certificate field, and then close the dialog.
- To sign the binary, enter the following command in the terminal:
codesign -f -s "fsfgdb" $INSTALL_LOCATION/fsfgdb
- In Qt Creator, select Qt Creator > Preferences > Build & Run > Kits > Add to create a kit that uses FSF GDB.
- In the Debugger field, specify the path to FSF GDB (
$HOME/gdb72/bin/fsfgdb, but with an explicit value for
- To use the debugger, add the kit in the Build Settings of the project.
Setting Up Experimental LLDB Support
To use the experimental interface to LLDB, you must set up a kit that uses the LLDB engine and select the kit for your project:
- Select Tools > Options > Build & Run > Kits.
- Select an automatically created kit in the list, and then select Clone to create a copy of the kit.
- In the Debugger field, select an LLDB Engine. If an LLDB Engine is not listed, select Manage to add it in Tools > Options > Build & Run > Debuggers. For more information, see Adding Debuggers.
- To use the debugger, add the kit in the Build Settings of the project.
© 2017 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.