## Symbian Device (Install SIS) Launch Configuration (Run-mode)

Select the Symbian Device (Install SIS) launch configuration to debug or run applications on a target device using the CODA (Carbide On-Device Debug Agent). CODA is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian installation file to the phone and install it prior to launching.

If the New Launch Configuration Wizard was used to create the CODA launch configuration no changes are usually needed. To modify the launch configuration settings, select the Run > Debug As menu option to open the Debug dialog. Select the Symbian Device (Install SIS) configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.

Figure 1. Device launch configuration in the Debug dialog

The Symbian Device (Install SIS) launch configuration panes include:

- The Main tab defines the project to be launched. Enter the name of the project in the Project field, and the executable name in the Executable field.
- The Arguments tab (standard CDT page) lets you specify the program arguments that an application uses.
- The Debugger tab defines debug configurations, such as entry point to begin debugging and target options.
- The File Transfer tab displays an auto-populated list of files that the IDE transfers to the target device at the start of each launch.
- The Installation tab specifies the .sis file(s) to install on the target device.
- The Executables tab allows you to specify which executables that you want to debug that are part of the project.
- The Source tab (standard CDT page) defines the location of source files used to display source when debugging an application. By default, these settings are derived from the associated project's build path. You may override these settings here.
- The Common tab (standard CDT page) defines general information about the launch configuration. You may choose to store the launch configuration in a specific file

#### Other references

- Launch Configuration Overview