On this page:
CLion enables using numerous run/debug configurations. Each run/debug configuration represents a named set of run/debug startup properties. When you perform run, debug, or test operations with CLion, you always start a process based on one of the existing configurations using its parameters.
CLion comes with a number of run/debug configuration types for the various running, debugging and testing issues. You can create your own run/debug configurations of specific types.
Each run/debug configuration type has its own default settings. Whenever a new run/debug configuration of the respective type is created, it is based on these default settings.
Temporary configurations are marked with semi-transparent icons and are managed same way as the permanent configurations.
By default, 5 temporary configurations are allowed per project. You can change this limit via the Edit Configurations dialog.
Permanent configurationA configuration of this type is explicitly created for a particular class or method. If there is no permanent configuration for an item, CLion automatically creates a temporary configuration for it, when you choose or on the context menu of this class or method.
Default run/debug configuration settings
The default run/debug configuration settings appear in the Run/Debug Configurations dialog under the nodeDefaults. They denote the settings that are used when new run/debug configurations are created.
You can set the default settings for a specific configuration type that will become applicable to any run/debug configuration of this type created later. Changing defaults does not affect the existing run/debug configurations.
The process of editing per-type default configuration settings is described in Changing Run/Debug Configuration Defaults. The process of creating or editing custom run/debug configurations is described in Creating and Editing Run/Debug Configurations.