There are various reasons why the debugger plugin may fail to automatically pick up a suitable native debugger. The following table summarizes the support for debugging C++ code: Platformįor more information on the debugger modes, see Launching the Debugger in Different Modes.

Specifically, it also uses compiled C++ code for the debugging helper library. The CDB native debugger has similar funtionality to the non-Python GDB debugger engine. The Python version uses a script version of the debugging helpers that does not need any special setup. For more information, see Debugging Helpers Based on C++. The non-Python versions use the compiled version of the debugging helpers, that you must enable separately. On Windows, Symbian, Maemo, and MeeGo Harmattan, only the Python version is supported. Use a Python enabled version if one is available.

The debugger plugin supports different builds of the GDB debugger, both with and without the ability to use Python scripting. 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) GDB on Mac OS, you must sign it and add it to Qt Creator as a tool chain. For more information, see Setting the Symbol Server in 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. However, you might have an unsupported GDB version installed, your Linux environment might not have GDB installed at all, or you might want to use the debugging tools for Windows. Typically, the interaction between Qt Creator and the native debugger is set up automatically and you do not need to do anything. Note: The information in this section applies only to debugging the C++ language.

Gdb debugger install windows