On Linux, the minimum supported version is LLDB 3.8. The minimum supported version is LLDB 320.4.
On macOS you can use the LLDB version delivered with Xcode or build from source. LLDB is typically used with the Clang compiler (even though you can use it with GCC, too). LLDB is the default debugger in Xcode on macOS for supporting C++ on the desktop. The LLDB native debugger has similar functionality to the GDB debugger. Supported CDB VersionsĪll versions of CDB targeting platforms supported by Qt are supported by Qt Creator. The minimum supported version is GDB 7.5 using Python version 2.7, or 3.3, or newer.įor remote debugging using GDB and GDB server, the minimum supported version of GDB server on the target device is 7.0. GDB builds without Python scripting are not supported anymore and will not work. Starting with version 3.1, Qt Creator requires the Python scripting extension. The following table summarizes the support for debugging C++ code: On macOS and Linux, the LLDB debugger can be used. On Microsoft Windows, when using the Microsoft tool chain, the Microsoft Console Debugger CDB is needed. On most supported platforms, the GNU Symbolic Debugger GDB can be used. Qt Creator supports native debuggers when working with compiled code. It also applies for code in other compiled languages such as C, FORTRAN, Ada.įor more information on the debugger modes, see Launching the Debugger in Different Modes. This section explains the options you have for debugging C++ code and provides installation notes for the supported native debuggers.
Note: To use the Free Software Foundation (FSF) version of GDB on macOS, you must sign it and modify your kit settings. For more information, see Setting CDB Paths on Windows.
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. If the debugger you want to use is not automatically detected, select Tools > Options > Kits > Debuggers > Add to add it. Make sure to select the cloned kit for your project. 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. 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). To specify the debugger and compiler to use for each kit, select Tools > Options > Kits.
The main debugger settings are associated with the kit you build and run your project with.