16 <li><a href="run_mode_debug_02.htm">Install an SDK</a></li> |
16 <li><a href="run_mode_debug_02.htm">Install an SDK</a></li> |
17 <li><a href="run_mode_debug_03.htm">Setup environment variables</a></li> |
17 <li><a href="run_mode_debug_03.htm">Setup environment variables</a></li> |
18 <li><a href="run_mode_debug_04.htm">Setup a virtual drive for Techview and Cust Kits</a></li> |
18 <li><a href="run_mode_debug_04.htm">Setup a virtual drive for Techview and Cust Kits</a></li> |
19 <li><a href="run_mode_debug_05.htm">Set the default kit in Devices.xml </a></li> |
19 <li><a href="run_mode_debug_05.htm">Set the default kit in Devices.xml </a></li> |
20 <li><a href="run_mode_debug_06.htm">Install the SISX file on the target device</a></li> |
20 <li><a href="run_mode_debug_06.htm">Install the SISX file on the target device</a></li> |
21 <li><a href="run_mode_debug_07.htm">Configure TRK connection on the device</a></li> |
21 <li><a href="run_mode_debug_07.htm">Configure CODA connection on the device</a></li> |
22 <li><b>Create a launch configuration</b></li> |
22 <li><b>Create a launch configuration</b></li> |
23 </ol> |
23 </ol> |
24 <div class="step"> |
24 <div class="step"> |
25 <h4><a name="runLaunch" id="runLaunch"> </a>Creating a Launch Configuration setup</h4> |
25 <h4><a name="runLaunch" id="runLaunch"> </a>Creating a Launch Configuration setup</h4> |
26 <ol> |
26 <ol> |
28 <li>Select the Project in the C/C++ Project pane you want to debug</li> |
28 <li>Select the Project in the C/C++ Project pane you want to debug</li> |
29 <li>From the IDE select Run > Debug…</li> |
29 <li>From the IDE select Run > Debug…</li> |
30 <li>The <a href="../../projects/launch/wiz_new_launch_config.htm">New Launch Configuration Wizard</a> appears</li> |
30 <li>The <a href="../../projects/launch/wiz_new_launch_config.htm">New Launch Configuration Wizard</a> appears</li> |
31 <p>To communicate between the Carbide.c++ debugger and the on-device debug agent or protocol interface you must define a debug launch configuration. The Debug window is where you define the type of debug launch configuration to use when debugging programs on the target device (Figure 4).</p> |
31 <p>To communicate between the Carbide.c++ debugger and the on-device debug agent or protocol interface you must define a debug launch configuration. The Debug window is where you define the type of debug launch configuration to use when debugging programs on the target device (Figure 4).</p> |
32 <p><img src="images/Debug_Config_main.png" width="986" height="640" /></p> |
32 <p><img src="images/Debug_Config_main.png" width="986" height="640" /></p> |
33 <p class="figure">Figure 4. Debug Window</p> |
33 <p class="figure">Figure 4. Debug window</p> |
34 <li>Select either a Symbian OS Device (Install SIS) or Symbian OS Device configuration type for on-device debugging and click New</li> |
34 <li>Select either a Symbian Device (Install SIS) or Symbian Device configuration type for on-device debugging and click New</li> |
35 <p>For debug launch configurations using the CODA debug agent, the following pages require review and possible option settings:</p> |
35 <p>For debug launch configurations using the CODA debug agent, the following pages require review and possible option settings:</p> |
36 <ul> |
36 <ul> |
37 <li><b>Main</b> - defines the project to be launched on the target device</li> |
37 <li><b>Main</b> - defines the project to be launched on the target device</li> |
38 <li>Arguments (<i>Eclipse</i>) - defines the arguments to be passed to the application and to the virtual machine</li> |
38 <li>Arguments (<i>Eclipse</i>) - defines the arguments to be passed to the application and to the virtual machine</li> |
39 <li><b>Debugger</b> - provides control over entry points, message handling, and instruction set default settings</li> |
39 <li><b>Debugger</b> - provides control over entry points, message handling, and instruction set default settings</li> |