This command starts selected debugger on the active file. If debugger is not set, a dialog will be displayed where the debugger for the active project may be selected.
In most cases, where the use of a debugger is appropriate, this will be specified as most compilers come packaged with an associated debugger and the Debugger key in the Compiler Options (under Linker Options) will show this (for example for Visual Studio, the debugger is set to " msdev").
Double clicking on the Debugger key presents a dialog where the user may specify a different debugger to be used if desired.
The user may click on the Debug button in the Tools toolbar to invoke the debugger.
UEStudio will check to see if a debugger is set. If this isn't set in the compiler options, UEStudio will display a browse dialog so a debugger may be selected. If a debugger is set, UEStudio will prompt if this debugger should be set as the default for future projects. If "Yes" is selected, the selected debugger will be saved in the compiler configuration file so that when a new project is selected this will be remembered and is not limited to the active project.
If the Edit Configuration button is pressed in the Select Compiler dialog the compiler configuration file will be displayed here and advanced users who are very familiar with their compiler/debugger functionality may edit this file directly if desired.
For example, users may set dependencies, and decide if they want to run the debugger as a console debugger ( gdb) or windowed debugger ( WinDbg).
In the configuration file, users may select the Debug key and modify the [Start Debugger] section. For example, if the default is set to a windowed debugger and you wish to use a console debugger you would have to change/add the key "DisplayConsole=1" in that section.
If the Make Configuration Local button is pressed in the Select Compiler dialog the compiler configuration file will be saved into the project directory and changes made after pressing this will be saved locally with the project.
Once a debugger is selected, the user may invoke the debugger from the Commands submenu in the Tools toolbar:
