You may then toggle among the names of the debug session configurations in the list, if needed to launch the most suitable session for the task at hand.
The easiest way to create a new configuration is duplicate an existing one, edit the configuration settings in the dialogue box, and then rename it.
By right clicking on an existing configuration, you enable the options to create a new one, duplicate the existing one or delete it. This is done by clicking on the down arrow next to the debug icon and selecting debug configurations to bring up the list of existing configurations. It is possible to create multiple debug session configurations. List making and history keeping are important driving factors in determining the practical behavior of Atollic TrueSTUDIOﾂｮ development environment. The Atollic TrueSTUDIOﾂｮ philosophy of resolving which executable image to program into the part must be considered carefully in this case. It is important to be cautious when doing so, as unexpected results may occur. After switching from Debug to Release, the target can be programmed by launching a debugging session. When code is found to behave as specified, a Release build with no symbolic debug information and high optimization level is usually built. ﾂｷ The lowest level of optimization is normally used. ﾂｷ Complete symbolic information is emitted by the toolchain to help navigate through the information in the high level code during the debug process. There are two important properties of the debug build configuration: Almost all developers start with the Debug configuration for building, downloading and de bugging the behavior of software.
0 kommentar(er)
