core/com.nokia.carbide.cpp.doc.user/html/projects/launch/attach_process.htm
changeset 2131 ff0156b93599
parent 2087 617a89f9dffc
child 2136 f0b706fa897d
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/attach_process.htm	Sat Oct 02 12:36:21 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/attach_process.htm	Wed Oct 06 10:31:32 2010 -0500
@@ -9,19 +9,19 @@
 
 <body>
 <h2>Attach to Process  Launch Configuration</h2>
-<p>Use the <b>Symbian OS Device (Attach to Process)</b> launch configuration to attach the debugger to an already running Symbian OS process or thread on a target device from within any project. This is useful for debugging servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate as one example. </p>
-<p>Attaching to a process requires a both target device running the Symbian OS and the presence of CODA on the device. <span class="note">You can also use the <a href="../../reference/view_symbian_kernel.htm">Symbian OS Data</a> view to attach to a process while debugging.</span> However, you can not attach to a process running on an emulator. </p>
-<p>If  the <a href="wiz_new_launch_config.htm">New Launch Configuration Wizard</a> created the Attach to Process launch configuration no changes are usually needed. The Attach to Process options match those of Symbian OS Device with one additional step, selection of the process to debug in the <b>Attach to Process</b> dialog. </p>
+<p>Use the <b>Symbian Device (Attach to Process)</b> launch configuration to attach the debugger to an already running Symbian process or thread on a target device from within any project. This is useful for debugging servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate as one example. </p>
+<p>Attaching to a process requires a both target device running the Symbian and the presence of CODA on the device. <span class="note">You can also use the <a href="../../reference/view_symbian_kernel.htm">Symbian Data</a> view to attach to a process while debugging.</span> However, you can not attach to a process running on an emulator. </p>
+<p>If  the <a href="wiz_new_launch_config.htm">New Launch Configuration Wizard</a> created the Attach to Process launch configuration no changes are usually needed. The Attach to Process options match those of Symbian Device with one additional step, selection of the process to debug in the <b>Attach to Process</b> dialog. </p>
 <p>To modify the  launch configuration settings, select the <b>Run &gt;  Debug As</b> menu option to open the <b>Debug</b> dialog. Select the Attach to Process configuration and click a tab to set specific options. Click <b>Apply</b> to save any option modifications. Click <b>Debug</b> to launch a debugging session using the new settings.</p>
 <p align="center"><img src="../images/wnd_debug_attach_process_launch_config.png" width="780" height="578"></p>
 <p class="figure">Figure 1. Attach to Process launch configuration in the Debug dialog </p>
-<p>The <b>Symbian OS Device (Attach to Process)</b> launch configuration panes include:</p>
+<p>The <b>Symbian Device (Attach to Process)</b> launch configuration panes include:</p>
 <ul>
   <li>The <a href="page_main.htm">Main</a> 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.</li>
   <li>The <a href="page_debugger.htm">Debugger</a> tab defines debug configurations, such as entry point to begin debugging, target options, and instruction set.</li>
   <li>The <a href="page_rom_log.htm">ROM Log </a> tab allows you to  specify where the ROM log file is stored and the <span class="code">Epoc32</span> directory.</li>
   <li>The <a href="page_executables.htm">Executables</a> tab allows you to specify which executables that you want to debug that are part of the project.</li>
-  <li>The <a href="../../reference/trk/wnd_new_connection_wizard.htm">Source</a> tab  (<i>standard CDT page</i>) 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. </li>
+  <li>The <a href="../remote_conn/wnd_new_connection_wizard.htm">Source</a> tab  (<i>standard CDT page</i>) 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. </li>
   <li>The <a href="wiz_new_launch_config.htm">Common</a> tab  (<i>standard CDT page</i>) defines general information about the launch configuration. You may choose to store the launch configuration in a specific file.</li>
 </ul>
 <h4>Other references</h4>