--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm Mon Apr 12 14:47:08 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm Tue Apr 13 15:55:45 2010 -0500
@@ -5,8 +5,7 @@
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Carbide Debugger panes</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/></head>
<body bgcolor="#FFFFFF">
<h2>Debugger panes</h2>
<p>The options shown in the <b>Debugger</b> page differ based upon the type of launch configuration. Generally, the options fall into these choices: </p>
@@ -89,7 +88,7 @@
</tr>
</table>
<h3><a name="trk_stopmode" id="trk_stopmode"></a>Stop-mode Debugger page </h3>
-<p>In stop-mode launch configurations like <b><a href="stop_mode.htm">System TRK</a></b>, <b><a href="trace32.htm">Trace32</a></b>, and <a href="attach_process.htm"><b>Attach to Process</b></a>, use the <b>Startup Options</b> to attach to a target and debug or run from the specified start address. Then use <b>Target Options</b> to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session. </p>
+<p>In stop-mode launch configurations like <b><a href="stop_mode.htm">System TRK</a></b>, <b><a href="trace32.htm">Trace32</a></b>,<b> </b>and <a href="attach_process.htm"><b>Attach to Process</b></a>, use the <b>Startup Options</b> to attach to a target and debug or run from the specified start address. Then use <b>Target Options</b> to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session. </p>
<p align="center"><img src="images/page_debugger_stop_mode.png" width="642" height="401"></p>
<p class="figure">Figure 3 - Debugger page showing stop-mode options </p>
<h5>Table 3. Debugger page — stop-mode options </h5>
@@ -135,7 +134,7 @@
<td> </td>
<td><b>Target initialization file </b></td>
<td><p>Check this box to have the debugger run an initialization script when the debug session starts. For example, if a target device requires initialization for the debugger to be able to read and write memory or registers, you can specify an initialization script here.</p>
- <p> Click Browse to select a script file using a standard file selection dialog box. When using T32, most of the initialization is done in the CMM script file. With other debug protocols you can specify the initialization file, which can be run after connecting to the target. </p></td>
+ <p> Click Browse to select a script file using a standard file selection dialog box. When using T32, most of the initialization is done in the CMM script file. With other debug protocols you specify the initialization file, which can be run after connecting to the target. </p></td>
</tr>
<tr>
<td> </td>
@@ -150,6 +149,6 @@
<li><a href="emulation.htm">Emulation Launch Configuration</a></li>
<li><a href="stop_mode.htm">System TRK Launch Configuration </a></li>
</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
</body>
</html>