--- a/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Tue Aug 03 14:05:25 2010 -0500
@@ -23,7 +23,7 @@
<ul>
<li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=11563">11563</a> - The Build Project dialog now also shows the project name. </li>
</ul>
-<h4><a name="bugs260" id="bugs2"></a>v2.7.0</h4>
+<h4><a name="bugs270" id="bugs2"></a>v2.7.0</h4>
<ul>
<li><a href="https://xdabug001.ext.nokia.com/bugzilla/show_bug.cgi?id=10267">11222</a> - You can now disable device discovery in the <strong>Remote Connection</strong> view to avoid conflicts between different connection protocols within Carbide. </li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/cheatsheets/getStarted_cs.xml Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/cheatsheets/getStarted_cs.xml Tue Aug 03 14:05:25 2010 -0500
@@ -1,9 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
-<cheatsheet title="Getting Started">
+<cheatsheet title="Creating and debugging an application project">
<intro>
- <description>
- Follow these steps to create a Symbian OS project and debug it using the S60 EPOC Emulator.
- </description>
+ Follow these steps to create and debug a Symbian project and using an emulator. using the S60 EPOC Emulator.
</intro>
<item title="Verify a Symbian SDK is available" dialog="true" skip="true" href="/com.nokia.carbide.cpp.doc.user/html/reference/SDKPreferences.html">
<description>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/common_debug_actions.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/common_debug_actions.htm Tue Aug 03 14:05:25 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body bgcolor="#FFFFFF">
<h2>Common Debugging Actions</h2>
-<p> This section explains how to perform common debugging actions within the <a href="../reference/perspective_debg.htm">Debug</a> perspective to correct source-code errors, control program execution, and observe memory behavior:</p>
+<p> This section explains how to perform common debugging actions within the <a href="../reference/perspective_debug.htm">Debug</a> perspective to correct source-code errors, control program execution, and observe memory behavior:</p>
<ul>
<li><a href="../debugger/debug/cmds_starting.htm">Start</a> the debugger</li>
<li>Step <a href="../debugger/debug/cmds_stepping.htm">into</a>, <a href="../debugger/debug/cmds_stepping.htm">out</a> of, or <a href="../debugger/debug/cmds_stepping.htm">over</a> routines</li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/concepts.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/concepts.htm Tue Aug 03 14:05:25 2010 -0500
@@ -28,7 +28,6 @@
<li><a href="build_targets.htm">Build Targets</a></li>
<li><a href="macros_carbide.htm">Carbide Macros</a></li>
<li><a href="contextual_menus.htm">Context menu support</a></li>
- <li><a href="dependency_tracking.htm">Dependency Tracking</a></li>
<li><a href="emulators.htm">Emulation Debugging</a></li>
<li><a href="ext_build_support.htm">External Builds Support</a></li>
<li><a href="../projects/launch/launch_configs_overview.htm">Launch Configurations</a></li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/cvs.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/cvs.htm Tue Aug 03 14:05:25 2010 -0500
@@ -12,7 +12,7 @@
<p>The <strong>Carbide.c++</strong> tools are built on top of the <strong>Eclipse</strong> and <strong>CDT</strong> open source projects (<a href="http://www.eclipse.org">eclipse.org</a>). Carbide can use several popular <a href="http://en.wikipedia.org/wiki/Software_configuration_management">software configuration management</a> systems including:</p>
<ul>
<li><a href="http://en.wikipedia.org/wiki/Apache_Subversion">Apache Subversive</a></li>
- <li><a href="tp://www.nongnu.org/cvs/">CVS</a> (<em>plug-in included with Carbide</em>)</li>
+ <li><a href="http://www.nongnu.org/cvs/">CVS</a> (<em>plug-in included with Carbide</em>)</li>
<li><a href="http://en.wikipedia.org/wiki/Git_(software)">Git</a></li>
<li><a href="http://en.wikipedia.org/wiki/Clearcase">IBM Rational Clearcase</a></li>
<li><a href="http://en.wikipedia.org/wiki/Mercurial">Mercurial</a></li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/emulators.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/emulators.htm Tue Aug 03 14:05:25 2010 -0500
@@ -1,37 +1,36 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Emulation Debugging</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Emulation Debugging </h2>
-<p>Symbian SDKs include an emulator that runs Symbian OS on a
- Microsoft Windows host computer. The emulator provides the full range of Symbian OS
- functionality, letting you do most development tasks on a single desktop computer. The
- emulator and the software you build for it with the Carbide.c++ software run natively on the Intel x86 family of processors.</p>
-<p> In many cases, you can build and debug a complete application using the emulator, then test the application on the actual device. There are cases however, where you cannot use
- the emulator, such as when developing device drivers that access hardware on a device.</p>
-<p>For more information about the emulator, please see the documentation that came with
- your SDK under: <b>Developer Library > Tools and Utilities > Emulator</b>.</p>
-<p> You will find an emulator to use with Carbide.c++ in:</p>
-<blockquote>
- <p class="code">C:\Symbian\<version>\<sdk>\Epoc32\release\winscw\udeb</p>
-</blockquote>
-<p>where <span class="code">Symbian</span> is the path containing the subdirectories and version number of the Symbian OS SDK.</p>
-<p class="note"><b>NOTE</b> The first time you launch an emulator it may take some time to appear. Remember that it is implementing the operating system on the target device and that some setup time is required. </p>
-<h5>Related tasks</h5>
-<ul>
- <li><a href="../tasks/projects/prj_debug_console.htm">Debugging Applications</a></li>
- <li><a href="../tasks/projects/prj_debug_dlls.htm">Debugging DLLs</a></li>
- <li>I<a href="../tasks/projects/prj_import_exe.htm">mporting Executables for Debugging </a></li>
-</ul>
-<div class="step">
- <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>
-
-</div>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Emulation Debugging</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Emulation Debugging </h2>
+<p>Symbian SDKs include an emulator that runs Symbian OS on a
+ Microsoft Windows host computer. The emulator provides the full range of Symbian OS
+ functionality, letting you do most development tasks on a single desktop computer. The
+ emulator and the software you build for it with the Carbide.c++ software run natively on the Intel x86 family of processors.</p>
+<p> In many cases, you can build and debug a complete application using the emulator, then test the application on the actual device. There are cases however, where you cannot use
+ the emulator, such as when developing device drivers that access hardware on a device.</p>
+<p>For more information about the emulator, please see the documentation that came with
+ your SDK under: <b>Developer Library > Tools and Utilities > Emulator</b>.</p>
+<p> You will find an emulator to use with Carbide.c++ in:</p>
+<blockquote>
+ <p class="code">C:\Symbian\<version>\<sdk>\Epoc32\release\winscw\udeb</p>
+</blockquote>
+<p>where <span class="code">Symbian</span> is the path containing the subdirectories and version number of the Symbian OS SDK.</p>
+<p class="note"><b>NOTE</b> The first time you launch an emulator it may take some time to appear. Remember that it is implementing the operating system on the target device and that some setup time is required. </p>
+<h5>Related tasks</h5>
+<ul>
+ <li><a href="../tasks/projects/prj_debug_console.htm">Debugging Applications</a></li>
+ <li><a href="../tasks/projects/prj_debug_dlls.htm">Debugging DLLs</a></li>
+</ul>
+<div class="step">
+ <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>
+
+</div>
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm Tue Aug 03 14:05:25 2010 -0500
@@ -6,7 +6,7 @@
<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>N-Gage Projects</title>
<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="../reference/perspective_debug.htm"></script>
</head>
<body bgcolor="#FFFFFF">
<h2>N-Gage Projects</h2>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/watchpoints.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/watchpoints.htm Tue Aug 03 14:05:25 2010 -0500
@@ -9,15 +9,15 @@
</head>
<body bgcolor="#FFFFFF">
<h2>Watchpoints Overview </h2>
-<p>A <b>watchpoint</b> is a marker set on a specific memory location which is designed to suspend program execution when the value at that location changes. Watchpoints are closely related to breakpoints and are shown in the <a href="../breakpoints/viewing_breakpoints.htm">Breakpoints</a> view. </p>
-<p>When a watchpoint is encountered during program execution, the debugger suspends execution and the <a href="../../reference/perspective_debug.htm">Debug</a> perspective appears so you can examine the executable's current state, check register and variable values, and use the stepping commands to walk line by line through the program to verify its operation. You can also change values and alter the flow of normal program execution. Setting watchpoints helps you debug your program and verify its efficiency.</p>
+<p>A <b>watchpoint</b> is a marker set on a specific memory location which is designed to suspend program execution when the value at that location changes. Watchpoints are closely related to breakpoints and are shown in the <a href="../reference/perspective_debug.htm">Breakpoints</a> view. </p>
+<p>When a watchpoint is encountered during program execution, the debugger suspends execution and the <a href="../reference/perspective_debug.htm">Debug</a> perspective appears so you can examine the executable's current state, check register and variable values, and use the stepping commands to walk line by line through the program to verify its operation. You can also change values and alter the flow of normal program execution. Setting watchpoints helps you debug your program and verify its efficiency.</p>
<p>The following topics cover various breakpoint concepts and actions: </p>
<ul>
- <li><a href="../breakpoints/viewing_breakpoints.htm">Viewing Breakpoints and Watchpoints</a> </li>
- <li><a href="status_watchpoints.htm">Watchpoint Status Indicators</a></li>
- <li><a href="setting_watchpoints.htm">Setting and Removing Watchpoints</a></li>
- <li><a href="toggling_watchpoints.htm">Enabling and Disabling Watchpoints</a></li>
- <li><a href="../breakpoints/exporting_breakpoints.htm">Exporting</a> and <a href="../breakpoints/importing_breakpoints.htm">importing</a> watchpoints</li>
+ <li><a href="../reference/perspective_debug.htm">Viewing Breakpoints and Watchpoints</a> </li>
+ <li><a href="../reference/perspective_debug.htm">Watchpoint Status Indicators</a></li>
+ <li><a href="../debugger/watchpoints/setting_watchpoints.htm">Setting and Removing Watchpoints</a></li>
+ <li><a href="../reference/perspective_debyg.htm">Enabling and Disabling Watchpoints</a></li>
+ <li><a href="http://www.nongnu.org/cvs/">Exporting</a> and <a href="http://www.nongnu.org/cvs/">importing</a> watchpoints</li>
</ul>
<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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_programs.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_programs.htm Tue Aug 03 14:05:25 2010 -0500
@@ -27,7 +27,7 @@
<h5>Related references </h5>
<ul>
<li><a href="../reference/view_breakpoints.htm">Breakpoints View</a> </li>
- <li><a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_dbg_brkpt_actions.htm">Breakpoint Actions</a> Preferences</li>
+ <li><a href="../reference/perspective_debug.htm">Breakpoint Actions</a> Preferences</li>
</ul>
<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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_variables.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_variables.htm Tue Aug 03 14:05:25 2010 -0500
@@ -26,7 +26,7 @@
<li><a href="../reference/view_variables.htm">Variables View</a> </li>
<li><a href="../tasks/variables/set_variable_formats.htm">Setting Variable Formats</a></li>
<li><a href="../tasks/variables/show_variables_view.htm">Opening a Variables View</a></li>
- <li><a href="../tasks/variables/show_global_variables.htm">Showing Global Variables</a></li>
+ <li><a href="../reference/perspective_debug.htm">Showing Global Variables</a></li>
</ul>
<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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/workspaces.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/workspaces.htm Tue Aug 03 14:05:25 2010 -0500
@@ -18,7 +18,7 @@
<body bgcolor="#FFFFFF">
<h2>Workspace Information </h2>
<p>A workspace is the default place to store and create resources like projects, folders, and files. These are then presented to the user in a perspective which enables the presentation and manipulation of the stored resources.</p>
-<p>When Carbide is launched it asks for a workspace to open (Figure 1). As you can have multiple workspaces, all independent from each other, choosing the workspace containing the projects to work on is important. Projects within a workspace are shown in the Carbide workbench within the <a href="PLUGINS_ROOT/org.eclipse.platform.doc.user/concepts/cnav.htm">Project Explorer</a> and <a href="../reference/view_proj_explorer.htm">C/C++ Project</a> views. When you create a new project it is automatically added to the currently open workspace. You can import existing projects into a workspace from INF files.</p>
+<p>When Carbide is launched it asks for a workspace to open (Figure 1). As you can have multiple workspaces, all independent from each other, choosing the workspace containing the projects to work on is important. Projects within a workspace are shown in the Carbide workbench within the <a href="../debugger/variables/viewing_variables.htm">Project Explorer</a> and <a href="../reference/view_proj_explorer.htm">C/C++ Project</a> views. When you create a new project it is automatically added to the currently open workspace. You can import existing projects into a workspace from INF files.</p>
<p align="center"><img src="images/wnd_workspace_launcher.png" alt="Workspace Launcher dialog" width="630" height="291"></p>
<p class="figure">Figure 1. Workspace Launcher dialog</p>
<p class="note"><span class="style1">WARNING</span> Bld.inf imported projects are not copied, so do not delete the contents when deleting the project.</p>
--- a/core/com.nokia.carbide.cpp.doc.user/html/context_help/eclipse_dialogs_help.xml Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/context_help/eclipse_dialogs_help.xml Tue Aug 03 14:05:25 2010 -0500
@@ -122,12 +122,6 @@
<topic label="Launch Configurations" href="html/concepts/launch_configuration.htm" />
</context>
- <context id="wizard_trace32_page" >
- <description>Specify Trace32 configuration information.</description>
- <topic label="Creating a Launch Configuration" href="html/tasks/projects/prj_debug_config.htm" />
- <topic label="Symbian OS Trace32 Support" href="html/reference/wnd_Trace32_config.htm" />
- </context>
-
<context id="wizard_trk_connection_page" >
<description>Specify TRK connection information.</description>
<topic label="Creating a Launch Configuration" href="html/tasks/projects/prj_debug_config.htm" />
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/properties_breakpoints.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/properties_breakpoints.htm Tue Aug 03 14:05:25 2010 -0500
@@ -12,7 +12,7 @@
<p>Use the <b>Properties for Breakpoint</b> window to examine and modify a specific breakpoints properties. By setting certain options its possible to create both <a href="conditional_breakpoints.htm">conditional</a> and <a href="temporary_breakpoints.htm">temporary</a> breakpoints. </p>
<p>The pages available include:</p>
<ul>
- <li><b>Actions</b> - define one or more specific <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/tasks/cdt_t_add_brk_action.htm">breakpoint actions</a> like playing a sound or showing an alert message to this breakpoint </li>
+ <li><b>Actions</b> - define one or more specific <a href="properties_breakpoints.htm">breakpoint actions</a> like playing a sound or showing an alert message to this breakpoint </li>
<li><b>Common</b> - shows common information including the class, breakpoint type, file location, and other attributes associated with the breakpoint. </li>
</ul>
<p align="center"><img src="../images/wnd_properties_breakpoints.png" width="628" height="544"></p>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Tue Aug 03 14:05:25 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body bgcolor="#FFFFFF">
<h2> Enabling, Disabling and Removing Breakpoints </h2>
-<p>Use the <b>Toggle Breakpoint</b> command (<span class="code">Ctrl+Shift+B</span>) to set a regular breakpoint in an <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_editor_view.htm">Editor</a> or <a href="../../reference/view_disassembly.htm">Disassembly</a> view. Only a single breakpoint can exist on a source code line. A regular breakpoint suspends program execution when it is hit, or executed, during a debug session. The debugger executes the line of source code that contains the regular breakpoint, then opens the <a href="../../reference/perspective_debug.htm">Debug</a> perspective to allow examination and modification.</p>
+<p>Use the <b>Toggle Breakpoint</b> command (<span class="code">Ctrl+Shift+B</span>) to set a regular breakpoint in an <a href="properties_breakpoints.htm">Editor</a> or <a href="../../reference/view_disassembly.htm">Disassembly</a> view. Only a single breakpoint can exist on a source code line. A regular breakpoint suspends program execution when it is hit, or executed, during a debug session. The debugger executes the line of source code that contains the regular breakpoint, then opens the <a href="../../reference/perspective_debug.htm">Debug</a> perspective to allow examination and modification.</p>
<p>If a regular breakpoint already exists on the selected line, as indicated by the enabled breakpoint badge (<img src="../../tasks/breakpoints/images/breakpoints_enabled_icon.png" width="9" height="10" align="baseline">) in the marker bar, use <b>Toggle Breakpoint</b> to remove the breakpoint.</p>
<h4>Enabling and Disabling breakpoints</h4>
<p>Once a source line is selected in an editor or Disassembly view, the methods of toggling breakpoints to be enabled of disabled include: </p>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/setting_watchpoints.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/setting_watchpoints.htm Tue Aug 03 14:05:25 2010 -0500
@@ -37,8 +37,8 @@
<td><p>Check the appropriate access type to trigger the watchpoint for the specified memory location. This setting is shown as a unique icon in the Breakpoints view next to the listed watchpoint. The following list shows the resolved version of the icons used to indicate the type of watchpoint set:</p>
<ul>
<li>Read only (<img src="../images/icon_watchpoint_read_resolved.png" width="18" height="13" align="absmiddle">)</li>
- <li>Write only (<img src="../../tasks/watchpoints/images/icon_watchpoint_write_resolved.png" width="15" height="16" align="absmiddle">)</li>
- <li>Read/Write (<img src="../../tasks/watchpoints/images/icon_watchpoint_rw_enabled_resolved.png" width="16" height="16" align="absmiddle">)</li>
+ <li>Write only (<img src="setting_watchpoints.htm" width="15" height="16" align="absmiddle">)</li>
+ <li>Read/Write (<img src="setting_watchpoints.htm" width="16" height="16" align="absmiddle">)</li>
</ul></td>
</tr>
</table>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/watchpoints.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/watchpoints.htm Tue Aug 03 14:05:25 2010 -0500
@@ -10,7 +10,7 @@
<body bgcolor="#FFFFFF">
<h2>Watchpoints Overview </h2>
<p> Use <em>watchpoints</em> (sometimes referred to as access breakpoints) to halt program execution when a specific global location is accessed. After you set a watchpoint at a key point in memory, you can halt program execution whenever that point in memory is written to or read from. You can then examine the call chain, check register and variable values, and step through your code. You can also change values and alter the flow of normal program execution.</p>
-<p>A watchpoint must be both enabled and resolved during a debug session in order to halt program execution. The <a href="../reference/view_breakpoints.htm">Breakpoints view</a> indicates the status of any watchpoint using a set of common icons and checkmark status badge. These include:</p>
+<p>A watchpoint must be both enabled and resolved during a debug session in order to halt program execution. The <a href="toggling_watchpoints.htm">Breakpoints view</a> indicates the status of any watchpoint using a set of common icons and checkmark status badge. These include:</p>
<ul>
<li>An <b>enabled</b> watchpoint has a non-gray icon (<img src="../images/icon_watchpoint_write_resolved.png" width="15" height="16" align="absmiddle" />) indicating that program execution halts when encountered.</li>
<li>A <b>disabled</b> watchpoint displays a gray icon (<img src="../images/icon_watchpoint_write_disabled.png" width="16" height="16" align="absmiddle" />) indicating that program execution will not stop when encountered. </li>
@@ -40,8 +40,8 @@
<p> </p>
<p>In addition, you can use these types of watchpoints:</p>
<ul>
- <li><a href="../tasks/watchpoints/pgm_wpt_setting.htm">regular</a> watchpoints—halt program execution</li>
- <li><a href="../tasks/watchpoints/pgm_wpt_conditional.htm">conditional</a> watchpoints—halt program execution after meeting a condition that you specify (same as for breakpoints)</li>
+ <li><a href="setting_watchpoints.htm">regular</a> watchpoints—halt program execution</li>
+ <li><a href="setting_watchpoints.htm">conditional</a> watchpoints—halt program execution after meeting a condition that you specify (same as for breakpoints)</li>
</ul>
<p>A watchpoint is equivalent to a memory breakpoint.</p>
<p>Unlike a breakpoint, a watchpoint can detect when any part of your program affects memory. For example, if a write or write/read watchpoint is set, when the program writes a new value to the address or area of memory that has the watchpoint, the debugger suspends program execution.</p>
@@ -95,21 +95,21 @@
</tr>
</table>
<p>A project can have a different maximum number of watchpoints, depending on the build target. The IDE generally limits the acceptable range for watchpoints to memory that it can write-protect. This range also depends on the host and on the application. </p>
-<p>All set watchpoints appear in the <a href="../reference/view_breakpoints.htm">Breakpoints view</a> list.</p>
+<p>All set watchpoints appear in the <a href="toggling_watchpoints.htm">Breakpoints view</a> list.</p>
<h5>Related concepts</h5>
<ul>
- <li> <a href="breakpoints.htm">Breakpoints</a></li>
+ <li> <a href="toggling_watchpoints.htm">Breakpoints</a></li>
</ul>
<h5>Related tasks </h5>
<ul>
- <li><a href="../tasks/watchpoints/pgm_wpt_setting.htm">Setting Watchpoints</a></li>
- <li><a href="../tasks/watchpoints/pgm_wpt_enable.htm">Enabling Watchpoints</a></li>
- <li><a href="../tasks/watchpoints/pgm_wpt_disable.htm">Disabling Watchpoints</a></li>
+ <li><a href="setting_watchpoints.htm">Setting Watchpoints</a></li>
+ <li><a href="toggling_watchpoints.htm">Enabling Watchpoints</a></li>
+ <li><a href="toggling_watchpoints.htm">Disabling Watchpoints</a></li>
<li><a href="../tasks/watchpoints/pgm_wpt_clearing.htm">Clearing Watchpoints</a></li>
</ul>
<h5>Related references </h5>
<ul>
- <li><a href="../reference/view_breakpoints.htm">Breakpoints view</a> </li>
+ <li><a href="toggling_watchpoints.htm">Breakpoints view</a> </li>
</ul>
<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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Tue Aug 03 14:05:25 2010 -0500
@@ -22,7 +22,6 @@
<li><b><a href="PLUGINS_ROOT/com.nokia.carbide.cpp.debug.crashdebugger/html/view.html">Symbian OS Crash Debugger</a></b> — used to launch an interactive command-line session with the Symbian OS crash debugger when the device crashes </li>
<li><b><a href="emulation.htm">Symbian OS Emulation</a> </b>— used to run or debug executables on an emulator. </li>
<li><b><a href="stop_mode.htm">Symbian OS System TRK</a></b> — used to run or debug applications or ROM code on a target device using the System TRK on-device debug agent. System TRK is an application that runs on reference boards and prototype phones and allows you to debug your executables. The debugger will download files to the phone prior to launching.</li>
- <li><b><a href="trace32.htm">Symbian OS Trace32</a></b> — is an external debugger that the Carbide debugger communicates with, to debug any Symbian OS module on a target using a JTAG connection.</li>
</ul>
<h4>Other references</h4>
<ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_types.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_types.htm Tue Aug 03 14:05:25 2010 -0500
@@ -16,7 +16,6 @@
<li><a href="attach_process.htm">Attach to Process</a></li>
<li><a href="emulation.htm">Emulation</a></li>
<li><a href="stop_mode.htm">System TRK</a></li>
- <li><a href="trace32.htm">Trace32</a></li>
</ul>
<h4>Other references</h4>
<ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm Tue Aug 03 14:05:25 2010 -0500
@@ -12,7 +12,7 @@
<ul>
<li><a href="#emulator_mode">Emulation Debugger page</a> (Emulation) </li>
<li><a href="#trk_runmode">Run-mode Debugger page</a> (Application TRK) </li>
- <li><a href="#trk_stopmode">Stop-mode Debugger page</a> (System TRK, Trace32, Attach to Process) </li>
+ <li><a href="#trk_stopmode">Stop-mode Debugger page</a> (System TRK, Attach to Process) </li>
</ul>
<h3><a name="emulator_mode" id="emulator_mode"></a>Emulation Debugger page </h3>
<p>The <b>Symbian OS <a href="emulation.htm">Emulation</a></b> launch configurations the <b>Debugger</b> page to specify entry point breaks and which logs to output to the Console view.</p>
@@ -88,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>,<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>In stop-mode launch configurations like <b><a href="stop_mode.htm">System TRK</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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Tue Aug 03 14:05:25 2010 -0500
@@ -13,7 +13,7 @@
<ul>
<li><a href="#emulator_mode">Emulation Main page</a> (Emulation) </li>
<li><a href="#run_mode">Run-mode Main page</a> (Application TRK) </li>
- <li><a href="#stop_mode">Stop-Mode Main page</a> (System TRK, Trace32) </li>
+ <li><a href="#stop_mode">Stop-Mode Main page</a> (System TRK) </li>
</ul>
<h3><a name="emulator_mode" id="emulator_mode"></a>Emulation Main page </h3>
<p>The <b>Symbian OS <a href="emulation.htm">Emulation</a></b> launch configuration uses the <b>Main</b> page to define the process to be launched by the emulator. </p>
@@ -88,9 +88,9 @@
</tr>
</table>
<h3><a name="stop_mode" id="stop_mode"></a>Stop-mode Main page </h3>
-<p>The <b>Symbian OS <a href="stop_mode.htm">System TRK</a></b> and <b><a href="trace32.htm">Trace32</a> </b> launch configurations uses the <b>Main</b> page to defines the project and the executable to launch on the target device. </p>
+<p>The <b>Symbian OS <a href="stop_mode.htm">System TRK</a></b> launch configurations uses the <b>Main</b> page to defines the project and the executable to launch on the target device. </p>
<p align="center"><img src="images/page_main_stop_mode.png" width="556" height="301"></p>
-<p class="figure">Figure 3. Main page (<i>TRACE32 shown</i>)</p>
+<p class="figure">Figure 3. Main page</p>
<h5>Table 3. Stop-mode Main page — items</h5>
<table width="94%" border="0" cellpadding="2" cellspacing="0">
<tr>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/stop_mode.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/stop_mode.htm Tue Aug 03 14:05:25 2010 -0500
@@ -9,7 +9,7 @@
<body>
<h2>System TRK Launch Configuration (Stop-mode) </h2>
-<p>Select the <b>Symbian OS System TRK </b> launch configuration provides C/C++ stop-mode debug options that use a JTAG interface when a Symbian OS <a href="trace32.htm">Trace32</a> launch configuration is created. The settings included in these launch configuration are a combination of Carbide, CDT, and Eclipse options. </p>
+<p>Select the <b>Symbian OS System TRK </b> launch configuration provides C/C++ stop-mode debug options that use a JTAG interface when a Symbian OS launch configuration is created. The settings included in these launch configuration are a combination of Carbide, CDT, and Eclipse options. </p>
<p>If the <a href="wiz_new_launch_config.htm">New Launch Configuration Wizard</a> was used to create the System TRK launch configuration no changes are usually needed. To modify the launch configuration settings, select the <b>Run > Debug As</b> menu option to open the <b>Debug</b> dialog. Select the System TRK 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_trace32_launch_config.png" width="832" height="640"></p>
<p class="figure">Figure 1. System TRK launch configuration in the Debug dialog </p>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/trace32.htm Tue Aug 03 13:32:44 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Trace32 Launch Configuration</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h2> Trace32 Launch Configuration</h2>
-<p>Select the <b>Symbian OS Trace32 </b> launch configuration to debug any Symbian OS module on a target using a JTAG connection. The external Trace32 debugger communicates with the Carbide debugger and enables stop mode debugging of the target device. </p>
-<p>If the <a href="wiz_new_launch_config.htm">New Launch Configuration Wizard</a> was used to create a Trace32 launch configuration no changes are usually needed. To modify the launch configuration settings, select the <b>Run > Debug As</b> menu option to open the <b>Debug</b> dialog. Select the Trace32 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_trace32_launch_config.png" width="832" height="640"></p>
-<p class="figure">Figure 1. Trace32 launch configuration in the Debug dialog </p>
-<p>The Trace32 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_connection.htm">Connection</a> tab</li>
- <li>The <a href="page_debugger.htm">Debugger</a> tab defines debug configurations, such as entry point to begin debugging and target options.</li>
- <li>The <a href="page_rom_image.htm">ROM Image</a> tab allows you to define startup options and ROM image download information.</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="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_run_dbg_srce.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="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_run_dbg_comm.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>
-<ul>
- <li><a href="launch_configs_overview.htm">Launch Configuration Overview</a></li>
-</ul>
-<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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Tue Aug 03 14:05:25 2010 -0500
@@ -42,13 +42,6 @@
</ul> </td>
</tr>
<tr>
- <td><b>Trace32</b></td>
- <td><ul>
- <li><a href="#TRACE32">Trace32 Initialization Settings</a></li>
- <li><a href="#ROM_IMG">Symbian ROM Image Settings</a></li>
- </ul> </td>
- </tr>
- <tr>
<td><b>Attach to Process</b></td>
<td><ul>
<li><a href="#TRK_CONN">TRK Connection Settings</a></li>
@@ -91,16 +84,6 @@
<p>If you checkmark <b> Advanced settings</b>, the <a href="../../reference/wnd_debug_configuration.htm">Debug</a> dialog appears instead of launching the project. This enables you to make additional changes to the new launch configuration before starting the debug session. By design and intent, this should seldom be required for the initial launch. </p>
<p align="center"><img src="../../images/icons/wiz_launch_config_finish.png" width="438" height="533"></p>
<p class="figure">Figure 8 - New Launch Configuration page </p>
-<h3><a name="TRACE32" id="TRACE32"></a>Trace32 Initialization Settings</h3>
-<p>Use the <b>Trace32 Initialization Settings</b> page to specify the <a href="trace32.htm">initialization</a> script and target processor of the target device.Enter the Trace32 Initialization Script and choose the Target Processor, then click <b>Next</b>. </p>
-<p> This page only appears when creating a Trace32 launch configuration. </p>
-<p align="center"><img src="../../images/icons/wiz_launch_config_trace32.png" width="438" height="533"></p>
-<p class="figure">Figure 9 - <b>Trace32 Initialization Settings</b> page </p>
-<h3><a name="ROM_IMG" id="ROM_IMG"></a>Symbian ROM Image Settings</h3>
-<p>Use the <b>Symbian ROM Image Settings</b> page to specify the method of <a href="page_debugger.htm">debugging</a>, the start address, and the <a href="page_rom_image.htm">ROM Image</a> and Log File locations. </p>
-<p>This page appears when creating a Trace32 launch configuration. </p>
-<p align="center"><img src="../../images/icons/wiz_launch_config_rom_image.png" width="438" height="533"></p>
-<p class="figure">Figure 10 - Symbian ROM Image Settings page</p>
<h5>Other references</h5>
<ul>
<li><a href="../../projects/launch/launch_configs_overview.htm">Launch Configuration</a> </li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wnd_debug_configuration.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wnd_debug_configuration.htm Tue Aug 03 14:05:25 2010 -0500
@@ -5,14 +5,14 @@
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Debug Configurations Window</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
</head>
<body bgcolor="#FFFFFF">
<h2>Debug Configurations Window</h2>
-<p>The <b>Debug Configurations</b> or launch configuration window provides C/C++ debugger options. A <a href="../projects/launch/launch_configs_overview.htm">launch configuration</a> defines the settings used by the Carbide debugger to launch and debug programs. A project must have at least one debug launch configuration in order to debug a project and can have many more. </p>
-<p>By default, Carbide creates a debug launch configuration the first time you launch the debugger based on current project settings. If additional information is required, like a port ID, the <a href="../projects/launch/wiz_new_launch_config.htm">New Launch Configuration Wizard</a> appears asking for the additional information. </p>
+<p>The <b>Debug Configurations</b> or launch configuration window provides C/C++ debugger options. A <a href="wiz_new_launch_config.htm">launch configuration</a> defines the settings used by the Carbide debugger to launch and debug programs. A project must have at least one debug launch configuration in order to debug a project and can have many more. </p>
+<p>By default, Carbide creates a debug launch configuration the first time you launch the debugger based on current project settings. If additional information is required, like a port ID, the <a href="wnd_config_launch_config.htm">New Launch Configuration Wizard</a> appears asking for the additional information. </p>
<p>The tabs in the window vary depending upon the currently selected launch configuration.</p>
-<p align="center"><img src="images/wnd_debug_overview.png" width="872" height="548"></p>
+<p align="center"><img src="images/wnd_debug_overview.png" width="864" height="471"></p>
<p align="center" class="figure"> Figure 1 - Debug or launch configuration window (Symbian OS emulation view)</p>
<h5>Table 1. Debug Configuration window — common items</h5>
<table width="94%" border="0" cellpadding="2" cellspacing="0">
@@ -51,7 +51,7 @@
<li>Filter Deleted/Unavailable Projects</li>
<li>Filter Configuration Types</li>
<li>Apply Window Working Set(s)</li>
- <li><a href="trk/panel_filter.htm">Filtering Preferences...</a></li>
+ <li><a href="wiz_new_launch_config.htm">Filtering Preferences...</a></li>
</ul></td>
</tr>
</table>
@@ -68,9 +68,9 @@
</div>
<h5>Other references</h5>
<ul>
- <li><a href="perspective_debug.htm">Debug Perspective</a></li>
- <li><a href="../tasks/projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
- <li><a href="../projects/launch/emulation.htm">Emulator overview</a></li>
+ <li><a href="../../debugger/debug/viewing_debug.htm">Debug Perspective</a></li>
+ <li><a href="../../tasks/projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
+ <li><a href="../../tasks/sdks/sdk_platform_filter.htm">Emulator overview</a></li>
<li><a href="../projects/launch/run_mode.htm">Run-mode overview</a></li>
<li><a href="../projects/launch/stop_mode.htm">Stop-mode overview</a> </li>
</ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_console.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_console.htm Tue Aug 03 14:05:25 2010 -0500
@@ -55,7 +55,6 @@
<li>New Emulation Program Output Console</li>
<li>New TRK Program Output Console</li>
<li>New TRK Communications Log Console</li>
- <li>New Trace32 Communications Log Console</li>
<li>New Symbian Rom Log Console</li>
<li>New Emulator Output Console</li>
<li>CVS</li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Tue Aug 03 14:05:25 2010 -0500
@@ -55,7 +55,7 @@
<tr valign="top">
<td class="Cell"><p> <b>Debug process or thread</b> </p></td>
<td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_debug.png" width="22" height="20" alt="" /></div></td>
- <td class="Cell"><p> Click the <b>Debug</b> button to attach to the process and debug the selected process or thread. Or right-click an item and choose <b>Debug</b>. This applies to both TRK (run mode) and Trace32 (stop mode).</p>
+ <td class="Cell"><p> Click the <b>Debug</b> button to attach to the process and debug the selected process or thread. Or right-click an item and choose <b>Debug</b>. This applies to both TRK (run mode) and TCF (stop mode).</p>
</td>
</tr>
<tr valign="top">
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_variables.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_variables.htm Tue Aug 03 14:05:25 2010 -0500
@@ -73,7 +73,7 @@
<h5>Related tasks</h5>
<ul>
<li><a href="../tasks/variables/show_variables_view.htm">Showing the Variables View</a> </li>
- <li><a href="../tasks/variables/show_global_variables.htm">Showing Global Variables</a> </li>
+ <li><a href="perspective_debug.htm">Showing Global Variables</a> </li>
</ul>
<h5>Related References </h5>
<ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/release_notes.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/release_notes.htm Tue Aug 03 14:05:25 2010 -0500
@@ -19,7 +19,6 @@
issues. </p>
<ul>
<li><a href="#whatsNew">What's new </a></li>
- <li><a href="#beta">User notes</a></li>
<li><a href="bugs_fixed.htm">K</a><a href="#issues">nown issues</a></li>
<li><a href="bugs_fixed.htm">Bug Fixes</a></li>
<li><a href="#support">Technical support</a> </li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/soft_attach_debug.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/soft_attach_debug.htm Tue Aug 03 14:05:25 2010 -0500
@@ -9,11 +9,12 @@
</head>
<body bgcolor="#FFFFFF">
<h2>Using Soft Attach for On-Device Debugging</h2>
-<p>You can debug hardware via Trace32 using the soft attach option. This enables you to debug an image flashed to ROM or on a memory card. Soft attach includes all the capabilities fo Stop-mode debugging but can't debug any code loaded before the OS is booted. </p>
+<p align="center" class="fix">NEEDS REWRITING</p>
+<p>You can debug hardware via TCF using the soft attach option. This enables you to debug an image flashed to ROM or on a memory card. Soft attach includes all the capabilities fo Stop-mode debugging but can't debug any code loaded before the OS is booted. </p>
<p>There are several components that must be provided to the debugger so that it can communicate with the attached hardware device. They are:</p>
<ul>
<li><b>Config_carbide.t32</b> - a required configuration file used to configure Carbide for soft attach debugging</li>
- <li><b>.cmm file</b> - you must select the correct .cmm script file for the hardware otherwise it will not initialize properly and the debugger will be unable to communicate. The .cmm script files are located in the <span class="code"><Carbide>\plugins\com.nokia.carbide.cpp.support_2.0.x.xxx\Symbian_Support\Trace32\cmm_scripts</span> directory.<br>
+ <li><b>.cmm file</b> - you must select the correct .cmm script file for the hardware otherwise it will not initialize properly and the debugger will be unable to communicate. The .cmm script files are located in the <span class="code"><Carbide>\plugins\com.nokia.carbide.cpp.support_3.0.x.xxx\Symbian_Support\TCF\cmm_scripts</span> directory.<br>
<br>
Also, if there is a specific .cmm file for the device, like H2 or H4, especially if it includes <span class="code">_attach</span> in the name, choose that version over the others to do soft attach on the hardware. </li>
<li><b>.log file</b> - you must have a valid .log file for the ROM image in order to debug the image </li>
@@ -53,13 +54,13 @@
<li>Click Run > Debug to launch the <a href="../../projects/launch/wiz_new_launch_config.htm">New Launch Configuration Wizard</a></li>
<li>In the Launch Types page
<ol type="a">
- <li>Select the Trace32 Launch Configuration</li>
+ <li>Select the TCF Launch Configuration</li>
<li>Click Next </li>
</ol>
</li>
<li>In the Symbian ROM Image Settings page
<ol type="a">
- <li>Enter the path to the Trace32 Initialization Script .cmm file </li>
+ <li>Enter the path to the TCF Initialization Script .cmm file </li>
<li>Select the Target Processor </li>
<li>Click Next </li>
</ol>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Tue Aug 03 14:05:25 2010 -0500
@@ -7,7 +7,13 @@
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
<style type="text/css">
<!--
-.style1 {font-size: 1em}
+.style6 {font-family: Verdana, Ariel, Helvetica, sans-serif; font-weight: bold; }
+.style8 {font-size: 1em; font-family: Verdana, Ariel, Helvetica, sans-serif; }
+.style11 {font-family: Verdana, Ariel, Helvetica, sans-serif; font-size: medium; }
+.style12 {
+ font-size: 1em;
+ font-weight: bold;
+}
-->
</style>
</head>
@@ -49,11 +55,11 @@
<th width="62%" scope="col">Explanation</th>
</tr>
<tr>
- <td>Project</td>
+ <td><span class="style12">Project</span></td>
<td><p>The project to associate with this debug launch configuration. Click Browse to select a different project.</p></td>
</tr>
<tr>
- <td>Executable</td>
+ <td><span class="style12">Executable</span></td>
<td><span
style="font-weight: normal;">This is the name of the executable that is linked to the project. </span>Click <b>Browse</b> to select a different executable.</td>
</tr>
@@ -69,13 +75,17 @@
<th width="62%" scope="col">Explanation</th>
</tr>
<tr>
- <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Trace32 Executable</b></font></font></p></td>
+ <td><span class="style11">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </span>
+ <p class="style11"><b>Trace32 Executable</b></p></td>
<td><p>Specify the path to the Trace32 executable. The default path assumes that the Trace32 executable is installed in the default location: C:\T32\T32marm.exe.</p></td>
</tr>
<tr>
- <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Trace32 Configuration File</b></font></font></p></td>
+ <td><span class="style11">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </span>
+ <p class="style11"><b>Trace32 Configuration File</b></p></td>
<td>Specify the path to the config.t32 file or other custom configuration file. The default path assumes that the Trace32 configuration file is installed in the default location: C:\T32\config.t32.
<p>For arm11 processors copy the trace32 configuration file for non-ARM11 processor (config_arm11.t32) to your C:\T32 folder and specify it in the edit box.</p>
<p>You can modify the config.t32 file to support UDP (User Datagram Protocol) connections by adding the following lines: <br />
@@ -85,17 +95,21 @@
PORT=20000</p></td>
</tr>
<tr>
- <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
+ <td><span class="style11">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Trace32 Initialization Script</b></font></font></p></td>
+ </span>
+ <p class="style11">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <b>Trace32 Initialization Script</b></p></td>
<td><p>Specify the path to the initialization <span class="code">cmm</span> file. This script will be run in T32 after connecting to T32. You can specify your own scripts for the targets used.</p></td>
</tr>
<tr>
- <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <p><b><font size="2" style="font-size: 9pt">
+ <td><span class="style11">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </font></b><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>View messages between Carbide and Trace32</b></font></font></p></td>
+ </span>
+ <p class="style11"><b>
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ View messages between Carbide and Trace32</b></p></td>
<td>Enable to log communications with Trace32 to the console window.</td>
</tr>
</table>
@@ -110,40 +124,40 @@
<th width="62%" scope="col">Explanation</th>
</tr>
<tr>
- <td><b>Break at entry point</b></td>
+ <td><span class="style6">Break at entry point</span></td>
<td><p>When checked, break at the specified entry point entered in the text field. For .EXE targets, the default entry point is set to <span class="code">E32Main</span>. By default, the <b>Break at entry point</b> option is unchecked for all other target types.</p></td>
</tr>
<tr>
- <td><b>Target Processor </b></td>
+ <td><span class="style6">Target Processor </span></td>
<td>A drop down with a list of all supported processors. The process selection should help in determining the memory model. This will in turn help determine the base address and the offsets for the Symbian OS kernel aware information.</td>
</tr>
<tr>
<td>
- <span class="style1">
+ <span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><font face="Georgia, serif"><b>Target Initialization File</b></font></p></td>
+ <p class="style8"><b>Target Initialization File</b></p></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. Click Browse to select a script file using a standard file selection dialog box.</p>
<p>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>
- <span class="style1">
+ <span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><b><font face="Georgia, serif">Memory Configuration File</font></b></p></td>
+ <p class="style8"><b>Memory Configuration File</b></p></td>
<td>Controls whether the debugger uses a memory configuration file when a debug session starts. The Carbide debugger uses this configuration file to know which memory is accessible, readable, and writable on the target.</td>
</tr>
<tr>
<td>
- <span class="style1">
+ <span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><b><font face="Georgia, serif">Reset target at the start of each debug session</font></b></p></td>
+ <p class="style8"><b>Reset target at the start of each debug session</b></p></td>
<td>Forces the Carbide IDE to reset the target at the start of each debug session. This ensures that the debugging session uses the most up-to-date program code.</td>
</tr>
<tr>
- <td><p><b>Default Instructon Set </b></p></td>
+ <td><p class="style6">Default Instructon Set </p></td>
<td><p>Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. This can happen at addresses for which we have no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code. The options are:</p>
<ul>
<li>Auto (examine code at current PC location) </li>
@@ -164,106 +178,106 @@
<th width="62%" scope="col">Explanation</th>
</tr>
<tr>
- <td><span class="style1">
+ <td><span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><font face="Georgia, serif">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Start Address</b></font></p></td>
+ <p class="style8">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <b>Start Address</b></p></td>
<td><p>Enter the physical address in memory where the Symbian OS start code begins execution. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x8000000 is a valid entry.</p>
<p class="note"><b>NOTE</b> The address entered in this field must match the start address specified in the source code used to build the Symbian OS ROM image to be debugged. The Start address must match the Download address.</p></td>
</tr>
<tr>
- <td><span class="style1">
+ <td><span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><font face="Georgia, serif">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Debug from Start address</b></font></p></td>
+ <p class="style8">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <b>Debug from Start address</b></p></td>
<td>Select this option to have the debugger halt the program at the address specified in Start Address once the target initialization is done and the OS is downloaded; if the user has chosen to download the OS. You can then step through start-up code or run the target in bare-board mode.</td>
</tr>
<tr>
- <td><span class="style1">
+ <td><span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><font face="Georgia, serif">
+ <p class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Run from start address</b></font></p></td>
+ <b>Run from start address</b></p></td>
<td>Select this option to have the debugger start the code at the address specified in Start Address once the target initialization is done. If you have breakpoints set, the debugger stops at the first breakpoint encountered. You can click the Break button to halt the device.</td>
</tr>
<tr>
- <td><span class="style1">
+ <td><span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><font face="Georgia, serif">
+ <p class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Symbian ROM Log file</b></font></p></td>
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <b>Symbian ROM Log file</b></p></td>
<td>Check the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images. In the first text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built.</td>
</tr>
<tr>
- <td><span class="style1">
+ <td><span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><font face="Georgia, serif">
+ <p class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Symbian OS Kit EPOC32 Directory</b></font></p></td>
+ <b>Symbian OS Kit EPOC32 Directory</b></p></td>
<td class="note"><p>Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory.</p>
<p class="note"><b>NOTE</b> Always include the epoc32 folder in this path.</p></td>
</tr>
<tr>
- <td><span class="style1">
+ <td><span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><font face="Georgia, serif">
+ <p class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Log unresolved modules</b></font></p></td>
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <b>Log unresolved modules</b></p></td>
<td class="note"><p>Check this box to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session.</p>
<p class="note"><b>NOTE</b> You cannot perform source-level debugging on components that do not include symbolic information.</p></td>
</tr>
<tr>
- <td><span class="style1">
+ <td><span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><b>
+ <p class="style8"><b>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </b><font face="Georgia, serif">
+ </b>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Debug non-XIP Executables</b></font></p></td>
+ <b>Debug non-XIP Executables</b></p></td>
<td><p>Check this box to debug a project, or a dynamically loaded module, that is loaded from NAND-Flash or other removable media (MMC, memory stick, etc.) at run time and executed in RAM. Use this option to debug modules that work fine when executed in place as part of the ROM image, but sometimes fail when placed in NAND-Flash or other removable media.</p>
<p class="note"> <b>NOTE</b> Selecting this option will affect debugging performance. When the debugger needs to load a module (DLL, EXE, etc.) it will stop the target, read information from it, then restart it.</p></td>
</tr>
<tr>
- <td><span class="style1">
+ <td><span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><b>
+ <p class="style8"><b>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </b><font face="Georgia, serif">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Symbian ROM Image</b></font></p></td>
+ </b>
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <b>Symbian ROM Image</b></p></td>
<td>Controls the logging of communication with Trace32. Enable to log communications with Trace32 to the console window.</td>
</tr>
<tr>
- <td><span class="style1">
+ <td><span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><font face="Georgia, serif"><b>Download Address (hex) </b></font></p></td>
+ <p class="style8"><b>Download Address (hex) </b></p></td>
<td><p>Enter the physical address in memory at which the debugger should place the ROM image. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x000FFF00 is a valid entry.</p>
<p class="note"> <b>NOTE</b> The address entered in this field must match the download address specified in the source code used to build the Symbian OS ROM image to be debugged. If you leave this field blank, the debugger does not download the ROM image to the device at the beginning of the debug session. The Download address must match the Start address.</p></td>
</tr>
<tr>
- <td><span class="style1">
+ <td><span class="style8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><font face="Georgia, serif"><b>Ask for download at the start of each debug session</b></font></p></td>
+ <p class="style8"><b>Ask for download at the start of each debug session</b></p></td>
<td>Check this box to have the debugger display a dialog box at the beginning of every debug session that lets you choose whether or not you want the debugger to download the ROM image to the device.</td>
</tr>
</table>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_dlls.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_dlls.htm Tue Aug 03 14:05:25 2010 -0500
@@ -4,7 +4,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Importing Executables for Debugging</title>
+<title>Debugging DLLs</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
</head>
<body bgcolor="#FFFFFF">
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_multiple_projects.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_multiple_projects.htm Tue Aug 03 14:05:25 2010 -0500
@@ -21,9 +21,7 @@
</ol>
</div>
<h5>Related Tasks</h5>
-<ul>
- <li><a href="prj_import_exe.htm">Importing Executables for Debugging</a></li>
- <li><a href="../WorkingwithSDKs.html">Working with SDKs</a></li>
+<ul><li><a href="../WorkingwithSDKs.html">Working with SDKs</a></li>
</ul>
<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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm Tue Aug 03 13:32:44 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm Tue Aug 03 14:05:25 2010 -0500
@@ -17,13 +17,8 @@
<blockquote>
<p class="note"><b>NOTE</b> You cannot debug ROM DLLs using Application TRK. </p>
</blockquote>
-<ul>
- <li>In Trace32 you must specify the ROM log file in the ROM Image tab of the <a href="../../projects/launch/trace32.htm">Trace32</a> launch configuration</li>
-</ul>
<h5>Other references </h5>
-<ul>
- <li><a href="prj_import_exe.htm">Importing Executables for Debugging</a></li>
- <li><a href="../../projects/launch/trace32.htm">Symbian OS Trace32 Support</a></li>
+<ul><li><a href="../../projects/launch/trace32.htm">Symbian OS Trace32 Support</a></li>
</ul>
<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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_import_exe.htm Tue Aug 03 13:32:44 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Importing a Symbian Executable</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Importing a Symbian Executable</h2>
-<p>Use the <b>File > Import > Symbian OS Executable</b> feature to import an executable into the <a href="../../reference/view_executables.htm">Executables</a> view and debug it. This is useful when the binary is not part of any project in the workspace. An example of this may be a library that is called from an mmp file. The binary must be built with the same build configuration as the current build configuration that is being used (compiler must be the same). </p>
-<p class="note"><b>NOTE</b> You also need the symbolics (.sym) file for debugging ARM build configurations.</p>
-<p class="note"><b>NOTE</b> Binaries built by the project can be debugged by selecting executables to debug in the Executable tab of the launch configuration Debug window.</p>
-<div class="step">
- <h4>To import a Symbian Executable </h4>
- <ol>
- <li>Select the File > Import... menu item</li>
- <p>The Import window appears (Figure 1). </p>
- <p align="center"><img src="images/wnd_import_executable_01.png" width="403" height="469" /></p>
- <p class="figure">Figure 1 - Import window</p>
- <li>Expand Symbian OS and select Symbian OS Executable in the list, then click Next</li>
- <p>The Import Executable window appears (Figure 2). </p>
- <li>Enter the executable name in the Select Executable field or click Browse to locate the executable </li>
- <p>Use the <b>Select executable</b> field to choose a single executable or <b>Search directory</b> field to select one or more Symbian executables to import from the specified directory.</p>
- <p align="center"><img src="images/wnd_import_executable_02.png" width="473" height="491" /></p>
- <p class="figure">Figure 2 - Import Executable window</p>
- <li>Click Finish</li>
- <p>The IDE imports the Symbian executable and displays it in the Executables view (figure 3).</p>
- <p align="center"><img src="images/wnd_import_executable_06.png" width="677" height="164" /></p>
- <p class="figure">Figure 3 - Executables view showing executable and source files </p>
- <p>The new project is listed under the <a href="../../reference/view_proj_explorer.htm">Project Explorer</a> view, as shown in Figure 4.</p>
- <p align="center"><img src="images/wnd_import_executable_05.png" width="252" height="206" /></p>
- <p class="figure">Figure 4 - New executable listed</p>
- </ol>
-</div>
-<h5>Related concepts</h5>
- <ul>
- <li><a href="../../concepts/Projects.html">Projects</a></li>
- <li><a href="../../concepts/Modify.html">Project Resources</a> </li>
- </ul>
- <h5>Related tasks</h5>
- <ul><li><a href="../ImportingProjects.html">Importing Projects</a></li>
- <li><a href="../ImportingProjects.html">Importing BLD.INF Files</a></li>
- <li><a href="prj_debug_rom.htm">Debugging in ROM</a></li>
- </ul>
- <h5>Related references </h5>
- <ul>
- <li><a href="../../reference/ProjectDirectories.html">Project Directories</a></li>
- <li><a href="../../reference/view_executables.htm">Executables view</a> </li>
-</ul>
-
-<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>
\ No newline at end of file