all instances of PLUGINS_ROOT preceded by any path had the path removed (incorrect syntax)
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/breakpoints.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/breakpoints.htm Wed Oct 06 14:30:50 2010 -0500
@@ -10,7 +10,7 @@
<body >
<h2>Breakpoints Overview</h2>
<p> A <b>breakpoint</b> is a marker set on a specific line of source code and is designed to halt program execution when encountered by the debugger. After you set a breakpoint at a key point in the program, you can halt its execution, examine its current state, and check register and variable values. You can also change values and alter the flow of normal program execution. Setting breakpoints helps you debug your program and verify its efficiency.</p>
-<p>A project can have multiple breakpoints set in the source code files. All breakpoints in a project are shown in the <a href="../reference/view_breakpoints.htm">Breakpoints</a> view. Breakpoints are enabled or disabled on the currently selected line within a source code editor by selecting the <b>Run > Toggle Breakpoint</b> menu option, right-clicking the marker bar in the editor and selecting <b>Toggle Breakpoint</b>, or by pressing <span class="code">CTRL-SHIFT-B</span>.</p>
+<p>A project can have multiple breakpoints set in the source code files. All breakpoints in a project are shown in the <a href="../debugger/views/view_breakpoints.htm">Breakpoints</a> view. Breakpoints are enabled or disabled on the currently selected line within a source code editor by selecting the <b>Run > Toggle Breakpoint</b> menu option, right-clicking the marker bar in the editor and selecting <b>Toggle Breakpoint</b>, or by pressing <span class="code">CTRL-SHIFT-B</span>.</p>
<p>You can set a breakpoint on any executable line of code that the debugger can resolve. Lines containing comments and other non executable code cannot be assigned a breakpoint as they are normally stripped from the compiled binary. The debugger must load the symbols for a module before it can attempt to resolve breakpoints within the module. This is most easily done using the <a href="../projects/views/view_executables.htm">Executables</a> view to import a binary file, especially if the binary is not in the workspace. </p>
<p>When the debugger attempts to resolve a breakpoint it will result in:</p>
<ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/common_debug_actions.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/common_debug_actions.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2>Common Debugging Actions</h2>
-<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>
+<p> This section explains how to perform common debugging actions within the <a href="../debugger/views/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/contextual_menus.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/contextual_menus.htm Wed Oct 06 14:30:50 2010 -0500
@@ -13,11 +13,11 @@
<p>Sample uses of the context menu for different tasks include:</p>
<ul>
<li>Editor views - perform editing functions, format, compare, and a host of other file actions </li>
- <li><a href="../reference/view_breakpoints.htm">Breakpoints</a> view - enable, disable, remove, or select all breakpoints</li>
+ <li><a href="../debugger/views/view_breakpoints.htm">Breakpoints</a> view - enable, disable, remove, or select all breakpoints</li>
<li><a href="../debugger/debug/viewing_debug.htm">Debug</a> view - restart, step into, over, or out of routines, terminate or suspend program execution </li>
- <li><a href="../reference/view_memory.htm">Memory</a> view - add or remove memory monitors </li>
+ <li><a href="../debugger/views/view_memory.htm">Memory</a> view - add or remove memory monitors </li>
<li><a href="../projects/views/view_proj_explorer.htm">Project Explorer</a> view - manage projects, build, delete, freeze, run, debug, and other common project commands</li>
- <li><a href="../reference/view_variables.htm">Variables</a> view - enable, disable, find, and change the format or value of variables displayed</li>
+ <li><a href="../debugger/views/view_variables.htm">Variables</a> view - enable, disable, find, and change the format or value of variables displayed</li>
</ul>
<p class="note"><b>TIP</b> Experiment using the context menu in various views to discover additional capabilities.</p>
<p>Figure 1 shows a sample context menu in the Breakpoints view.</p>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/debugger_about.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/debugger_about.htm Wed Oct 06 14:30:50 2010 -0500
@@ -17,11 +17,11 @@
<li>Suspend execution after changing a specified memory value</li>
<li>Suspend any running thread from the stack crawl in the Debug view</li>
</ul>
-<p>After the debugger suspends program execution, use the <a href="../reference/perspective_debug.htm">Debug</a> perspective to perform these tasks:</p>
+<p>After the debugger suspends program execution, use the <a href="../debugger/views/perspective_debug.htm">Debug</a> perspective to perform these tasks:</p>
<ul>
<li><a href="../debugger/debug/viewing_debug.htm">View</a> the function-call chain</li>
- <li><a href="../reference/view_variables.htm">Manipulate</a> variable values</li>
- <li><a href="../reference/view_registers.htm">View</a> register values in the computer processor</li>
+ <li><a href="../debugger/views/view_variables.htm">Manipulate</a> variable values</li>
+ <li><a href="../debugger/views/view_registers.htm">View</a> register values in the computer processor</li>
</ul>
<h5>Related concepts</h5>
<ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm Wed Oct 06 14:30:50 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="../reference/perspective_debug.htm"></script>
+<script language="JavaScript" src="../debugger/views/perspective_debug.htm"></script>
</head>
<body >
<h2>N-Gage Projects</h2>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/registers.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/registers.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,13 +9,13 @@
</head>
<body >
<h2>Registers</h2>
-<p>Use the <a href="../reference/view_registers.htm">Registers</a> view to view the general and specific registers central processing unit (CPU) of the host computer. The exact listing of these registers depends on the host CPU and current build target. </p>
+<p>Use the <a href="../debugger/views/view_registers.htm">Registers</a> view to view the general and specific registers central processing unit (CPU) of the host computer. The exact listing of these registers depends on the host CPU and current build target. </p>
<ul>
<li><a href="#general">General registers</a></li>
<li><a href="#arm">ARM registers</a></li>
</ul>
<h2><a name="general"></a>General registers</h2>
-<p>Registers are the register contents of the central processing unit (CPU) of the host computer or the targeted device. When debugging projects using the emulator, only the host computer x86 registers are visible in the <a href="../reference/view_registers.htm">Registers</a> view. When debugging projects on a device, only the target device registers are visible. </p>
+<p>Registers are the register contents of the central processing unit (CPU) of the host computer or the targeted device. When debugging projects using the emulator, only the host computer x86 registers are visible in the <a href="../debugger/views/view_registers.htm">Registers</a> view. When debugging projects on a device, only the target device registers are visible. </p>
<p>In most cases, the contents of all the registers can be modified. However, when debugging applications on a target device with Symbian Device (Install SIS), you cannot change the LR and SP registers.</p>
<p align="center"><img src="images/view_registers.png" width="463" height="260"></p>
<p class="figure">Figure 1. Registers view with possible register types</p>
@@ -41,7 +41,7 @@
<p align="left" class="figure">Figure 2 - ARM Registers </p>
<h5>Other references <b></b></h5>
<ul>
- <li><a href="../reference/view_registers.htm">Registers</a> view</li>
+ <li><a href="../debugger/views/view_registers.htm">Registers</a> view</li>
<li><a href="../tasks/registers/mem_reg_open_wnd.htm">Opening a Registers View</a></li>
<li><a href="../tasks/registers/mem_reg_changing.htm">Changing Register Values</a></li>
</ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/watchpoints.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/watchpoints.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,12 +9,12 @@
</head>
<body >
<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="../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>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="../debugger/views/perspective_debug.htm">Breakpoints</a> view. </p>
+<p>When a watchpoint is encountered during program execution, the debugger suspends execution and the <a href="../debugger/views/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="../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/views/perspective_debug.htm">Viewing Breakpoints and Watchpoints</a> </li>
+ <li><a href="../debugger/views/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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_debugger.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_debugger.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2>Debugger Program Execution </h2>
-<p> This section explains how to work with the debugger in the Carbide IDE to control program execution. The main component of the debugger is the <a href="../reference/perspective_debug.htm">Debug perspective</a>, which shows these items:</p>
+<p> This section explains how to work with the debugger in the Carbide IDE to control program execution. The main component of the debugger is the <a href="../debugger/views/perspective_debug.htm">Debug perspective</a>, which shows these items:</p>
<ul>
<li>Common debugging controls in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> view for:
<ul>
@@ -21,8 +21,8 @@
<li><a href="../debugger/debug/cmds_resuming.htm">Restarting</a> the debugger</li>
</ul>
</li>
- <li>Variable information in the <a href="../reference/view_variables.htm">Variables</a> view—see the variables in the executing code, their <a href="../reference/perspective_debug.htm">values</a>, and their <a href="working_with_variables.htm">types</a></li>
- <li>Breakpoint information in the <a href="../reference/view_breakpoints.htm">Breakpoints</a> view—see the <a href="../tasks/breakpoints/pgm_bp_enable.htm">breakpoints</a>, <a href="../tasks/breakpoints/pgm_bp_conditional.htm">conditional</a> breakpoints, and <a href="working_with_debugger.htm">breakpoint actions</a></li>
+ <li>Variable information in the <a href="../debugger/views/view_variables.htm">Variables</a> view—see the variables in the executing code, their <a href="../debugger/views/perspective_debug.htm">values</a>, and their <a href="working_with_variables.htm">types</a></li>
+ <li>Breakpoint information in the <a href="../debugger/views/view_breakpoints.htm">Breakpoints</a> view—see the <a href="../tasks/breakpoints/pgm_bp_enable.htm">breakpoints</a>, <a href="../tasks/breakpoints/pgm_bp_conditional.htm">conditional</a> breakpoints, and <a href="working_with_debugger.htm">breakpoint actions</a></li>
<li>Source code—see the source code under debugger control</li>
</ul>
<h5>Related concepts</h5>
@@ -33,11 +33,11 @@
</ul>
<h5>Related references</h5>
<ul>
- <li><a href="../reference/perspective_debug.htm">Debug Perspective</a></li>
+ <li><a href="../debugger/views/perspective_debug.htm">Debug Perspective</a></li>
<li><a href="../debugger/debug/viewing_debug.htm">Debug View</a> </li>
- <li><a href="../reference/view_expressions.htm">Expressions View</a></li>
- <li><a href="../reference/view_variables.htm">Variables View</a></li>
- <li><a href="../reference/view_breakpoints.htm">Breakpoints View </a> </li>
+ <li><a href="../debugger/views/view_expressions.htm">Expressions View</a></li>
+ <li><a href="../debugger/views/view_variables.htm">Variables View</a></li>
+ <li><a href="../debugger/views/view_breakpoints.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/concepts/working_with_memory.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_memory.htm Wed Oct 06 14:30:50 2010 -0500
@@ -11,8 +11,8 @@
<h2>Working with Memory</h2>
<p> This section explains how to work with memory in a debugging session. Topics include:</p>
<ul>
- <li><a href="../reference/view_memory.htm">Memory</a> view —shows the memory that your project manipulates as it executes</li>
- <li><a href="../reference/view_registers.htm">Registers</a> view—shows the register contents of a processor</li>
+ <li><a href="../debugger/views/view_memory.htm">Memory</a> view —shows the memory that your project manipulates as it executes</li>
+ <li><a href="../debugger/views/view_registers.htm">Registers</a> view—shows the register contents of a processor</li>
</ul>
<h5>Related tasks</h5>
<ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_programs.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_programs.htm Wed Oct 06 14:30:50 2010 -0500
@@ -26,8 +26,8 @@
</ul>
<h5>Related references </h5>
<ul>
- <li><a href="../reference/view_breakpoints.htm">Breakpoints View</a> </li>
- <li><a href="../reference/perspective_debug.htm">Breakpoint Actions</a> Preferences</li>
+ <li><a href="../debugger/views/view_breakpoints.htm">Breakpoints View</a> </li>
+ <li><a href="../debugger/views/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 Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_variables.htm Wed Oct 06 14:30:50 2010 -0500
@@ -17,16 +17,16 @@
<h2>Working with Variables</h2>
<p> This section explains how to work with variables in a Carbide™ IDE debugging session. The following windows show various types of information about variables.</p>
<ul>
- <li><a href="../reference/view_variables.htm">Variables</a> view — <span class="style2">shows information about global and static variables in your project</span></li>
- <li><a href="../reference/view_expressions.htm">Expressions</a> window— shows variable values and lets you form calculation expressions based on those values</li>
+ <li><a href="../debugger/views/view_variables.htm">Variables</a> view — <span class="style2">shows information about global and static variables in your project</span></li>
+ <li><a href="../debugger/views/view_expressions.htm">Expressions</a> window— shows variable values and lets you form calculation expressions based on those values</li>
</ul>
<h5>Related references</h5>
<ul>
- <li><a href="../reference/view_expressions.htm">Expressions view</a></li>
- <li><a href="../reference/view_variables.htm">Variables View</a> </li>
+ <li><a href="../debugger/views/view_expressions.htm">Expressions view</a></li>
+ <li><a href="../debugger/views/view_variables.htm">Variables View</a> </li>
<li><a href="working_with_variables.htm">Setting Variable Formats</a></li>
- <li><a href="../reference/perspective_debug.htm">Opening a Variables View</a></li>
- <li><a href="../reference/perspective_debug.htm">Showing Global Variables</a></li>
+ <li><a href="../debugger/views/perspective_debug.htm">Opening a Variables View</a></li>
+ <li><a href="../debugger/views/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 Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/workspaces.htm Wed Oct 06 14:30:50 2010 -0500
@@ -28,7 +28,7 @@
<h4>Other references</h4>
<ul>
<li><a href="../projects/views/perspective_carbide.htm">Carbide.c++ perspective </a></li>
- <li><a href="../reference/perspective_debug.htm">Debug perspective </a></li>
+ <li><a href="../debugger/views/perspective_debug.htm">Debug perspective </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/debugger/breakpoints/breakpoints.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/breakpoints.htm Wed Oct 06 14:30:50 2010 -0500
@@ -10,7 +10,7 @@
<body >
<h2>Breakpoints Overview </h2>
<p>A <b>breakpoint</b> is a marker set on a specific line of source code and is designed to suspend program execution. Breakpoints are shown in the UI both with the associated source code in an editor view as well as a dedicated <a href="viewing_breakpoints.htm">Breakpoints</a> view. </p>
-<p>When a breakpoint 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 breakpoints helps you debug your program and verify its efficiency.</p>
+<p>When a breakpoint is encountered during program execution, the debugger suspends execution and the <a href="../views/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 breakpoints 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="viewing_breakpoints.htm">Viewing Breakpoints</a></li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/conditional_breakpoints.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/conditional_breakpoints.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2> Creating Conditional Breakpoints </h2>
-<p>Use the <b>Properties for Breakpoint > Common > Conditional</b> option to create conditional breakpoints. Where regular breakpoints suspend execution each time they are hit, a condition breakpoint evaluates an expression to determine if it is true or not. If the expression evaluates true, then program execuation is suspended and the <a href="../../reference/perspective_debug.htm">Debug</a> perpective shown. If the expression evaluates to false, execution continues. </p>
+<p>Use the <b>Properties for Breakpoint > Common > Conditional</b> option to create conditional breakpoints. Where regular breakpoints suspend execution each time they are hit, a condition breakpoint evaluates an expression to determine if it is true or not. If the expression evaluates true, then program execuation is suspended and the <a href="../views/perspective_debug.htm">Debug</a> perpective shown. If the expression evaluates to false, execution continues. </p>
<p align="center"><img src="../images/option_condition.png" width="434" height="202"></p>
<p class="figure">Figure 1. Condition field in Properties for Breakpoint window </p>
<p>You create a conditional breakpoint in the <b>Conditional</b> field by entering a valid expression. Valid expressions include:</p>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/importing_breakpoints.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/importing_breakpoints.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2> Importing Breakpoints and Watchpoints</h2>
-<p>Use the <b>Import Breakpoints</b> command to import a <span class="code">.bkpt</span> file containing breakpoint and watchpoint data and apply it to the current project. Right-click in the <a href="../../reference/view_breakpoints.htm">Breakpoints</a> view and select <b>Import Breakpoints...</b> from the context menu. You have the options of updating all existing breakpoints with the stored data or simply creating a working set containing the imported data. </p>
+<p>Use the <b>Import Breakpoints</b> command to import a <span class="code">.bkpt</span> file containing breakpoint and watchpoint data and apply it to the current project. Right-click in the <a href="../views/view_breakpoints.htm">Breakpoints</a> view and select <b>Import Breakpoints...</b> from the context menu. You have the options of updating all existing breakpoints with the stored data or simply creating a working set containing the imported data. </p>
<p align="center"><img src="../images/wnd_import_breakpoints.png" width="438" height="415"></p>
<p class="figure">Figure 2 - Import Breakpoints dialog </p>
<table cellspacing="0" cellpadding="5" summary="Import breakpoints page" border="1">
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/resolving_breakpoints.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/resolving_breakpoints.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2> Breakpoint Status Indicators </h2>
-<p>Breakpoints must be located and resolved by the debugger before they can be hit. When a breakpoint is hit in the module, the debugger halts program execution and displays the state of the program in the <a href="../../reference/perspective_debug.htm">Debug</a> perspective. </p>
+<p>Breakpoints must be located and resolved by the debugger before they can be hit. When a breakpoint is hit in the module, the debugger halts program execution and displays the state of the program in the <a href="../views/perspective_debug.htm">Debug</a> perspective. </p>
<p>To hit a breakpoint during a debug session, the debugger must first load the symbols for an executable module and then attempt to resolve the breakpoints within the loaded module. Any module listed into the <a href="../../projects/views/view_executables.htm">Executables</a> view is available for loading by a debug session. If a module is not present in the Executable view you'll need to import it before the debugger to load and resolve any breakpoints within that module. </p>
<p>You set a breakpoint on any executable line of code that the debugger can resolve. Lines containing comments and other non executable code cannot be assigned a breakpoint as they are normally stripped from the compiled binary. Carbide helps by preventing you from setting a breakpoint on a non-compilable line of code. </p>
<p>When the debugger attempts to resolve a breakpoint the possible results are shown in Table 1.</p>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<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="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>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="../views/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="../views/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>
@@ -20,7 +20,7 @@
<li>Double-click in the marker bar to enable or disable a breakpoint on that source line </li>
</ul>
<h4>Removing breakpoints</h4>
-<p>In the <a href="../../reference/view_breakpoints.htm">Breakpoints</a> view, locate the source code line to modify and: </p>
+<p>In the <a href="../views/view_breakpoints.htm">Breakpoints</a> view, locate the source code line to modify and: </p>
<ul>
<li>Right-click the breakpoint and choose <b>Remove</b> from the context menu to remove the breakpoint </li>
</ul>
@@ -28,7 +28,7 @@
<p>Breakpoints must first be loaded and resolved before they can be hit during a debug session. See <a href="resolving_breakpoints.htm">Resolving Breakpoint States</a> for more information on the various states a breakpoint can exhibit. </p>
<p>See <a href="exporting_breakpoints.htm">Saving and importing breakpoints</a> for information on storing breakpoint data sets for sharing or re-use. </p>
<p class="note"><strong>TIP</strong> If you find that a breakpoint is not being hit during a debug session, verify that the EXE or DLL is listed in the <a href="../../projects/views/view_executables.htm">Executables</a> view. </p>
-<p class="note"><strong>TIP</strong> If debugging a server launched by a client, you must attach to the server process using the <a href="../../reference/view_symbian_kernel.htm">Symbian Data</a> view in order to hit the breakpoints in the server. Alternately, you can launch the server and client as two independent EXEs using the same COM port and debug them that way.</p>
+<p class="note"><strong>TIP</strong> If debugging a server launched by a client, you must attach to the server process using the <a href="../views/view_symbian_kernel.htm">Symbian Data</a> view in order to hit the breakpoints in the server. Alternately, you can launch the server and client as two independent EXEs using the same COM port and debug them that way.</p>
<h4>Other references</h4>
<ul>
<li><a href="breakpoints.htm">Breakpoints overview </a></li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/viewing_breakpoints.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/viewing_breakpoints.htm Wed Oct 06 14:30:50 2010 -0500
@@ -10,7 +10,7 @@
<body >
<h2>Viewing Breakpoints and Watchpoints </h2>
<p>Use the <b>Breakpoints</b> view (Figure 1) to <a href="properties_breakpoints.htm">examine</a> a project's breakpoints and watchpoints, <a href="toggling_breakpoints.htm">toggle</a> individual breakpoints between enabled and disabled, set <a href="conditional_breakpoints.htm">conditional</a> breakpoints, <a href="exporting_breakpoints.htm">export</a> and <a href="importing_breakpoints.htm">import</a> breakpoints, or remove them from one or more build configurations. </p>
-<p>The <b>Breakpoints</b> view is available in the <a href="../../reference/perspective_debug.htm">Debug</a> perspective by default. To open it in another perspective, use the <b>Window > Show View > Breakpoints</b> menu option. Once open you have control over breakpoint states and how they are shown. For example: </p>
+<p>The <b>Breakpoints</b> view is available in the <a href="../views/perspective_debug.htm">Debug</a> perspective by default. To open it in another perspective, use the <b>Window > Show View > Breakpoints</b> menu option. Once open you have control over breakpoint states and how they are shown. For example: </p>
<ul>
<li>Click a check box next to a breakpoint to toggle its state between enabled (checked) and disabled (no checkmark) </li>
<li>Double-click a breakpoint to open the associated source file at the breakpoint line number in an editor view</li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/debug/cmds_reposition_pc.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/debug/cmds_reposition_pc.htm Wed Oct 06 14:30:50 2010 -0500
@@ -17,7 +17,7 @@
</head>
<body >
<h2>Repositioning the Program Counter</h2>
-<p>Once you've <a href="cmds_resuming.htm">suspended</a> a program debug session, the <a href="../../reference/view_disassembly.htm">Disassembly</a> view provides commands for move or reposition the program counter (PC). These command include:</p>
+<p>Once you've <a href="cmds_resuming.htm">suspended</a> a program debug session, the <a href="../views/view_disassembly.htm">Disassembly</a> view provides commands for move or reposition the program counter (PC). These command include:</p>
<ul>
<li><a href="#RUN_TO">Run to Line (C/C++)</a></li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/debug/debug.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/debug/debug.htm Wed Oct 06 14:30:50 2010 -0500
@@ -21,7 +21,7 @@
</ul>
<h4>Other references</h4>
<ul>
- <li><a href="../../reference/perspective_debug.htm">Debug perspective</a></li>
+ <li><a href="../views/perspective_debug.htm">Debug perspective</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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/variables/adding_expressions.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/variables/adding_expressions.htm Wed Oct 06 14:30:50 2010 -0500
@@ -10,7 +10,7 @@
<body >
<h2>Adding and Removing Expressions</h2>
<p>An <i>expression</i> is a snippet of code that is evaluated to produce a value. In Carbide they are defined using C/C++ expressions. Some expressions may need to be evaluated at a specific location in the program so that its variables can be referenced. Adding more expressions to the <a href="viewing_expressions.htm">Expressions</a> view list can slow down the automatic display as each must be evaluated to update its value. To manage large lists of expressions, use the <b>Enable</b> and <b>Disable</b> options in the context menu to control which expressions are automatically evaluated.</p>
-<p>You add expressions in the <b>Add Watch Expression</b> dialog using a variety of views, including <a href="../../reference/view_expressions.htm">Expressions</a>, <a href="../../reference/view_variables.htm">Variables</a>, and editor views. Right-click in the view and select the <b>Add Watch Expression...</b> command from the context menu.</p>
+<p>You add expressions in the <b>Add Watch Expression</b> dialog using a variety of views, including <a href="../views/view_expressions.htm">Expressions</a>, <a href="../views/view_variables.htm">Variables</a>, and editor views. Right-click in the view and select the <b>Add Watch Expression...</b> command from the context menu.</p>
<p align="center"><img src="../images/wnd_add_watch_expr.png"></p>
<p class="figure">Figure 1. Add Watch Expression dialog</p>
<p>You can enter any valid C/C++ expression, for example:</p>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/variables/viewing_variables.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/variables/viewing_variables.htm Wed Oct 06 14:30:50 2010 -0500
@@ -100,7 +100,7 @@
</tr>
<tr>
<td><b>View Memory</b></td>
- <td>Opens a <a href="../../reference/view_memory.htm">Memory</a> view on the selected variable so you can examine it.</td>
+ <td>Opens a <a href="../views/view_memory.htm">Memory</a> view on the selected variable so you can examine it.</td>
</tr>
<tr>
<td><b>Format</b></td>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/perspective_debug.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,53 @@
+<!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>Debug perspective</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+</head>
+<body >
+<h2>Debug perspective</h2>
+<p>The Carbide.c++ <img src="../../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.debug.ui.DebugPerspective)")'>
+Debug</a> perspective is where you debug programs running on an emulator or a target device. The default views include:</p>
+<ul>
+ <li><a href="../debug/viewing_debug.htm">Debug</a> view - displays information about a suspended process during a debug session</li>
+ <li><a href="view_variables.htm">Variables</a> view - allows manipulation of variables used in source code</li>
+ <li><a href="view_breakpoints.htm">Breakpoints</a> view - allows manipulation of breakpoints and watchpoints</li>
+ <li><a href="view_symbian_kernel.htm">Symbian OS Data</a> view - shows kernel data in the Symbian running on the device being debugged</li>
+ <li><a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_editor_view.htm">Editor</a> view - one or more source code editor windows </li>
+ <li><a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_outline_view.htm">Outline</a> view - displays an outline of a structured C/C++ file that is currently open in the
+ editor view </li>
+ <li><a href="../../projects/views/view_console.htm">Console</a> view - display<span><span>s the output of a process</span></span>, like the execution of your program, or other outputs </li>
+ <li><a href="PLUGINS_ROOT/org.eclipse.platform.doc.user/reference/ref-31.htm">Tasks</a> view - <span>displays </span>tasks that you manually add</li>
+ <li><a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_problems_view.htm">Problems</a> view - displays build errors </li>
+ <li><a href="../../projects/views/view_executables.htm">Executables</a> view - provides a dynamic list of executables and their related source files</li>
+</ul>
+<p>And can include:</p>
+<ul>
+ <li><a href="view_memory.htm">Memory</a> view - allows you to monitor and modify process memory</li>
+ <li><a href="view_disassembly.htm">Disassembly</a> view - displays the assembly code of the source code currently being debugged </li>
+ <li><a href="view_expressions.htm">Expressions</a> view - used to monitor and manipulate global and local variables, structure members, and array elements</li>
+ <li><a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_modules_view.htm">Modules</a> view - uses the <a href="../../projects/launch/wiz_new_launch_config.htm">Symbolics Loading</a> option to show modules loaded during a debug session </li>
+ <li><a href="view_registers.htm">Registers</a> view - shows general, FPU, or host-specific registers of the host computer or target device</li>
+</ul>
+<p align="center"><img src="../../images/views/perspective_debug.png" width="1028" height="789" alt="" /></p>
+<p class="figure">Figure 1. Debug perspective used by Carbide.c++</p>
+<p class="note"><b>NOTE</b> Click the <img src="../../images/icons/double_arrow_icon.png" width="12" height="9" valign="absmiddle" alt="" /> icon to show additional options that may not be visible in the perspective view.</p>
+<p>For more information on perspectives see <b>Workbench User Guide > Concepts > <a href="PLUGINS_ROOT/org.eclipse.platform.doc.user/concepts/concepts-4.htm">Perspectives</a></b>, and for views see <b>C/C++ Development User Guide > Reference
+> <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_o_views.htm">C/C++ Views and Editors</a></b>.</p>
+<h5>Related references</h5>
+<ul>
+ <li> <a href="../../projects/views/perspective_carbide.htm">Carbide C/C++ Perspective</a></li>
+ <li><a href="../debug/viewing_debug.htm">Debug view</a></li>
+ <li><a href="view_variables.htm">Variables view</a></li>
+ <li><a href="view_breakpoints.htm">Breakpoints view</a></li>
+ <li><a href="view_memory.htm">Memory view</a></li>
+ <li><a href="view_symbian_kernel.htm">Symbian Data 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
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_breakpoints.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,80 @@
+<!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>Breakpoints View</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body >
+<h2>Breakpoints View </h2>
+<p>Use the <b>Breakpoints</b> view to <a href="../../tasks/breakpoints/pgm_bp_setting.htm">set</a>, <a href="../../tasks/breakpoints/pgm_bp_view_props.htm">examine</a>, <a href="../../tasks/breakpoints/pgm_bp_enable.htm">enable</a>, <a href="../../tasks/breakpoints/pgm_bp_disable.htm">disable</a>, and <a href="../../tasks/breakpoints/pgm_bp_clearing.htm">remove</a> breakpoints and <a href="../../tasks/watchpoints/pgm_watchpoints.htm">watchpoints</a> in one or more <a href="../../concepts/build_configurations.htm">build configurations</a>. Table 1 explains items in the view.</p>
+<p align="center"><img src="../../reference/images/view_breakpoints.png" width="544" height="264" /></p>
+<p class="figure">Figure 1 - Breakpoints view</p>
+<h5>Table 1. Breakpoints view—items </h5>
+<table width="100%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="27%" scope="col">Item</th>
+ <th width="11%" scope="col">Icon</th>
+ <th width="62%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Remove Selected Breakpoint </b></td>
+ <td><div align="center"><img src="../../images/icons/breakpoints_remove_one_icon.png" width="19" height="19" /></div></td>
+ <td>Removes the selected breakpoint from the breakpoints list. </td>
+ </tr>
+ <tr>
+ <td><b>Remove All Breakpoints </b></td>
+ <td><div align="center"><img src="../../images/icons/breakpoints_remove_all_icon.png" width="21" height="19" /></div></td>
+ <td>Removes all breakpoints from the breakpoints list. </td>
+ </tr>
+ <tr>
+ <td><b>Show Breakpoints Supported by Selected Target </b></td>
+ <td><div align="center"><img src="../../images/icons/breakpoints_show_icon.png" width="20" height="19" /></div></td>
+ <td>Limits the breakpoints shown to only those supported in the current target. </td>
+ </tr>
+ <tr>
+ <td><b>Go to File for Breakpoint </b></td>
+ <td><div align="center"><img src="../../images/icons/breakpoints_goto_icon.png" width="20" height="19" /></div></td>
+ <td>Displays the breakpoint in an editor view, opening the source file if required. </td>
+ </tr>
+ <tr>
+ <td><b>Skip All Breakpoints </b></td>
+ <td><div align="center"><img src="../../images/icons/breakpoints_skip_all_icon.png" width="19" height="19" /></div></td>
+ <td>Toggles the debugger to skip all breakpoints regardless of their current enabled or disabled state, or hit all breakpoints.</td>
+ </tr>
+ <tr>
+ <td><b>Expand All </b></td>
+ <td><div align="center"><img src="../../images/icons/breakpoints_collapse_icon.png" width="19" height="18" /></div></td>
+ <td>Expand all matches in the hierarchical view.</td>
+ </tr>
+ <tr>
+ <td><b>Collapse All </b></td>
+ <td><div align="center"><img src="../../images/icons/breakpoints_expand_icon.png" width="19" height="18" /></div></td>
+ <td>Collapse all matches in the hierarchical view.</td>
+ </tr>
+ <tr>
+ <td><b>Link with Debug View</b></td>
+ <td><div align="center"><img src="../../images/icons/breakpoints_linkto_debug_icon.png" width="20" height="19" /></div></td>
+ <td>When enabled, the breakpoint shown in the editor view is also highlighted in the Breakpoints view. When disabled, the breakpoint selected in the Breakpoints view does not change. </td>
+ </tr>
+ <tr>
+ <td><b>Menu</b></td>
+ <td><div align="center"><img src="../../reference/images/icon_breakpoint_menu.png" width="16" height="9" /></div></td>
+ <td>Click to display additional Breakpoint view options for paths and working sets. </td>
+ </tr>
+</table>
+ <h5>Other references</h5>
+ <ul>
+ <li><a href="perspective_debug.htm">Debug Perspective </a></li>
+ <li><a href="../../concepts/breakpoints.htm">Breakpoints</a></li>
+ <li><a href="../../tasks/breakpoints/pgm_bp_setting.htm">Setting Breakpoints</a></li>
+ <li><a href="../../tasks/breakpoints/pgm_bp_enable.htm">Enabling Breakpoints</a></li>
+ <li><a href="../../tasks/breakpoints/pgm_bp_disable.htm">Disabling Breakpoints</a></li>
+ <li><a href="../../tasks/breakpoints/pgm_bp_clearing.htm">Removing Breakpoints</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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_disassembly.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,124 @@
+<!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>Disassembly Window</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<style type="text/css">
+<!--
+.style1 {
+ color: #FF0000;
+ font-weight: bold;
+}
+-->
+</style>
+</head>
+<body >
+<h2>Disassembly View</h2>
+<p> When debugging your application, the <b>Disassembly</b> view shows the loaded program as assembler instructions. When you use the Disassembly view, you can do the following tasks:</p>
+<ul>
+ <li>Step through the disassembly instructions of your program using the <b>Instruction Stepping Mode</b> (<img src="../../reference/images/icon_instr_stepping_mode.png" width="18" height="16" align="absmiddle">) icon in the <a href="../debug/viewing_debug.htm">Debug</a> view (Figure 1). </li>
+ <li>Reposition the PC using the various move commands (Figure 1) by first selecting the line to move to, then select the command from the context menu.</li>
+ <li>Set breakpoints at the start of any assembler instruction by right-clicking the left hand column to view the context menu options (Figure 2) </li>
+</ul>
+<p>Figure 1 shows the <b>Dissassembly</b> view stopped at a breakpoint.</p>
+<p align="center"><img src="../../reference/images/view_disassembly.png" width="555" height="272" alt="" /></p>
+<p class="figure">Figure 1 - Disassembly view</p>
+<p>Figure 2 shows the context menu that appears when you right-click in the Dissassembly pane. Right-clicking the left border opens the breakpoint context menu in Figure 3.</p>
+<p class="figure"><img src="../../reference/images/view_disassembly_menu.png" width="232" height="133"></p>
+<p class="figure">Figure 2 - Disassembly pane context menu</p>
+<h5>Table 1. Disassembly pane — context menu</h5>
+<table width="88%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="26%" scope="col">Item</th>
+ <th width="8%" scope="col">Icon</th>
+ <th width="66%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Run to Line </b></td>
+ <td><center>
+ <img src="../../reference/images/icon_dis_run_to_line.png" width="18" height="18">
+ </center></td>
+ <td>Select <b>Run to Line</b> to execute the program from the currently executed line (the green line) to the selected line (the blue line).</td>
+ </tr>
+ <tr>
+ <td><b>Move to Line</b></td>
+ <td><center>
+ <img src="../../reference/images/icon_dis_move_to_line.png" width="19" height="15">
+ </center></td>
+ <td><p>Select <b>Move to Line</b> to move the program counter to the selected line (the blue line) skipping all intermediate lines but not resume execution. This enables you to skip suspect code and continue stepping through your program.</p>
+ <p class="note"><span class="style1">WARNING</span> Using this command can leave a program in an unstable state. Use at your own risk.</p></td>
+ </tr>
+ <tr>
+ <td><b>Resume at Line </b></td>
+ <td><center>
+ <img src="../../reference/images/icon_dis_resume_at_line.png" width="18" height="14">
+ </center></td>
+ <td><p>Select <b>Resume at Line</b> to begin program execution at the selected line (the blue line), skipping all lines between it and the currently executed line (the green line). </p>
+ <p class="note"><span class="style1">WARNING</span> Using this command can leave a program in an unstable state. Use at your own risk.</p></td>
+ </tr>
+ <tr>
+ <td><b>ABLD</b></td>
+ <td> </td>
+ <td>Use the <a href="../../reference/menus/abld.htm">ABLD</a> menu option to invoke an specific <span class="code">abld</span> command on the selected project or file.</td>
+ </tr>
+ <tr>
+ <td><b>Freeze Exports</b></td>
+ <td><center>
+ <img src="../../reference/images/icon_freeze_exports.png" width="19" height="18">
+ </center>
+ </td>
+ <td>Calls the appropriate <span class="code">abld</span> command to generate a .def file.</td>
+ </tr>
+ <tr>
+ <td><b>Build All Configurations</b></td>
+ <td><center>
+ <img src="../../reference/images/icon_build_all_configs.png" width="20" height="18">
+ </center>
+ </td>
+ <td>Click <b>Build All Configurations</b> to build all enabled build configurations in the current project.</td>
+ </tr>
+ <tr>
+ <td><b>Toggle Breakpoint </b></td>
+ <td><center>
+ </center></td>
+ <td>Right-click in left-hand column of the Disassembly view and select this option to toggle the breakpoint state between <a href="../../tasks/breakpoints/pgm_bp_setting.htm">setting</a> and <a href="../../tasks/breakpoints/pgm_bp_clearing.htm">removing</a> the breakpoint. </td>
+ </tr>
+ <tr>
+ <td><b>Disable/Enable Breakpoint </b></td>
+ <td><center>
+ </center></td>
+ <td>Right-click in left-hand column of the Disassembly view and select the breakpoint option shown as determined by the current state of the breakpoint.</td>
+ </tr>
+ <tr>
+ <td><b>Breakpoint Properties </b></td>
+ <td><center>
+ </center></td>
+ <td>Select this option to open the <b>Breakpoint Properties</b> dialog. </td>
+ </tr>
+</table>
+<p class="figure"><img src="../../reference/images/view_disassm_breakpoint.png" width="506" height="172" alt="" /></p>
+<p class="figure">Figure 3 - Setting Breakpoints in the Disassembly view </p>
+<div class="step">
+ <h4>Opening the Disassembly view </h4>
+ <ul>
+ <li>Select Window > Show View > Disassembly </li>
+ </ul>
+ <blockquote>
+ <p>OR</p>
+ </blockquote>
+ <ul>
+ <li>Click the Instruction Stepping Mode (<img src="../../reference/images/icon_instr_stepping_mode.png" width="18" height="16" align="absmiddle">) icon in the <a href="../debug/viewing_debug.htm">Debug</a> view
+ <p>A Disassembly view appears in the current perspective.</p>
+ </li>
+ </ul>
+ </div>
+<h5>Related reference</h5>
+<ul><li><a href="../../concepts/breakpoints.htm">Breakpoints</a></li>
+ <li><a href="../debug/cmds_reposition_pc.htm">Repositioning the Program Counter</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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_expressions.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,90 @@
+<!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>Expressions Window</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body >
+<h2>Expressions View </h2>
+<p> Use the <b>Expressions</b> view to monitor and manipulate:</p>
+<ul>
+ <li>global and local variables</li>
+ <li>structure members</li>
+ <li>array elements</li>
+</ul>
+<p>The Expressions view displays these panes: </p>
+<ul>
+ <li>Expression pane (left) — Lists expressions and expression hierarchies. Click the hierarchical controls to expand or collapse the expression view.</li>
+ <li>Value pane (right) — Shows the current value of each corresponding expression. Double-click a value to change it.</li>
+</ul>
+<p>Figure 1 shows the <b>Expressions</b> view.</p>
+<p align="center"><img src="../../reference/images/view_expressions.png" width="439" height="144" /></p>
+<p class="figure">Figure 1 - Expressions view </p>
+<h5>Table 1. Expressions view —items </h5>
+<table width="88%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="34%" scope="col">Item</th>
+ <th width="14%" scope="col">Icons</th>
+ <th width="52%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Show Type Names </b></td>
+ <td><div align="center"><img src="../../images/icons/var_toggle_type_names_icon.png" width="19" height="19" /></div></td>
+ <td>Toggles the display of type names in the Expressions view. </td>
+ </tr>
+ <tr>
+ <td><b>Show Logical Structure </b></td>
+ <td><div align="center"><img src="../../images/icons/var_show_logical_struct_icon.png" width="19" height="19" /></div></td>
+ <td>Not available in C/C++ yet. </td>
+ </tr>
+ <tr>
+ <td><b>Collapse All </b></td>
+ <td><div align="center"><img src="../../images/icons/var_collapse_all_icon.png" width="17" height="18" /></div></td>
+ <td>Collapses all expanded expressions into the top level. </td>
+ </tr>
+ <tr>
+ <td><b>New Watch Expression</b></td>
+ <td> </td>
+ <td>Click to open the <b>Add Watch Expression</b> dialog.</td>
+ </tr>
+ <tr>
+ <td><b>Remove Selected Expression </b></td>
+ <td><div align="center"><img src="../../images/icons/var_remove_selected_globals_icon.png" width="18" height="16" /></div></td>
+ <td>Click to remove all currently selected expressions from the expressions list. </td>
+ </tr>
+ <tr>
+ <td><b>Remove All Expressions </b></td>
+ <td><div align="center"><img src="../../images/icons/var_remove_all_globals_icon.png" width="19" height="19" /></div></td>
+ <td>Click to remove all expressions from the expressions list. </td>
+ </tr>
+ <tr>
+ <td><b>Refresh</b></td>
+ <td><center>
+ </center>
+ </td>
+ <td>Click to refresh view display.</td>
+ </tr>
+</table>
+<h4>Opening the Expressions View </h4>
+ <p>Use the Expressions view to inspect frequently used variables as their values change during a debugging session.</p>
+ <div class="step">
+ <h4>Opening an Expressions view </h4>
+ <ul>
+ <li>Select Window > Show View > Expressions</li>
+ <li>OR</li>
+ <li>Right-click a variable in the <a href="view_variables.htm">Variables</a> or editor view and choose the Add Watchpoint (C/C++) menu item</li>
+ <p>An Expressions view appears in the current perspective.</p>
+ </ul>
+</div>
+<h5>Related tasks</h5>
+<ul>
+ <li><a href="../variables/adding_expressions.htm">Adding & Removing Expressions</a></li>
+ <li><a href="../variables/editing_expressions.htm">Editing Expressions</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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_memory.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,88 @@
+<!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>Memory view</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body >
+<h2>Memory view </h2>
+<p> Use the <b>Memory</b> view to inspect and change process memory. You can address memory using expressions such as:</p>
+<ul>
+ <li class="code">0x0847d3c </li>
+ <li class="code">(&y)+1024 </li>
+ <li class="code">*ptr</li>
+ <li class="code">FNname + 1 </li>
+</ul>
+<p>You can configure your output to display traditional, hexadecimal, ascii and/or signed/unsigned decimal. You can also set the size of the rendering columns. </p>
+<p class="note"><b>CAUTION</b> Arbitrarily changing memory contents could degrade the stability of the IDE, another program, or the operating system itself. Understand the consequences of manipulating memory.</p>
+<p>Figure 1 shows the Memory view.</p>
+<p align="center"><img src="../../reference/images/view_memory.png" alt="Memory view" width="619" height="208"></p>
+<p class="figure">Figure 2 - Memory view showing a memory rendering in traditional format</p>
+<h5>Table 1 Memory view—items </h5>
+<table width="100%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="37%" scope="col">Item</th>
+ <th width="11%" scope="col">Icon</th>
+ <th width="52%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><a href="../../tasks/memory/view_memory_show.htm">New Memory View</a> </td>
+ <td><div align="center"><img src="../../reference/images/view_mem_new_memory_btn.png" width="16" height="17" /></div></td>
+ <td>Click to add a new Memory monitor view. </td>
+ </tr>
+ <tr>
+ <td><b>Pin Memory Monitor </b></td>
+ <td><div align="center"><img src="../../reference/images/view_mem_pin_memory_btn.png" width="19" height="18" /></div></td>
+ <td>Pin memory view.</td>
+ </tr>
+ <tr>
+ <td><b>Toggle Memory Monitors Pane </b></td>
+ <td><div align="center"><img src="../../reference/images/view_mem_toggle_pane_btn.png" width="19" height="17" /></div></td>
+ <td>Toggles the current Memory monitors view between showing only a Memory Monitor pane and a Memory Monitor and Memory Rendering pane. </td>
+ </tr>
+ <tr>
+ <td><b>Toggle Split Pane </b></td>
+ <td><div align="center"><img src="../../reference/images/view_mem_split_pane_btn.png" width="17" height="17" /></div></td>
+ <td>Alternately shows and hides the Memory Rendering pane. </td>
+ </tr>
+ <tr>
+ <td><b>Link Memory Monitor Panes </b></td>
+ <td><div align="center"><img src="../../reference/images/view_mem_link_btn.png" width="20" height="19" /></div></td>
+ <td><span>Enable to synchronize the current selection between the rendering of the same memory monitor </span>. </td>
+ </tr>
+ <tr>
+ <td><b>Switch Memory Monitor </b></td>
+ <td><div align="center"><img src="../../reference/images/view_mem_switch_monitor_btn.png" width="33" height="20" /></div></td>
+ <td>If different memory monitor views have been added, select from list of memory monitor views.</td>
+ </tr>
+ <tr>
+ <td><a href="../../tasks/memory/memory_monitor_adding.htm">Add Memory Monitor</a> / <a href="../../tasks/memory/memory_rendering_adding.htm">Add Rendering</a> </td>
+ <td><div align="center"><img src="../../images/icons/mem_add_monitor_icon.png" width="18" height="18" /></div></td>
+ <td>Add a new memory address or variable to the Memory Monitors pane, or add a new rendering to the Memory Rendering pane. </td>
+ </tr>
+ <tr>
+ <td><a href="../../tasks/memory/memory_monitor_removing.htm">Remove Memory Monitor / Remove Rendering </a></td>
+ <td><div align="center"><img src="../../images/icons/mem_remove_monitor_icon.png" width="19" height="19" /></div></td>
+ <td>Remove the selected memory address or variable from the Memory Monitors pane, or remove the selected rendering from the Memory Rendering pane. </td>
+ </tr>
+ <tr>
+ <td><b>Remove All </b></td>
+ <td><div align="center"><img src="../../images/icons/mem_remove_all_icon.png" width="21" height="20" /></div></td>
+ <td>Remove all memory monitors or renderings from the associated pane. </td>
+ </tr>
+</table>
+<p align="left">Each memory monitor rendering pane can be configured independently. Right-click in the Renderings pane to see the rendering options available. The options presented in the context menu may differ if you have not chosen the Traditional rendering view (Figure 2). </p>
+<p align="center"><img src="../../reference/images/menu_memory_rendering_options.png" width="444" height="380"></p>
+<p class="figure">Figure 2 - Rendering pane options </p>
+<h5>Related tasks</h5>
+<ul>
+ <li><a href="../../tasks/memory/memory_monitor_adding.htm"> Adding a Memory Monitor</a></li>
+ <li><a href="../../tasks/memory/memory_rendering_adding.htm">Adding a Memory Rendering </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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_module.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,24 @@
+<!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>Modules View</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body >
+<h2>Modules View</h2>
+<p>The <b>Modules</b> view displays a list of modules loaded while debugging your program. The listed modules can be selected to show related information. You can open the Modules view in the <a href="../../projects/views/perspective_carbide.htm">Carbide C/C++</a> perspective by selecting <b>Window > Show view > Other...</b>, then expand the Debug folder and select Modules. In the <a href="perspective_debug.htm">Debug</a> perspective select <b>Window > Show view > Modules</b>.</p>
+<p>The Modules view is only loaded during a debug session and closes when the debug session ends. Select the running man icon to list the Type, Symbols, and Symbols file for the executable. Select the stack of books icon to list the Type, Symbols, Symbols file, and Base address for the shared library. </p>
+<p>Figure 1 shows the Modules view.</p>
+<p align="center"><img src="../../images/views/view_module.png" width="595" height="181" /></p>
+<p class="figure">Figure 1 - Modules view</p>
+<h5>Related reference </h5>
+<ul>
+ <li> <a href="../debug/viewing_debug.htm">Debug 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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_registers.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,176 @@
+<!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" />
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<title>Registers view</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body >
+<h2>Registers view</h2>
+<p>The <img src="../../images/command_link.png" border="0" alt="" /> <a href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.debug.ui.RegisterView)")' class="command-link"><b>Registers</b></a> view reveals a hierarchical view of all registers of the host computer or target device based on the debugging mode chosen. The view contains two separate panes:</p>
+<ul>
+ <li>Registers pane – displays a tree list of register groups, the registers in each group and their values</li>
+ <li>Details pane – shows the selected register value</li>
+</ul>
+<p>You can use the <b>Register</b> view to perform these tasks:</p>
+<ul>
+ <li>expand the hierarchical items in the window and <a href="../../tasks/registers/mem_reg_viewing.htm">view</a> their contents</li>
+ <li>select and <a href="../../tasks/registers/mem_reg_changing.htm">modify</a> register values</li>
+ <li><a href="../../tasks/registers/mem_reg_data_views.htm">view</a> documentation for individual registers (depending on the register)</li>
+</ul>
+<p>Figure 1 shows a sample <b>Registers</b> view.</p>
+<p align="center"><img src="../../reference/images/view_registers.png" width="367" height="370"></p>
+<p class="figure">Figure 1 - Registers view (Register and Detail panes shown)</p>
+<div class="step">
+ <h4>To open a Registers view </h4>
+ <ul>
+ <li>Click the Window > Show View > Registers menu option</li>
+ <p>A <b>Registers</b> view appears.</p>
+ </ul>
+</div>
+<h2><strong>Executables view toolbar icons</strong></h2>
+<p>The table below lists the unique icons displayed in the <b>Registers</b> view toolbar. </p>
+<h5>Table 1. <span class="figure">Registers</span> toolbar options </h5>
+<table width="88%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="12%" scope="col">Icons</th>
+ <th width="36%" scope="col">Item</th>
+ <th width="52%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><div align="center"><img src="../../images/icons/var_toggle_type_names_icon.png" alt="Toggle Type Names icon" width="19" height="19" /></div></td>
+ <td><b>Show Type Names </b></td>
+ <td>Toggles the display of type names in the <span class="figure"><b>Registers</b></span> view. </td>
+ </tr>
+ <tr>
+ <td><div align="center"><img src="../../images/icons/var_show_logical_struct_icon.png" alt="Logical Structure icon" width="19" height="19" /></div></td>
+ <td><b>Show Logical Structure </b></td>
+ <td>Not available in C/C++ yet. </td>
+ </tr>
+ <tr>
+ <td><div align="center"><img src="../../images/icons/var_collapse_all_icon.png" alt="Collapse All icon" width="17" height="18" /></div></td>
+ <td><b>Collapse All </b></td>
+ <td>Collapses all expanded variables into the top level.</td>
+ </tr>
+ <tr>
+ <td><div align="center"><img src="../../reference/images/icon_menu_white.png" alt="View menu icon" width="12" height="12"></div></td>
+ <td><b>View Menu</b></td>
+ <td><p>Provides access to Layout options for the view. Options include:</p>
+ <ul>
+ <li>Vertical - shows panes in vertical mode (default)</li>
+ <li>Horizontal – show panes in horizontal mode</li>
+ <li>Automatic – selects mode</li>
+ <li>Registers View Only – hides details pane</li>
+ </ul></td>
+ </tr>
+</table>
+<h2>Registers view context menu options</h2>
+<p>The <b>Registers</b> view contains these contextual menu options:</p>
+<h5>Table 2. <span class="figure">Registers</span> context menu options – Registers pane</h5>
+<table width="88%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="33%" scope="col">Item</th>
+ <th width="67%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Select All</b></td>
+ <td>Selects all register values shown.</td>
+ </tr>
+ <tr>
+ <td><b>Copy Registers</b></td>
+ <td>Copies the register values to the clipboard.</td>
+ </tr>
+ <tr>
+ <td><b>Enable</b></td>
+ <td>Enables the display of register values for the selected register group.</td>
+ </tr>
+ <tr>
+ <td><b>Disable</b></td>
+ <td>Disables the display of register values for the selected register group.</td>
+ </tr>
+ <tr>
+ <td><b>Find...</b></td>
+ <td>Opens the <b>Find</b> dialog.</td>
+ </tr>
+ <tr>
+ <td><b>Add Register Group</b></td>
+ <td>Opens the <b>Register Group</b> dialog where you can define new register groups.</td>
+ </tr>
+ <tr>
+ <td><b>Restore Default Register Groups</b></td>
+ <td>Restores the default registers group.</td>
+ </tr>
+ <tr>
+ <td><b>Edit Register Group</b></td>
+ <td>Opens the <b>Register Group</b> dialog where you can edit the selected register group.</td>
+ </tr>
+ <tr>
+ <td><b>Remove Register Group</b></td>
+ <td>Removes the selected register group.</td>
+ </tr>
+</table>
+<h5>Table 3. <span class="figure">Registers</span> context menu options – Details pane</h5>
+<table width="88%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="33%" scope="col">Item</th>
+ <th width="67%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Assign Value</b></td>
+ <td>Assigns the edited value in the <b>Details</b> pane to the selected register in the Registers pane.</td>
+ </tr>
+ <tr>
+ <td><b>Content Assist</b></td>
+ <td>Shows the <b>Content Assist</b> hover pane.</td>
+ </tr>
+ <tr>
+ <td><b>Cut</b></td>
+ <td>Cut the selected value and place it on the clipboard.</td>
+ </tr>
+ <tr>
+ <td><b>Copy</b></td>
+ <td>Copy the selected value and place it on the clipboard.</td>
+ </tr>
+ <tr>
+ <td><b>Paste</b></td>
+ <td>Paste the contents of the clipboard into the selected value.</td>
+ </tr>
+ <tr>
+ <td><b>Select All</b></td>
+ <td>Select all values shown.</td>
+ </tr>
+ <tr>
+ <td><b>Find/Replace...</b></td>
+ <td>Opens the Find/Replace dialog.</td>
+ </tr>
+ <tr>
+ <td><b>Wrap Text</b></td>
+ <td>Toggles whether text is wrapped to the view or not.</td>
+ </tr>
+ <tr>
+ <td><b>Max Length</b></td>
+ <td>Opens the <b>Configure Details Pane</b> dialog to specify the maximum number of characters to display in the <b>Details</b> pane.</td>
+ </tr>
+ <tr>
+ <td><b>Symbian Build</b></td>
+ <td><p>A sub-menu of build options including:</p>
+ <ul>
+ <li>Freeze Exports</li>
+ <li>Build All Configurations</li>
+ </ul></td>
+ </tr>
+</table>
+<h5>Other references </h5>
+<ul>
+ <li><a href="../../concepts/registers.htm">Registers</a></li>
+ <li><a href="../../tasks/registers/mem_reg_open_wnd.htm">Opening Register View</a></li>
+ <li><a href="../../tasks/registers/mem_reg_viewing.htm">Viewing Register Values </a></li>
+ <li><a href="../../tasks/registers/mem_reg_changing.htm">Changing Register Values</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
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_signals.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,45 @@
+<!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>Signals view</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body >
+<h2>Signals view</h2>
+<p> The Signals view of the Debug perspective lets you view the signals defined on the selected debug target and how the debugger handles each one. Figure 1 shows the Signals view.</p>
+<p align="center"><img src="../../images/views/view_signals.png" width="500" height="205" /></p>
+<p class="figure">Figure 1 - Signals view</p>
+<h5>Table 1 Signals view—items </h5>
+<table width="76%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="22%" scope="col">Item</th>
+ <th width="78%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Name</b></td>
+ <td>Displays the name of the signal.</td>
+ </tr>
+ <tr>
+ <td><b>Pass</b></td>
+ <td>Where "yes" is displayed, the debugger lets your program see the signal. Your program can handle the signal, or else it may terminate if the signal is fatal and not handled.</td>
+ </tr>
+ <tr>
+ <td><b>Suspend</b></td>
+ <td>Where "yes" is displayed, the debugger suspends your program when this signal is handled.</td>
+ </tr>
+ <tr>
+ <td><b>Description</b></td>
+ <td>Displays a description of the signal.</td>
+ </tr>
+</table>
+<h5>Related reference </h5>
+<ul>
+ <li> <a href="../debug/viewing_debug.htm">Debug 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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_sym_os_data_chunks.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,44 @@
+<!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>Symbian OS Data: Chunks</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+</head>
+<body >
+<h2>Symbian Data view: Chunks</h2>
+<p>The <img src="../../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.edc.ui.SymbianSystemView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. Data to be viewed includes:</p>
+<ul>
+ <li><a href="view_sym_os_data_overview.htm">Overview</a></li>
+ <li><a href="view_sym_os_data_process.htm">Processes</a></li>
+ <li><a href="view_sym_os_data_threads.htm">Threads</a></li>
+ <li><a href="view_sym_os_data_chunks.htm">Chunks</a></li>
+ <li><a href="view_sym_os_data_libs.htm">Libraries</a></li>
+</ul>
+<p class="note"><b>NOTE</b> Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.</p>
+<hr>
+<h2><a name="chunks" id="chunks"></a>Chunks</h2>
+<p>Chunks are an area of contiguous linear memory. It is the unit of memory allocation where a region of RAM is mapped into contiguous logical addresses. Chunks are allocated during boot for such things as the Kernel's data and stack.</p>
+<p>The Chunks tab (Figure 4) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header.</p>
+<p class="note"> <b>NOTE</b> Chunks data is not available during CODA debugging.</p>
+<p align="center"><img src="../../reference/images/view_symbianOS_chunks.png" width="530" height="278" alt="" /></p>
+<p class="figure">Figure 4. Chunks Pane of Symbian View</p>
+<h3><a name="attach" id="attach"></a>Attaching to a Process</h3>
+<p>If <span class="note">you double click on a thread item in the Thread tab, or right-click and choose <b>Debug</b>, the owning process of the thread will be attached.</span> The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose <b>Properties</b>.</p>
+<p class="note"><b>NOTE </b>If an executable is not part of a project in the workspace use the Executables view to import an executable to make it visible to the debugger. Once included in the Executables list, the symbolics for that executable can be loaded and breakpoints resolved and hit. Open a source file in an editor view or use the <a href="view_breakpoints.htm">Breakpoints</a> view to verify that the executable breakpoints have been <a href="../../concepts/breakpoints.htm">resolved</a>. </p>
+<p class="note"><b>IMPORTANT</b> In stop mode debugging when debugging multiple processes at the same time, selecting a process in the <a href="../debug/viewing_debug.htm">Debug</a> pane and clicking <b>Terminate</b> disconnects the attached process on the board, leaving all other processes running. It does not terminate the debug session. However, if there is only one debug process when you click <b>Terminate</b> the CPU is suspended until the next debug session.</p>
+<p class="note"><b>WARNING</b> Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device. </p>
+<p><img src="../../reference/images/symOSData_attachprocess.png" width="1144" height="332" alt="" /></p>
+<h5>Other references</h5>
+<ul>
+ <li><a href="../debug/viewing_debug.htm">Debug view</a></li>
+ <li><a href="../../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
+ </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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_sym_os_data_libs.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,44 @@
+<!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>Symbian OS Data: Libraries</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+</head>
+<body >
+<h2>Symbian Data view: Libraries</h2>
+<p>The <img src="../../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.edc.ui.SymbianSystemView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. </p>
+<p>Data to be viewed includes:</p>
+<ul>
+ <li><a href="view_sym_os_data_overview.htm">Overview</a></li>
+ <li><a href="view_sym_os_data_process.htm">Processes</a></li>
+ <li><a href="view_sym_os_data_threads.htm">Threads</a></li>
+ <li><a href="view_sym_os_data_chunks.htm">Chunks</a></li>
+ <li><a href="view_sym_os_data_libs.htm">Libraries</a></li>
+</ul>
+<p class="note"><b>NOTE</b> Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.</p>
+<hr>
+<h2><a name="Library" id="Library"></a>Libraries Tab</h2>
+<p> The Libraries pane (Figure 5) in the Symbian view provides information on libraries in the Symbian residing on the target.</p>
+<p class="note"> <b>NOTE</b> Library data is not available during CODA debugging.</p>
+<p align="center"><img src="../../reference/images/view_symbianOS_Lib.png" width="531" height="278" alt="" /></p>
+<p class="figure">Figure 5. Libraries Pane of Symbian view</p>
+<h3><a name="attach" id="attach"></a>Attaching to a Process</h3>
+<p>If <span class="note">you double click on a thread item in the Thread tab, or right-click and choose <b>Debug</b>, the owning process of the thread will be attached.</span> The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose <b>Properties</b>.</p>
+<p class="note"><b>NOTE </b>If an executable is not part of a project in the workspace use the Executables view to import an executable to make it visible to the debugger. Once included in the Executables list, the symbolics for that executable can be loaded and breakpoints resolved and hit. Open a source file in an editor view or use the <a href="view_breakpoints.htm">Breakpoints</a> view to verify that the executable breakpoints have been <a href="../../concepts/breakpoints.htm">resolved</a>. </p>
+<p class="note"><b>IMPORTANT</b> In stop mode debugging when debugging multiple processes at the same time, selecting a process in the <a href="../debug/viewing_debug.htm">Debug</a> pane and clicking <b>Terminate</b> disconnects the attached process on the board, leaving all other processes running. It does not terminate the debug session. However, if there is only one debug process when you click <b>Terminate</b> the CPU is suspended until the next debug session.</p>
+<p class="note"><b>WARNING</b> Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device. </p>
+<p><img src="../../reference/images/symOSData_attachprocess.png" width="1144" height="332" alt="" /></p>
+<h5>Other references</h5>
+<ul>
+ <li><a href="../debug/viewing_debug.htm">Debug view</a></li>
+ <li><a href="../../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
+ </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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_sym_os_data_overview.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,114 @@
+<!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>Symbian OS Data: Overview</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+</head>
+<body >
+<h2>Symbian Data view: Overview</h2>
+<p>The <img src="../../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.edc.ui.SymbianSystemView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. To open the Symbian Data view select<b> Window > Show View > Symbian Data</b> when the <a href="perspective_debug.htm">Debug</a> perspective is visible or select <b>Window > Show View > Other...</b>, then expand the Carbide.c++ folder and select <b>Symbian Data</b> when the <a href="../../projects/views/perspective_carbide.htm">Carbide C/C++ perspective</a> is visible. Click <b>Ok</b> to display the Symbian Data window (Figure 1).</p>
+<p class="note"><b>NOTE</b> The Symbian Data view works with the debugger and will only display data during a live debug session. The Symbian Data view is not supported for emulator debugging, and will not show anything during emulator debug.</p>
+<p>The <b>Symbian Data</b> view reveals kernel data in the Symbian running on the device being debugged. The kernel data displayed is always that of the device with the currently selected thread or process in <a href="../debug/viewing_debug.htm">Debug</a> view. If you are debugging two devices at the same time, the content of the view will change when focus is switched from a thread on one device to a thread on another device. The kernel data includes more than just processes and threads. </p>
+<p>For the stop mode debugger and the crash debugger, all the data listed above is supported. For the Application and Symbian Device debuggers, the chunks and libraries views are not supported. The Symbian Data view is not supported for the emulator debugger and will show nothing during an emulator debug session. During a stop mode debug session or a CODA debug session, you are able to select a process or a thread in the Symbian Data view and attach the debugger to it for source level debugging if the binary is listed in the <a href="../../projects/views/view_executables.htm">Executables</a> view. Binaries listed in the Executable view can be source level debugged. Binaries not listed in the Executables view can only be assembly code debugged in the <a href="view_disassembly.htm">Disassembly</a> view.</p>
+<p class="note"><b>NOTE</b> Any executable must be included in the <b>Executables</b> view before it can be debugged. </p>
+<p>When the <a href="../../reference/pref_carb_debugger.htm">Time interval for auto-refreshing OS View</a> option is enabled (which is on by default except for crash debugger), the data in the Symbian Data view will be auto-refreshed. Note that "auto-refresh" has a different meaning in different debuggers. During a stop mode debug session, the view will refresh data whenever the debugged program on the device is stopped and shows data as stale (greyed out) when the program is running. During a CODA debug session, the View will refresh data at a time interval regardless of whether the debugged program is stopped or not. The time interval is specified by an option in the Carbide.c++ global preference panel, which is five seconds by default.</p>
+<p>When auto-refresh is turned off, the debugger will not automatically refresh data in the View and will show the data as stale (greyed out). However you can manually refresh the data by clicking on the "Refresh" button in the View. Usually you may want to turn off the auto-refresh if you think it is slowing down your debug operations such as stepping.</p>
+<h3>Symbian Data pages
+</h3>
+<p>The Symbian Data view consists of five tabs. Each tabbed pane is described below. In all panes, the <b>Name Filter</b> field is a standard Eclipse UI control that allows you to find an item by filtering out items by name using wildcards (*, ?) and camel case naming conventions. Camel case refers to using mixed case multiple names merged together in coding like <span class="code">SecInvInit</span> and <span class="code">DosServer</span>. In all panes, you can select an item and view its properties (attributes). In panes with columns you can click a column title to toggle between ascending and descending sorting. </p>
+<p>Data to be viewed includes:</p>
+<ul>
+ <li><a href="view_sym_os_data_overview.htm">Overview</a></li>
+ <li><a href="view_sym_os_data_process.htm">Processes</a></li>
+ <li><a href="view_sym_os_data_threads.htm">Threads</a></li>
+ <li><a href="view_sym_os_data_chunks.htm">Chunks</a></li>
+ <li><a href="view_sym_os_data_libs.htm">Libraries</a></li>
+</ul>
+<p class="note"><b>NOTE</b> Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.</p>
+<h4><a name="overview" id="overview"></a>Overview Tab</h4>
+<p>This tab (shown in Figure 1) provides a tree view of ownership of all processes, threads, and chunks in the OS.
+ In contrast, the other tabs provide a flat list of corresponding kernel objects such as process, thread, chunk, library, etc.</p>
+<p align="center"><img src="../../reference/images/view_symbianOSkernel.png" width="602" height="300" alt="" /></p>
+<p class="figure">Figure 1. Symbian Data view</p>
+<h5>Table 1 - Symbian Data view toolbar buttons </h5>
+<table cellpadding="2" cellspacing="0"
+border="0">
+ <tr valign="top">
+ <th width="209" class="Cell">Button</th>
+ <th width="49" class="Cell">Icon</th>
+ <th width="534" class="Cell">Function</th>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><p> <b>Refresh data</b></p></td>
+ <td class="Cell"><div align="center"><img src="../../reference/images/view_symbianOSbtn_refresh.png" width="19" height="19" alt="" /></div></td>
+ <td class="Cell"><p> Click this button to force a refresh of data in the view. Use the <a href="../../reference/pref_carb_debugger.htm">Carbide.c++ Debugger</a> preference panel <b>Time interval for auto-refreshing OS View</b> option to control the automatic refreshing of data. </p></td>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><p> <b>Enable/disable auto-refresh</b> </p></td>
+ <td class="Cell"><div align="center"><img src="../../reference/images/view_symbianOSbtn_autorefresh.png" width="19" height="21" alt="" /></div></td>
+ <td class="Cell"><p> Click this button to turn on/off auto refresh of data.</p></td>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><p> <b>Debug process or thread</b> </p></td>
+ <td class="Cell"><div align="center"><img src="../../reference/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 CODA (run mode) and TCF (stop mode).</p>
+ </td>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><p> <b>Properties</b> </p></td>
+ <td class="Cell"><div align="center"><img src="../../reference/images/view_symbianOSbtn_prop.png" width="21" height="18" alt="" /></div></td>
+ <td class="Cell"><p>Click this button to show properties of currently selected item in the <b>Properties</b> view. Or right-click an item and choose <b>Properties</b>.</p></td>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><p> <b>Timer</b></p></td>
+ <td class="Cell"><div align="center"><img src="../../reference/images/view_symbianOSbtn_timer.png" width="21" height="18" alt="" /></div></td>
+ <td class="Cell"><p> Click this button to define the time interval for auto-refreshing data. This applies to run mode debugging only. </p></td>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><b>Collapse All </b></td>
+ <td class="Cell"><div align="center"><img src="../../reference/images/view_symbianOSbtn_collapse.png" width="17" height="17" alt="" /></div></td>
+ <td class="Cell">Click the <b>Collaps All</b> command to collapse all of the currently elements in the view.</td>
+ </tr>
+</table>
+<h4><a name="processes" id="processes"></a>Processes</h4>
+<p>The Processes tab (Figure 2) provides a flat list of corresponding kernel objects.
+Click a column title to sort the list by the title attribute in alternating ascending and descending order. For example, you may choose to sort the process list by Name, ID, or by Priority. </p>
+<p align="center"><img src="../../reference/images/view_symbianOS_PTC.png" width="602" height="291" alt="" /></p>
+<p class="figure">Figure 2. Processes Pane of Symbian View</p>
+<p>The process(es) being debugged will be shown in bold font. You can debug (attach debugger to) any process in the Processes tab by selecting it and clicking the "Debug" button or just by double clicking on it. In that case a new process item will show up in the Debug View if the process is not being debugged. Otherwise, you will get a message saying it's already under debug.</p>
+<h4><a name="threads" id="threads"></a>Threads</h4>
+<p>The Threads tab (Figure 3) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header. The thread(s) being debugged will be shown in bold font.</p>
+<p class="note"><b>NOTE</b> You can debug (attach debugger to) any thread in the Thread tab by double clicking on it or selecting it and clicking the Debug button. In that case, a new thread item will show up in Debug view if the thread is not being debugged.</p>
+<p align="center"><img src="../../reference/images/view_symbianOS_threads.png" width="602" height="291" alt="" /></p>
+<p class="figure">Figure 3. Threads Pane of Symbian View</p>
+<h4><a name="chunks" id="chunks"></a>Chunks</h4>
+<p>Chunks are an area of contiguous linear memory. It is the unit of memory allocation where a region of RAM is mapped into contiguous logical addresses. Chunks are allocated during boot for such things as the Kernel's data and stack.</p>
+<p>The Chunks tab (Figure 4) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header.</p>
+<p class="note"> <b>NOTE</b> Chunks data is not available during CODA debugging.</p>
+<p align="center"><img src="../../reference/images/view_symbianOS_chunks.png" width="530" height="278" alt="" /></p>
+<p class="figure">Figure 4. Chunks Pane of Symbian View</p>
+<h4><a name="Library" id="Library"></a>Libraries Tab</h4>
+<p> The Libraries pane (Figure 5) in the Symbian view provides information on libraries in the Symbian residing on the target.</p>
+<p class="note"> <b>NOTE</b> Library data is not available during CODA debugging.</p>
+<p align="center"><img src="../../reference/images/view_symbianOS_Lib.png" width="531" height="278" alt="" /></p>
+<p class="figure">Figure 5. Libraries Pane of Symbian View</p>
+<h3><a name="attach" id="attach"></a>Attaching to a Process</h3>
+<p>If <span class="note">you double click on a thread item in the Thread tab, or right-click and choose <b>Debug</b>, the owning process of the thread will be attached.</span> The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose <b>Properties</b>.</p>
+<p class="note"><b>NOTE </b>If an executable is not part of a project in the workspace use the Executables view to import an executable to make it visible to the debugger. Once included in the Executables list, the symbolics for that executable can be loaded and breakpoints resolved and hit. Open a source file in an editor view or use the <a href="view_breakpoints.htm">Breakpoints</a> view to verify that the executable breakpoints have been <a href="../../concepts/breakpoints.htm">resolved</a>. </p>
+<p class="note"><b>IMPORTANT</b> In stop mode debugging when debugging multiple processes at the same time, selecting a process in the <a href="../debug/viewing_debug.htm">Debug</a> pane and clicking <b>Terminate</b> disconnects the attached process on the board, leaving all other processes running. It does not terminate the debug session. However, if there is only one debug process when you click <b>Terminate</b> the CPU is suspended until the next debug session.</p>
+<p class="note"><b>WARNING</b> Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device. </p>
+<p><img src="../../reference/images/symOSData_attachprocess.png" width="1144" height="332" alt="" /></p>
+<h5>Other references</h5>
+<ul>
+ <li><a href="../debug/viewing_debug.htm">Debug view</a></li>
+ <li><a href="../../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
+ </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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_sym_os_data_process.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,37 @@
+<!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>Symbian OS Data: Process</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+</head>
+<body >
+<h2>Symbian Data view: Process</h2>
+<p>The <img src="../../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.edc.ui.SymbianSystemView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. Data to be viewed includes:</p>
+<ul>
+ <li><a href="view_sym_os_data_overview.htm">Overview</a></li>
+ <li><a href="view_sym_os_data_process.htm">Processes</a></li>
+ <li><a href="view_sym_os_data_threads.htm">Threads</a></li>
+ <li><a href="view_sym_os_data_chunks.htm">Chunks</a></li>
+ <li><a href="view_sym_os_data_libs.htm">Libraries</a></li>
+ </ul>
+<hr>
+<h2><a name="processes" id="processes"></a>Processes</h2>
+<p>The Processes tab (Figure 2) provides a flat list of corresponding kernel objects.
+Click a column title to sort the list by the title attribute in alternating ascending and descending order. For example, you may choose to sort the process list by Name, ID, or by Priority. </p>
+<p align="center"><img src="../../reference/images/view_symbianOS_PTC.png" width="602" height="291" alt="" /></p>
+<p class="figure">Figure 2. Processes Pane of Symbian view</p>
+<p>The process(es) being debugged will be shown in bold font. You can debug (attach debugger to) any process in the Processes tab by selecting it and clicking the "Debug" button or just by double clicking on it. In that case a new process item will show up in the Debug View if the process is not being debugged. Otherwise, you will get a message saying it's already under debug.</p>
+<h4>Other references</h4>
+<ul>
+ <li><a href="../debug/viewing_debug.htm">Debug view</a></li>
+ <li><a href="../../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
+ </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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_sym_os_data_threads.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +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>Symbian OS Data: Threads</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+</head>
+<body >
+<h2>Symbian Data view: Threads</h2>
+<p>The <img src="../../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.edc.ui.SymbianSystemView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. Data to be viewed includes:</p>
+<ul>
+ <li><a href="view_sym_os_data_overview.htm">Overview</a></li>
+ <li><a href="view_sym_os_data_process.htm">Processes</a></li>
+ <li><a href="view_sym_os_data_threads.htm">Threads</a></li>
+ <li><a href="view_sym_os_data_chunks.htm">Chunks</a></li>
+ <li><a href="view_sym_os_data_libs.htm">Libraries</a></li>
+</ul>
+<hr>
+<h2><a name="threads" id="threads"></a>Threads</h2>
+<p>The Threads tab (Figure 3) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header. The thread(s) being debugged will be shown in bold font.</p>
+<p class="note"><b>NOTE</b> You can debug (attach debugger to) any thread in the Thread tab by double clicking on it or selecting it and clicking the Debug button. In that case, a new thread item will show up in Debug view if the thread is not being debugged.</p>
+<p align="center"><img src="../../reference/images/view_symbianOS_threads.png" width="602" height="291" alt="" /></p>
+<p class="figure">Figure 3. Threads Pane of Symbian view</p>
+<h4>Other references</h4>
+<ul>
+ <li><a href="../debug/viewing_debug.htm">Debug view</a></li>
+ <li><a href="../../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
+ </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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_symbian_kernel.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,114 @@
+<!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>Symbian OS Data</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+</head>
+<body >
+<h2>Symbian Data view</h2>
+<p>The <img src="../../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.debug.kernelaware.ui.SymbianOSView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. To open the Symbian Data view select<b> Window > Show View > Symbian Data</b> when the <a href="perspective_debug.htm">Debug</a> perspective is visible or select <b>Window > Show View > Other...</b>, then expand the Carbide.c++ folder and select <b>Symbian Data</b> when the <a href="../../projects/views/perspective_carbide.htm">Carbide C/C++ perspective</a> is visible. Click <b>Ok</b> to display the Symbian Data window (Figure 1).</p>
+<p class="note"><b>NOTE</b> The Symbian Data view works with the debugger and will only display data during a live debug session. The Symbian Data view is not supported for emulator debugging, and will not show anything during emulator debug.</p>
+<p>The <b>Symbian Data</b> view reveals kernel data in the Symbian running on the device being debugged. The kernel data displayed is always that of the device with the currently selected thread or process in <a href="../debug/viewing_debug.htm">Debug</a> view. If you are debugging two devices at the same time, the content of the view will change when focus is switched from a thread on one device to a thread on another device. The kernel data includes more than just processes and threads. </p>
+<p>For the stop mode debugger and the crash debugger, all the data listed above is supported. For the Application and Symbian Device debuggers, the chunks and libraries views are not supported. The Symbian Data view is not supported for the emulator debugger and will show nothing during an emulator debug session. During a stop mode debug session or a CODA debug session, you are able to select a process or a thread in the Symbian Data view and attach the debugger to it for source level debugging if the binary is listed in the <a href="../../projects/views/view_executables.htm">Executables</a> view. Binaries listed in the Executable view can be source level debugged. Binaries not listed in the Executables view can only be assembly code debugged in the <a href="view_disassembly.htm">Disassembly</a> view.</p>
+<p class="note"><b>NOTE</b> Any executable must be included in the <b>Executables</b> view before it can be debugged. </p>
+<p>When the <a href="../../reference/pref_carb_debugger.htm">Time interval for auto-refreshing OS View</a> option is enabled (which is on by default except for crash debugger), the data in the Symbian Data view will be auto-refreshed. Note that "auto-refresh" has a different meaning in different debuggers. During a stop mode debug session, the view will refresh data whenever the debugged program on the device is stopped and shows data as stale (greyed out) when the program is running. During a CODA debug session, the View will refresh data at a time interval regardless of whether the debugged program is stopped or not. The time interval is specified by an option in the Carbide.c++ global preference panel, which is five seconds by default.</p>
+<p>When auto-refresh is turned off, the debugger will not automatically refresh data in the View and will show the data as stale (greyed out). However you can manually refresh the data by clicking on the "Refresh" button in the View. Usually you may want to turn off the auto-refresh if you think it is slowing down your debug operations such as stepping.</p>
+<h3>Symbian Data pages
+</h3>
+<p>The Symbian Data view consists of five tabs. Each tabbed pane is described below. In all panes, the <b>Name Filter</b> field is a standard Eclipse UI control that allows you to find an item by filtering out items by name using wildcards (*, ?) and camel case naming conventions. Camel case refers to using mixed case multiple names merged together in coding like <span class="code">SecInvInit</span> and <span class="code">DosServer</span>. In all panes, you can select an item and view its properties (attributes). In panes with columns you can click a column title to toggle between ascending and descending sorting. </p>
+<p>Data to be viewed includes:</p>
+<ul>
+ <li><a href="#overview">Overview</a></li>
+ <li><a href="#processes">Processes</a></li>
+ <li><a href="#threads">Threads</a></li>
+ <li><a href="#chunks">Chunks</a></li>
+ <li><a href="#Library">Libraries</a></li>
+</ul>
+<p class="note"><b>NOTE</b> Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.</p>
+<h4><a name="overview" id="overview"></a>Overview Tab</h4>
+<p>This tab (shown in Figure 1) provides a tree view of ownership of all processes, threads, and chunks in the OS.
+ In contrast, the other tabs provide a flat list of corresponding kernel objects such as process, thread, chunk, library, etc.</p>
+<p align="center"><img src="../../reference/images/view_symbianOSkernel.png" width="602" height="300" alt="" /></p>
+<p class="figure">Figure 1. Symbian Data view</p>
+<h5>Table 1 - Symbian Data view toolbar buttons </h5>
+<table cellpadding="2" cellspacing="0"
+border="0">
+ <tr valign="top">
+ <th width="209" class="Cell">Button</th>
+ <th width="49" class="Cell">Icon</th>
+ <th width="534" class="Cell">Function</th>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><p> <b>Refresh data</b></p></td>
+ <td class="Cell"><div align="center"><img src="../../reference/images/view_symbianOSbtn_refresh.png" width="19" height="19" alt="" /></div></td>
+ <td class="Cell"><p> Click this button to force a refresh of data in the view. Use the <a href="../../reference/pref_carb_debugger.htm">Carbide.c++ Debugger</a> preference panel <b>Time interval for auto-refreshing OS View</b> option to control the automatic refreshing of data. </p></td>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><p> <b>Enable/disable auto-refresh</b> </p></td>
+ <td class="Cell"><div align="center"><img src="../../reference/images/view_symbianOSbtn_autorefresh.png" width="19" height="21" alt="" /></div></td>
+ <td class="Cell"><p> Click this button to turn on/off auto refresh of data.</p></td>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><p> <b>Debug process or thread</b> </p></td>
+ <td class="Cell"><div align="center"><img src="../../reference/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 CODA (run mode) and TCF (stop mode).</p>
+ </td>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><p> <b>Properties</b> </p></td>
+ <td class="Cell"><div align="center"><img src="../../reference/images/view_symbianOSbtn_prop.png" width="21" height="18" alt="" /></div></td>
+ <td class="Cell"><p>Click this button to show properties of currently selected item in the <b>Properties</b> view. Or right-click an item and choose <b>Properties</b>.</p></td>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><p> <b>Timer</b></p></td>
+ <td class="Cell"><div align="center"><img src="../../reference/images/view_symbianOSbtn_timer.png" width="21" height="18" alt="" /></div></td>
+ <td class="Cell"><p> Click this button to define the time interval for auto-refreshing data. This applies to run mode debugging only. </p></td>
+ </tr>
+ <tr valign="top">
+ <td class="Cell"><b>Collapse All </b></td>
+ <td class="Cell"><div align="center"><img src="../../reference/images/view_symbianOSbtn_collapse.png" width="17" height="17" alt="" /></div></td>
+ <td class="Cell">Click the <b>Collaps All</b> command to collapse all of the currently elements in the view.</td>
+ </tr>
+</table>
+<h4><a name="processes" id="processes"></a>Processes</h4>
+<p>The Processes tab (Figure 2) provides a flat list of corresponding kernel objects.
+Click a column title to sort the list by the title attribute in alternating ascending and descending order. For example, you may choose to sort the process list by Name, ID, or by Priority. </p>
+<p align="center"><img src="../../reference/images/view_symbianOS_PTC.png" width="602" height="291" alt="" /></p>
+<p class="figure">Figure 2. Processes Pane of Symbian View</p>
+<p>The process(es) being debugged will be shown in bold font. You can debug (attach debugger to) any process in the Processes tab by selecting it and clicking the "Debug" button or just by double clicking on it. In that case a new process item will show up in the Debug View if the process is not being debugged. Otherwise, you will get a message saying it's already under debug.</p>
+<h4><a name="threads" id="threads"></a>Threads</h4>
+<p>The Threads tab (Figure 3) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header. The thread(s) being debugged will be shown in bold font.</p>
+<p class="note"><b>NOTE</b> You can debug (attach debugger to) any thread in the Thread tab by double clicking on it or selecting it and clicking the Debug button. In that case, a new thread item will show up in Debug view if the thread is not being debugged.</p>
+<p align="center"><img src="../../reference/images/view_symbianOS_threads.png" width="602" height="291" alt="" /></p>
+<p class="figure">Figure 3. Threads Pane of Symbian View</p>
+<h4><a name="chunks" id="chunks"></a>Chunks</h4>
+<p>Chunks are an area of contiguous linear memory. It is the unit of memory allocation where a region of RAM is mapped into contiguous logical addresses. Chunks are allocated during boot for such things as the Kernel's data and stack.</p>
+<p>The Chunks tab (Figure 4) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header.</p>
+<p class="note"> <b>NOTE</b> Chunks data is not available during CODA debugging.</p>
+<p align="center"><img src="../../reference/images/view_symbianOS_chunks.png" width="530" height="278" alt="" /></p>
+<p class="figure">Figure 4. Chunks Pane of Symbian View</p>
+<h4><a name="Library" id="Library"></a>Libraries Tab</h4>
+<p> The Libraries pane (Figure 5) in the Symbian view provides information on libraries in the Symbian residing on the target.</p>
+<p class="note"> <b>NOTE</b> Library data is not available during CODA debugging.</p>
+<p align="center"><img src="../../reference/images/view_symbianOS_Lib.png" width="531" height="278" alt="" /></p>
+<p class="figure">Figure 5. Libraries Pane of Symbian View</p>
+<h3><a name="attach" id="attach"></a>Attaching to a Process</h3>
+<p>If <span class="note">you double click on a thread item in the Thread tab, or right-click and choose <b>Debug</b>, the owning process of the thread will be attached.</span> The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose <b>Properties</b>.</p>
+<p class="note"><b>NOTE </b>If an executable is not part of a project in the workspace use the Executables view to import an executable to make it visible to the debugger. Once included in the Executables list, the symbolics for that executable can be loaded and breakpoints resolved and hit. Open a source file in an editor view or use the <a href="view_breakpoints.htm">Breakpoints</a> view to verify that the executable breakpoints have been <a href="../../concepts/breakpoints.htm">resolved</a>. </p>
+<p class="note"><b>IMPORTANT</b> In stop mode debugging when debugging multiple processes at the same time, selecting a process in the <a href="../debug/viewing_debug.htm">Debug</a> pane and clicking <b>Terminate</b> disconnects the attached process on the board, leaving all other processes running. It does not terminate the debug session. However, if there is only one debug process when you click <b>Terminate</b> the CPU is suspended until the next debug session.</p>
+<p class="note"><b>WARNING</b> Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device. </p>
+<p><img src="../../reference/images/symOSData_attachprocess.png" width="1144" height="332" alt="" /></p>
+<h5>Other references</h5>
+<ul>
+ <li><a href="../debug/viewing_debug.htm">Debug view</a></li>
+ <li><a href="../../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
+ </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>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/views/view_variables.htm Wed Oct 06 14:30:50 2010 -0500
@@ -0,0 +1,86 @@
+<!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>Variables View</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body >
+<h2>Variables View </h2>
+<p>The <b>Variables</b> view allows manipulation of the variables or variable hierarchy used in source code. For example, you can change the variable format, change a variables value, add watchpoints, and add global variables. In addition to the standard C/C++, Symbian, and the Qt data types: <span class="code">QString</span>, <span class="code">QByteArray</span>, <span class="code">QSet</span>, <span class="code">QHash</span>, <span class="code">QMap</span>, <span class="code">QVector</span>, <span class="code">QList</span>, <span class="code">QLinkedList</span> and <span class="code">Qvariant</span>.</p>
+<p>Figure 1 shows the Variables view with <b>Show Type Names</b> option enabled.</p>
+<p align="center"><img src="../../images/views/view_variables.png" width="544" height="221" /></p>
+<p class="figure">Figure 1 - Variables view showing type names </p>
+<h5>Table 1. Variables view—items </h5>
+<table width="88%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="34%" scope="col">Item</th>
+ <th width="14%" scope="col">Icons</th>
+ <th width="52%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Show Type Names </b></td>
+ <td><div align="center"><img src="../../images/icons/var_toggle_type_names_icon.png" width="19" height="19" /></div></td>
+ <td>Toggles the display of type names in the Variables view. </td>
+ </tr>
+ <tr>
+ <td><b>Show Logical Structure </b></td>
+ <td><div align="center"><img src="../../images/icons/var_show_logical_struct_icon.png" width="19" height="19" /></div></td>
+ <td>Not available in C/C++ yet. </td>
+ </tr>
+ <tr>
+ <td><b>Collapse All </b></td>
+ <td><div align="center"><img src="../../images/icons/var_collapse_all_icon.png" width="17" height="18" /></div></td>
+ <td>Collapses all expanded variables into the top level. </td>
+ </tr>
+ <tr>
+ <td><b>Add Global Variables </b></td>
+ <td><div align="center"><img src="../../images/icons/var_add_global_vars_icon.png" width="19" height="19" /></div></td>
+ <td>Click to open a window where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list. </td>
+ </tr>
+ <tr>
+ <td><b>Remove Selected Global Variables </b></td>
+ <td><div align="center"><img src="../../images/icons/var_remove_selected_globals_icon.png" width="18" height="16" /></div></td>
+ <td>Click to remove all currently selected global variables from the variables list. </td>
+ </tr>
+ <tr>
+ <td><b>Remove All Global Variables </b></td>
+ <td><div align="center"><img src="../../images/icons/var_remove_all_globals_icon.png" width="19" height="19" /></div></td>
+ <td>Click to remove all global variables from the variables list. </td>
+ </tr>
+ <tr>
+ <td><b>Menu</b></td>
+ <td><div align="center"><img src="../../reference/images/icon_menu_white.png" width="12" height="12"></div></td>
+ <td><p>Enables you to modifiy the <b>Layout</b> to change the view orientation between: horizontal, vertical, or variables pane only.</p>
+ <p>In addition, use <b>Show All Variables</b> to toggle between showing only those variables that are in scope and live or show all local variables, even if redundant. With this option on you will see all of the variables including the multiple defined variables like “i” for your loops and ones that may no longer have accurate values.</p></td>
+ </tr>
+</table>
+<div class="step">
+ <h4>To open the Variables view </h4>
+ <ul>
+ <li>Click Window > Show View > Variables </li>
+ <p>The Variables view appears.</p>
+ </ul>
+</div>
+<h5>Related concepts</h5>
+<ul>
+ <li><a href="../../concepts/common_debug_actions.htm">Common Debug Actions </a></li>
+ <li><a href="../../concepts/working_with_memory.htm">Working with Memory</a></li>
+ <li><a href="../../concepts/working_with_variables.htm">Working with Variables</a> </li>
+</ul>
+<h5>Related tasks</h5>
+<ul>
+ <li><a href="perspective_debug.htm">Showing the Variables View</a> </li>
+ <li><a href="perspective_debug.htm">Showing Global Variables</a> </li>
+</ul>
+<h5>Related References </h5>
+<ul>
+ <li><a href="view_expressions.htm">Expressions View</a></li>
+ <li><a href="../../concepts/working_with_variables.htm">Variables 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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/setting_watchpoints.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/setting_watchpoints.htm Wed Oct 06 14:30:50 2010 -0500
@@ -11,7 +11,7 @@
<h2>Setting and Removing Watchpoints</h2>
<p>You create a watchpoint to monitor a value in a specified memory location. The debugger halts program execution on the line of source code that triggered the watchpoint. This is different than a breakpoint, which halts program execution prior to executing the line of source code on which the breakpoint is set.</p>
<h4>Setting watchpoints</h4>
-<p>Right-click in the <a href="../breakpoints/viewing_breakpoints.htm">Breakpoints</a> view and choose the <b>Add Watchpoint (C/C++)...</b> command to open the <b>Add Watchpoint</b> window. A watchpoint suspends program execution when the memory location that you specify is accessed with a write or read operation and it's based on the access setting. Use the <b>Add Watchpoint</b> window to specify the memory location, its memory size, unit size, and define whether the watchpoint triggers on a read, write, or on both operations. Watchpoints can also be added directly in the <a href="../../reference/view_variables.htm">Variables</a>, <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_outline_view.htm">Outline</a>, and the <a href="../../reference/view_memory.htm">Memory Rendering</a> views.</p>
+<p>Right-click in the <a href="../breakpoints/viewing_breakpoints.htm">Breakpoints</a> view and choose the <b>Add Watchpoint (C/C++)...</b> command to open the <b>Add Watchpoint</b> window. A watchpoint suspends program execution when the memory location that you specify is accessed with a write or read operation and it's based on the access setting. Use the <b>Add Watchpoint</b> window to specify the memory location, its memory size, unit size, and define whether the watchpoint triggers on a read, write, or on both operations. Watchpoints can also be added directly in the <a href="../views/view_variables.htm">Variables</a>, <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_outline_view.htm">Outline</a>, and the <a href="../views/view_memory.htm">Memory Rendering</a> views.</p>
<p align="center"><img src="../images/wnd_add_watchpoint.png" width="238" height="253"></p>
<p align="center" class="figure">Figure 1. Add Watchpoint window </p>
<h5>Table 1. Add Watchpoint options </h5>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/attach_process.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/attach_process.htm Wed Oct 06 14:30:50 2010 -0500
@@ -10,7 +10,7 @@
<body>
<h2>Attach to Process Launch Configuration</h2>
<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>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="../../debugger/views/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 > 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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Wed Oct 06 14:30:50 2010 -0500
@@ -17,7 +17,7 @@
<p>Launch configurations come in several varieties, each designed for a specific purpose. You must choose one at the very start of the New Launch Configuration Wizard, so knowing the differences between them is important. Currently, the types to choose from include: </p>
<ul>
<li><b><a href="stop_mode.htm">Symbian Device</a></b> — used to run or debug applications or ROM code on a target device using CODA (Carbide On-device Debug Agent). CODA is an application that runs on reference boards and prototype phones and allows you to debug executables. The debugger will download files to the phone prior to launching.</li>
- <li><b><a href="attach_process.htm">Symbian Device (Attach to Process)</a></b> — used to debug processes running on a target device for which a symbol file is available. This is available only for CODA and stop mode debugging. This launch configuration is not available for emulator debugging. Stop mode and CODA can both attach to a process from the <a href="../../reference/view_symbian_kernel.htm">Symbian Data</a> view.</li>
+ <li><b><a href="attach_process.htm">Symbian Device (Attach to Process)</a></b> — used to debug processes running on a target device for which a symbol file is available. This is available only for CODA and stop mode debugging. This launch configuration is not available for emulator debugging. Stop mode and CODA can both attach to a process from the <a href="../../debugger/views/view_symbian_kernel.htm">Symbian Data</a> view.</li>
<li><b><a href="run_mode.htm">Symbian Device (Install SIS)</a></b> — used to run or debug applications on a target device using CODA. 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.</li>
<li><b><a href="emulation.htm">Symbian Emulator</a> </b>— used to run or debug executables on an emulator. </li>
<li><b><a href="emulation.htm">Symbian Simulator</a> </b>— used to run or debug executables on a simulator. </li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/exporting_remote_conns.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/exporting_remote_conns.htm Wed Oct 06 14:30:50 2010 -0500
@@ -7,7 +7,7 @@
><meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Exporting Remote Connections</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="../../reference/trk/PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body >
<h2>Exporting Remote Connections</h2>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/importing_remote_conns.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/importing_remote_conns.htm Wed Oct 06 14:30:50 2010 -0500
@@ -7,7 +7,7 @@
><meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Importing Remote Connections</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="../../reference/trk/PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body >
<h2>Importing Remote Connections</h2>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/view_remote_connection.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/view_remote_connection.htm Wed Oct 06 14:30:50 2010 -0500
@@ -7,7 +7,7 @@
><meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Remote Connections view</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="../../reference/trk/PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
<style type="text/css">
<!--
.style1 {
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_new_conn_install_tab.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_new_conn_install_tab.htm Wed Oct 06 14:30:50 2010 -0500
@@ -7,7 +7,7 @@
><meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Install Remote Agents pane</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="../../reference/trk/PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body >
<h2>Install Remote Agents</h2>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_new_conn_settings_pane.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_new_conn_settings_pane.htm Wed Oct 06 14:30:50 2010 -0500
@@ -7,7 +7,7 @@
<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Install Remote Agents pane</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="../../reference/trk/PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body >
<h2>Install Remote Agents pane</h2>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_new_conn_wiz_add.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_new_conn_wiz_add.htm Wed Oct 06 14:30:50 2010 -0500
@@ -7,7 +7,7 @@
><meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Adding, Editing, and Deleting Connections</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="../../reference/trk/PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body >
<h2>Adding, Editing, and Deleting Connections</h2>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_new_conn_wiz_edit.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_new_conn_wiz_edit.htm Wed Oct 06 14:30:50 2010 -0500
@@ -7,7 +7,7 @@
><meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Editing connections</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="../../reference/trk/PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body >
<h2>Editing connections</h2>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_new_connection_wizard.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_new_connection_wizard.htm Wed Oct 06 14:30:50 2010 -0500
@@ -7,7 +7,7 @@
><meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Setup Connection</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="../../reference/trk/PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body >
<h2>Setup Connection</h2>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_on_device_check_tab.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_on_device_check_tab.htm Wed Oct 06 14:30:50 2010 -0500
@@ -7,7 +7,7 @@
><meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Test Connection</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="../../reference/trk/PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body >
<h2>Test Connection</h2>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_on_device_setup.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/remote_conn/wnd_on_device_setup.htm Wed Oct 06 14:30:50 2010 -0500
@@ -7,7 +7,7 @@
><meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>On-Device Connections</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="../../reference/trk/PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body >
<h2>On-Device Connections </h2>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_from_template_04.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_from_template_04.htm Wed Oct 06 14:30:50 2010 -0500
@@ -34,7 +34,7 @@
<li>Click the Run > Debug (<span class="code">F11</span>) menu item.</li>
<li>Click the Debug (<img src="../images/icon_debug.png" alt="Debug icon" width="17" height="17" align="absmiddle">) icon in the toolbar.</li>
</ul>
- <p>The emulator is launched and the <a href="../../reference/perspective_debug.htm">Debug</a> perspective appears to manage the debug session.</p>
+ <p>The emulator is launched and the <a href="../../debugger/views/perspective_debug.htm">Debug</a> perspective appears to manage the debug session.</p>
</li>
<li>Click the Options soft-menu and select any menu option to hit the breakpoint set in Step 2. <br />
<p><img src="../images/debugging_project_04.png" alt="Select menu option" width="360" height="397"></p>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/run_mode_debug_example_04.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/run_mode_debug_example_04.htm Wed Oct 06 14:30:50 2010 -0500
@@ -17,7 +17,7 @@
<li><strong>Debug project on target device</strong></li>
</ol>
<hr>
-<p>You debug on a remote device using the exact same methods used for the emulator. Once the project is built and downloaded to the target device, the CODA remote agent then takes control. Then, using the Carbide debugger you can use all the debugger features to exercise the program on the device while monitoring its vitals in the <a href="../../reference/perspective_debug.htm">Debug</a> perspective.</p>
+<p>You debug on a remote device using the exact same methods used for the emulator. Once the project is built and downloaded to the target device, the CODA remote agent then takes control. Then, using the Carbide debugger you can use all the debugger features to exercise the program on the device while monitoring its vitals in the <a href="../../debugger/views/perspective_debug.htm">Debug</a> perspective.</p>
<div class="step">
<h4>Debugging a program on a remote device</h4>
<ol>
@@ -33,8 +33,8 @@
<li>Use the various <a href="../../debugger/debug/debug.htm">stepping</a> commands to walk through the program.</li>
<li>Examine and change variables and expressions in the <a href="../../debugger/variables/variables.htm">Variables</a> view.</li>
<li>Examine the stack in the <a href="../../debugger/debug/viewing_debug.htm">Debug</a> view</li>
- <li>Review the assembler code in the <a href="../../reference/view_disassembly.htm">Disassembly</a> view</li>
- <li>Examine memory usage in the <a href="../../reference/view_memory.htm">Memory</a> view</li>
+ <li>Review the assembler code in the <a href="../../debugger/views/view_disassembly.htm">Disassembly</a> view</li>
+ <li>Examine memory usage in the <a href="../../debugger/views/view_memory.htm">Memory</a> view</li>
</ul>
</li>
</ol>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/views/perspective_carbide.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/views/perspective_carbide.htm Wed Oct 06 14:30:50 2010 -0500
@@ -11,9 +11,9 @@
<li><a href="view_sym_proj_nav.htm">Symbian Project Navigator</a> view - shows all files that belong to the
current build configuration </li>
<li><a href="../../hints_tips.htm">Editor</a> view - one or more source code editor windows </li>
- <li><a href="../../concepts/PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_outline_view.htm">Outline</a> view - displays an outline of a structured C/C++ file that is currently open in the editor view </li>
+ <li><a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_outline_view.htm">Outline</a> view - displays an outline of a structured C/C++ file that is currently open in the editor view </li>
<li><a href="view_carbide_portal.htm">Carbide.c++ Portal</a> editor - provides Carbide news, release information, additional extensions, and support options</li>
- <li><a href="../../concepts/PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_problems_view.htm">Problems</a> view - displays build errors </li>
+ <li><a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_problems_view.htm">Problems</a> view - displays build errors </li>
<li><a href="view_console.htm">Console</a> view - shows the output of a process and allows you to provide keyboard input to a process</li>
<li><a href="view_executables.htm">Executables</a> view - provides a dynamic list of executables and their related source files</li>
<li><a href="../remote_conn/view_remote_connection.htm">Remote Connections</a> view – use to monitor, create, edit, or remove common connection settings</li>
@@ -28,7 +28,7 @@
<a href="../../concepts/build_configurations.htm">Active Configurations</a>. </p>
<h5>Related references</h5>
<ul>
- <li><a href="../../reference/perspective_debug.htm">Debug Perspective</a></li>
+ <li><a href="../../debugger/views/perspective_debug.htm">Debug Perspective</a></li>
<li><a href="view_proj_explorer.htm">Project Explorer</a> view</li>
<li><a href="view_sym_proj_nav.htm">Symbian Project Navigator</a> view </li>
</ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/views/view_executables.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/views/view_executables.htm Wed Oct 06 14:30:50 2010 -0500
@@ -95,7 +95,7 @@
</table>
<h5>Other references</h5>
<ul>
- <li><a href="../../reference/perspective_debug.htm">Debug perspective </a></li>
+ <li><a href="../../debugger/views/perspective_debug.htm">Debug perspective </a></li>
<li><a href="../../concepts/autotargeting.htm">Auto-Targeting of Executables</a></li>
<li><a href="../../tasks/processes/attach_to_process.htm">Attaching to a Process</a></li>
</ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/views/view_proj_explorer.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/views/view_proj_explorer.htm Wed Oct 06 14:30:50 2010 -0500
@@ -28,7 +28,7 @@
<li><b>files</b> (<img src="../../reference/images/icon_project_file.png" width="15" height="16" align="absmiddle" />)—these files are located in the workspace within the project directories. Double-click a file icon to open it for editing.</li>
<li><b>folder links</b>—these are links pointing to folders that enable the project to support cvs related sources. </li>
</ul>
-<p>See <b>C/C++ Development User Guide > Reference > C/C++ Views and Editors > <a href="../../reference/PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_project_explorer_view.htm">Project Explorer view</a></b> for more info. </p>
+<p>See <b>C/C++ Development User Guide > Reference > C/C++ Views and Editors > <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_project_explorer_view.htm">Project Explorer view</a></b> for more info. </p>
<h5>Related references</h5>
<ul>
<li><a href="perspective_carbide.htm">Carbide C/C++ Perspective </a></li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/views/view_sym_proj_nav.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/views/view_sym_proj_nav.htm Wed Oct 06 14:30:50 2010 -0500
@@ -6,7 +6,7 @@
<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Symbian Project Navigator view</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="../../reference/PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body >
<h2>Symbian Project Navigator view</h2>
@@ -43,7 +43,7 @@
</tr>
</table>
<h5>Related references</h5>
-<ul><li><a href="../../reference/view_symbian_kernel.htm">Symbian View</a></li>
+<ul><li><a href="../../debugger/views/view_symbian_kernel.htm">Symbian View</a></li>
<li><a href="../../debugger/debug/viewing_debug.htm">Debug 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/reference/debugger_settings.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/debugger_settings.htm Wed Oct 06 14:30:50 2010 -0500
@@ -11,7 +11,7 @@
<h2>Debugger Settings</h2>
<p>The Carbide.c++ debugger settings include:</p>
<ul>
- <li><a href="perspective_debug.htm">Debug Perspective</a></li>
+ <li><a href="../debugger/views/perspective_debug.htm">Debug Perspective</a></li>
<li><a href="wnd_debug_configuration.htm">Debug Window </a> </li>
<li><a href="../debugger/debug/viewing_debug.htm">Debug View </a></li>
</ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/memory_rendering_options.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/memory_rendering_options.htm Wed Oct 06 14:30:50 2010 -0500
@@ -77,7 +77,7 @@
</ul>
<h5>Related References </h5>
<ul>
- <li><a href="view_memory.htm">Memory View</a></li>
+ <li><a href="../debugger/views/view_memory.htm">Memory 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/reference/menus/abld.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/abld.htm Wed Oct 06 14:30:50 2010 -0500
@@ -10,7 +10,7 @@
</head>
<body >
<h2>ABLD Actions </h2>
-<p>Use the <b>ABLD</b> menu option to invoke an specific <span class="code">abld</span> command on the selected project or file. ABLD is available under <b>Symbian Build > ABLD</b> or by right-clicking a project or file in the <a href="../../projects/views/view_proj_explorer.htm">Project Explorer</a>, <a href="../../projects/views/view_sym_proj_nav.htm">Symbian Project Navigator</a>, and <a href="../view_disassembly.htm">Disassembly</a> views and choosing <b>ABLD > <i>command</i></b>. When executed any arguments specified in the <a href="../build_properties/pane_build_config_args.htm">Carbide Build Configurations</a> pane for the command are passed to the selected tool. </p>
+<p>Use the <b>ABLD</b> menu option to invoke an specific <span class="code">abld</span> command on the selected project or file. ABLD is available under <b>Symbian Build > ABLD</b> or by right-clicking a project or file in the <a href="../../projects/views/view_proj_explorer.htm">Project Explorer</a>, <a href="../../projects/views/view_sym_proj_nav.htm">Symbian Project Navigator</a>, and <a href="../../debugger/views/view_disassembly.htm">Disassembly</a> views and choosing <b>ABLD > <i>command</i></b>. When executed any arguments specified in the <a href="../build_properties/pane_build_config_args.htm">Carbide Build Configurations</a> pane for the command are passed to the selected tool. </p>
<p align="center"><img src="../images/menu_symb_abld.png" width="890" height="204"></p>
<p class="figure">Figure 1 - Available ABLD actions</p>
<p>The available commands include:</p>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm Wed Oct 06 14:30:50 2010 -0500
@@ -48,7 +48,7 @@
</ul>
<h5 align="left">Common references </h5>
<ul>
- <li><a href="perspective_debug.htm">Debug Perspective</a></li>
+ <li><a href="../debugger/views/perspective_debug.htm">Debug Perspective</a></li>
<li><a href="wnd_debug_configuration.htm">Debug Window </a> </li>
<li><a href="../debugger/debug/viewing_debug.htm">Debug View</a></li>
</ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/perspective_debug.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,52 +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>Debug perspective</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body >
-<h2>Debug perspective</h2>
-<p>The Carbide.c++ <img src="../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.debug.ui.DebugPerspective)")'>
-Debug</a> perspective is where you debug programs running on an emulator or a target device. The default views include:</p>
-<ul>
- <li><a href="../debugger/debug/viewing_debug.htm">Debug view</a> - displays information about a suspended process during a debug session</li>
- <li><a href="view_variables.htm">Variables view</a> - allows manipulation of variables used in source code</li>
- <li><a href="view_breakpoints.htm">Breakpoints view</a> - allows manipulation of breakpoints and watchpoints</li>
- <li><a href="view_symbian_kernel.htm">Symbian Data view</a> - shows kernel data in the Symbian running on the device being debugged</li>
- <li><a href="../projects/views/view_executables.htm">Executables</a> view - provides a dynamic list of executables and their related source files</li>
- <li><a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_editor_view.htm">Editor</a> view - one or more source code editor windows </li>
- <li><a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_outline_view.htm">Outline</a> view - displays an outline of a structured C/C++ file that is currently open in the
- editor view </li>
- <li><a href="../projects/views/view_console.htm">Console</a> view - display<span><span>s the output of a process</span></span>, like the execution of your program, or other outputs </li>
- <li><a href="PLUGINS_ROOT/org.eclipse.platform.doc.user/reference/ref-31.htm">Tasks</a> view - <span>displays </span>tasks that you manually add</li>
-</ul>
-<p>And can include:</p>
-<ul>
- <li><a href="view_memory.htm">Memory</a> view - allows you to monitor and modify process memory</li>
- <li><a href="view_disassembly.htm">Disassembly</a> view - displays the assembly code of the source code currently being debugged </li>
- <li><a href="view_expressions.htm">Expressions</a> view - used to monitor and manipulate global and local variables, structure members, and array elements</li>
- <li><a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_modules_view.htm">Modules</a> view - uses the <a href="../projects/launch/wiz_new_launch_config.htm">Symbolics Loading</a> option to show modules loaded during a debug session </li>
- <li><a href="view_registers.htm">Registers</a> view - shows general, FPU, or host-specific registers of the host computer or target device</li>
-</ul>
-<p align="center"><img src="../images/views/perspective_debug.png" width="1028" height="789" alt="" /></p>
-<p class="figure">Figure 1. Debug perspective used by Carbide.c++</p>
-<p class="note"><b>NOTE</b> Click the <img src="../images/icons/double_arrow_icon.png" width="12" height="9" valign="absmiddle" alt="" /> icon to show additional options that may not be visible in the perspective view.</p>
-<p>For more information on perspectives see <b>Workbench User Guide > Concepts > <a href="PLUGINS_ROOT/org.eclipse.platform.doc.user/concepts/concepts-4.htm">Perspectives</a></b>, and for views see <b>C/C++ Development User Guide > Reference
-> <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_o_views.htm">C/C++ Views and Editors</a></b>.</p>
-<h5>Related references</h5>
-<ul>
- <li> <a href="../projects/views/perspective_carbide.htm">Carbide C/C++ Perspective</a></li>
- <li><a href="../debugger/debug/viewing_debug.htm">Debug view</a></li>
- <li><a href="view_variables.htm">Variables view</a></li>
- <li><a href="view_breakpoints.htm">Breakpoints view</a></li>
- <li><a href="view_memory.htm">Memory view</a></li>
- <li><a href="view_symbian_kernel.htm">Symbian Data 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
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/pref_carb_debugger.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/pref_carb_debugger.htm Wed Oct 06 14:30:50 2010 -0500
@@ -40,7 +40,7 @@
</tr>
<tr>
<td><b>Time interval for auto-refreshing OS View</b></td>
- <td>Determines how often to refresh data in the <a href="view_symbian_kernel.htm">Symbian Data</a> view which is available to the developer when using CODA or stop-mode debugging. </td>
+ <td>Determines how often to refresh data in the <a href="../debugger/views/view_symbian_kernel.htm">Symbian Data</a> view which is available to the developer when using CODA or stop-mode debugging. </td>
</tr>
</table>
<div class="step">
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm Wed Oct 06 14:30:50 2010 -0500
@@ -27,21 +27,21 @@
</li>
<li>Views
<ul>
- <li><a href="view_breakpoints.htm">Breakpoints</a></li>
+ <li><a href="../debugger/views/view_breakpoints.htm">Breakpoints</a></li>
<li><a href="../projects/views/view_carbide_portal.htm">Carbide.c++ Portal</a></li>
<li><a href="../projects/views/view_console.htm">Console</a></li>
<li><a href="../debugger/debug/viewing_debug.htm">Debug</a></li>
- <li><a href="view_disassembly.htm">Disassembly</a></li>
+ <li><a href="../debugger/views/view_disassembly.htm">Disassembly</a></li>
<li><a href="../projects/views/view_executables.htm">Executables</a></li>
- <li><a href="view_expressions.htm">Expressions</a></li>
- <li><a href="view_memory.htm">Memory</a></li>
- <li><a href="view_module.htm">Modules</a></li>
+ <li><a href="../debugger/views/view_expressions.htm">Expressions</a></li>
+ <li><a href="../debugger/views/view_memory.htm">Memory</a></li>
+ <li><a href="../debugger/views/view_module.htm">Modules</a></li>
<li><a href="../projects/views/view_proj_explorer.htm">Project Explorer</a></li>
- <li><a href="view_registers.htm">Registers</a></li>
+ <li><a href="../debugger/views/view_registers.htm">Registers</a></li>
<li><a href="../projects/remote_conn/view_remote_connection.htm">Remote Connections</a></li>
- <li><a href="view_signals.htm">Signals</a></li>
- <li><a href="view_symbian_kernel.htm">Symbian Data</a></li>
- <li><a href="view_variables.htm">Variables</a></li>
+ <li><a href="../debugger/views/view_signals.htm">Signals</a></li>
+ <li><a href="../debugger/views/view_symbian_kernel.htm">Symbian Data</a></li>
+ <li><a href="../debugger/views/view_variables.htm">Variables</a></li>
</ul>
</li>
</ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_breakpoints.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,80 +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>Breakpoints View</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body >
-<h2>Breakpoints View </h2>
-<p>Use the <b>Breakpoints</b> view to <a href="../tasks/breakpoints/pgm_bp_setting.htm">set</a>, <a href="../tasks/breakpoints/pgm_bp_view_props.htm">examine</a>, <a href="../tasks/breakpoints/pgm_bp_enable.htm">enable</a>, <a href="../tasks/breakpoints/pgm_bp_disable.htm">disable</a>, and <a href="../tasks/breakpoints/pgm_bp_clearing.htm">remove</a> breakpoints and <a href="../tasks/watchpoints/pgm_watchpoints.htm">watchpoints</a> in one or more <a href="../concepts/build_configurations.htm">build configurations</a>. Table 1 explains items in the view.</p>
-<p align="center"><img src="images/view_breakpoints.png" width="544" height="264" /></p>
-<p class="figure">Figure 1 - Breakpoints view</p>
-<h5>Table 1. Breakpoints view—items </h5>
-<table width="100%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="27%" scope="col">Item</th>
- <th width="11%" scope="col">Icon</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Remove Selected Breakpoint </b></td>
- <td><div align="center"><img src="../images/icons/breakpoints_remove_one_icon.png" width="19" height="19" /></div></td>
- <td>Removes the selected breakpoint from the breakpoints list. </td>
- </tr>
- <tr>
- <td><b>Remove All Breakpoints </b></td>
- <td><div align="center"><img src="../images/icons/breakpoints_remove_all_icon.png" width="21" height="19" /></div></td>
- <td>Removes all breakpoints from the breakpoints list. </td>
- </tr>
- <tr>
- <td><b>Show Breakpoints Supported by Selected Target </b></td>
- <td><div align="center"><img src="../images/icons/breakpoints_show_icon.png" width="20" height="19" /></div></td>
- <td>Limits the breakpoints shown to only those supported in the current target. </td>
- </tr>
- <tr>
- <td><b>Go to File for Breakpoint </b></td>
- <td><div align="center"><img src="../images/icons/breakpoints_goto_icon.png" width="20" height="19" /></div></td>
- <td>Displays the breakpoint in an editor view, opening the source file if required. </td>
- </tr>
- <tr>
- <td><b>Skip All Breakpoints </b></td>
- <td><div align="center"><img src="../images/icons/breakpoints_skip_all_icon.png" width="19" height="19" /></div></td>
- <td>Toggles the debugger to skip all breakpoints regardless of their current enabled or disabled state, or hit all breakpoints.</td>
- </tr>
- <tr>
- <td><b>Expand All </b></td>
- <td><div align="center"><img src="../images/icons/breakpoints_collapse_icon.png" width="19" height="18" /></div></td>
- <td>Expand all matches in the hierarchical view.</td>
- </tr>
- <tr>
- <td><b>Collapse All </b></td>
- <td><div align="center"><img src="../images/icons/breakpoints_expand_icon.png" width="19" height="18" /></div></td>
- <td>Collapse all matches in the hierarchical view.</td>
- </tr>
- <tr>
- <td><b>Link with Debug View</b></td>
- <td><div align="center"><img src="../images/icons/breakpoints_linkto_debug_icon.png" width="20" height="19" /></div></td>
- <td>When enabled, the breakpoint shown in the editor view is also highlighted in the Breakpoints view. When disabled, the breakpoint selected in the Breakpoints view does not change. </td>
- </tr>
- <tr>
- <td><b>Menu</b></td>
- <td><div align="center"><img src="images/icon_breakpoint_menu.png" width="16" height="9" /></div></td>
- <td>Click to display additional Breakpoint view options for paths and working sets. </td>
- </tr>
-</table>
- <h5>Other references</h5>
- <ul>
- <li><a href="perspective_debug.htm">Debug Perspective </a></li>
- <li><a href="../concepts/breakpoints.htm">Breakpoints</a></li>
- <li><a href="../tasks/breakpoints/pgm_bp_setting.htm">Setting Breakpoints</a></li>
- <li><a href="../tasks/breakpoints/pgm_bp_enable.htm">Enabling Breakpoints</a></li>
- <li><a href="../tasks/breakpoints/pgm_bp_disable.htm">Disabling Breakpoints</a></li>
- <li><a href="../tasks/breakpoints/pgm_bp_clearing.htm">Removing Breakpoints</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/reference/view_disassembly.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,124 +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>Disassembly Window</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-<style type="text/css">
-<!--
-.style1 {
- color: #FF0000;
- font-weight: bold;
-}
--->
-</style>
-</head>
-<body >
-<h2>Disassembly View</h2>
-<p> When debugging your application, the <b>Disassembly</b> view shows the loaded program as assembler instructions. When you use the Disassembly view, you can do the following tasks:</p>
-<ul>
- <li>Step through the disassembly instructions of your program using the <b>Instruction Stepping Mode</b> (<img src="images/icon_instr_stepping_mode.png" width="18" height="16" align="absmiddle">) icon in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> view (Figure 1). </li>
- <li>Reposition the PC using the various move commands (Figure 1) by first selecting the line to move to, then select the command from the context menu.</li>
- <li>Set breakpoints at the start of any assembler instruction by right-clicking the left hand column to view the context menu options (Figure 2) </li>
-</ul>
-<p>Figure 1 shows the <b>Dissassembly</b> view stopped at a breakpoint.</p>
-<p align="center"><img src="images/view_disassembly.png" width="555" height="272" alt="" /></p>
-<p class="figure">Figure 1 - Disassembly view</p>
-<p>Figure 2 shows the context menu that appears when you right-click in the Dissassembly pane. Right-clicking the left border opens the breakpoint context menu in Figure 3.</p>
-<p class="figure"><img src="images/view_disassembly_menu.png" width="232" height="133"></p>
-<p class="figure">Figure 2 - Disassembly pane context menu</p>
-<h5>Table 1. Disassembly pane — context menu</h5>
-<table width="88%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="26%" scope="col">Item</th>
- <th width="8%" scope="col">Icon</th>
- <th width="66%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Run to Line </b></td>
- <td><center>
- <img src="images/icon_dis_run_to_line.png" width="18" height="18">
- </center></td>
- <td>Select <b>Run to Line</b> to execute the program from the currently executed line (the green line) to the selected line (the blue line).</td>
- </tr>
- <tr>
- <td><b>Move to Line</b></td>
- <td><center>
- <img src="images/icon_dis_move_to_line.png" width="19" height="15">
- </center></td>
- <td><p>Select <b>Move to Line</b> to move the program counter to the selected line (the blue line) skipping all intermediate lines but not resume execution. This enables you to skip suspect code and continue stepping through your program.</p>
- <p class="note"><span class="style1">WARNING</span> Using this command can leave a program in an unstable state. Use at your own risk.</p></td>
- </tr>
- <tr>
- <td><b>Resume at Line </b></td>
- <td><center>
- <img src="images/icon_dis_resume_at_line.png" width="18" height="14">
- </center></td>
- <td><p>Select <b>Resume at Line</b> to begin program execution at the selected line (the blue line), skipping all lines between it and the currently executed line (the green line). </p>
- <p class="note"><span class="style1">WARNING</span> Using this command can leave a program in an unstable state. Use at your own risk.</p></td>
- </tr>
- <tr>
- <td><b>ABLD</b></td>
- <td> </td>
- <td>Use the <a href="menus/abld.htm">ABLD</a> menu option to invoke an specific <span class="code">abld</span> command on the selected project or file.</td>
- </tr>
- <tr>
- <td><b>Freeze Exports</b></td>
- <td><center>
- <img src="images/icon_freeze_exports.png" width="19" height="18">
- </center>
- </td>
- <td>Calls the appropriate <span class="code">abld</span> command to generate a .def file.</td>
- </tr>
- <tr>
- <td><b>Build All Configurations</b></td>
- <td><center>
- <img src="images/icon_build_all_configs.png" width="20" height="18">
- </center>
- </td>
- <td>Click <b>Build All Configurations</b> to build all enabled build configurations in the current project.</td>
- </tr>
- <tr>
- <td><b>Toggle Breakpoint </b></td>
- <td><center>
- </center></td>
- <td>Right-click in left-hand column of the Disassembly view and select this option to toggle the breakpoint state between <a href="../tasks/breakpoints/pgm_bp_setting.htm">setting</a> and <a href="../tasks/breakpoints/pgm_bp_clearing.htm">removing</a> the breakpoint. </td>
- </tr>
- <tr>
- <td><b>Disable/Enable Breakpoint </b></td>
- <td><center>
- </center></td>
- <td>Right-click in left-hand column of the Disassembly view and select the breakpoint option shown as determined by the current state of the breakpoint.</td>
- </tr>
- <tr>
- <td><b>Breakpoint Properties </b></td>
- <td><center>
- </center></td>
- <td>Select this option to open the <b>Breakpoint Properties</b> dialog. </td>
- </tr>
-</table>
-<p class="figure"><img src="images/view_disassm_breakpoint.png" width="506" height="172" alt="" /></p>
-<p class="figure">Figure 3 - Setting Breakpoints in the Disassembly view </p>
-<div class="step">
- <h4>Opening the Disassembly view </h4>
- <ul>
- <li>Select Window > Show View > Disassembly </li>
- </ul>
- <blockquote>
- <p>OR</p>
- </blockquote>
- <ul>
- <li>Click the Instruction Stepping Mode (<img src="images/icon_instr_stepping_mode.png" width="18" height="16" align="absmiddle">) icon in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> view
- <p>A Disassembly view appears in the current perspective.</p>
- </li>
- </ul>
- </div>
-<h5>Related reference</h5>
-<ul><li><a href="../concepts/breakpoints.htm">Breakpoints</a></li>
- <li><a href="../debugger/debug/cmds_reposition_pc.htm">Repositioning the Program Counter</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/reference/view_expressions.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,90 +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>Expressions Window</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body >
-<h2>Expressions View </h2>
-<p> Use the <b>Expressions</b> view to monitor and manipulate:</p>
-<ul>
- <li>global and local variables</li>
- <li>structure members</li>
- <li>array elements</li>
-</ul>
-<p>The Expressions view displays these panes: </p>
-<ul>
- <li>Expression pane (left) — Lists expressions and expression hierarchies. Click the hierarchical controls to expand or collapse the expression view.</li>
- <li>Value pane (right) — Shows the current value of each corresponding expression. Double-click a value to change it.</li>
-</ul>
-<p>Figure 1 shows the <b>Expressions</b> view.</p>
-<p align="center"><img src="images/view_expressions.png" width="439" height="144" /></p>
-<p class="figure">Figure 1 - Expressions view </p>
-<h5>Table 1. Expressions view —items </h5>
-<table width="88%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="34%" scope="col">Item</th>
- <th width="14%" scope="col">Icons</th>
- <th width="52%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Show Type Names </b></td>
- <td><div align="center"><img src="../images/icons/var_toggle_type_names_icon.png" width="19" height="19" /></div></td>
- <td>Toggles the display of type names in the Expressions view. </td>
- </tr>
- <tr>
- <td><b>Show Logical Structure </b></td>
- <td><div align="center"><img src="../images/icons/var_show_logical_struct_icon.png" width="19" height="19" /></div></td>
- <td>Not available in C/C++ yet. </td>
- </tr>
- <tr>
- <td><b>Collapse All </b></td>
- <td><div align="center"><img src="../images/icons/var_collapse_all_icon.png" width="17" height="18" /></div></td>
- <td>Collapses all expanded expressions into the top level. </td>
- </tr>
- <tr>
- <td><b>New Watch Expression</b></td>
- <td> </td>
- <td>Click to open the <b>Add Watch Expression</b> dialog.</td>
- </tr>
- <tr>
- <td><b>Remove Selected Expression </b></td>
- <td><div align="center"><img src="../images/icons/var_remove_selected_globals_icon.png" width="18" height="16" /></div></td>
- <td>Click to remove all currently selected expressions from the expressions list. </td>
- </tr>
- <tr>
- <td><b>Remove All Expressions </b></td>
- <td><div align="center"><img src="../images/icons/var_remove_all_globals_icon.png" width="19" height="19" /></div></td>
- <td>Click to remove all expressions from the expressions list. </td>
- </tr>
- <tr>
- <td><b>Refresh</b></td>
- <td><center>
- </center>
- </td>
- <td>Click to refresh view display.</td>
- </tr>
-</table>
-<h4>Opening the Expressions View </h4>
- <p>Use the Expressions view to inspect frequently used variables as their values change during a debugging session.</p>
- <div class="step">
- <h4>Opening an Expressions view </h4>
- <ul>
- <li>Select Window > Show View > Expressions</li>
- <li>OR</li>
- <li>Right-click a variable in the <a href="view_variables.htm">Variables</a> or editor view and choose the Add Watchpoint (C/C++) menu item</li>
- <p>An Expressions view appears in the current perspective.</p>
- </ul>
-</div>
-<h5>Related tasks</h5>
-<ul>
- <li><a href="../debugger/variables/adding_expressions.htm">Adding & Removing Expressions</a></li>
- <li><a href="../debugger/variables/editing_expressions.htm">Editing Expressions</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/reference/view_memory.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,88 +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>Memory view</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body >
-<h2>Memory view </h2>
-<p> Use the <b>Memory</b> view to inspect and change process memory. You can address memory using expressions such as:</p>
-<ul>
- <li class="code">0x0847d3c </li>
- <li class="code">(&y)+1024 </li>
- <li class="code">*ptr</li>
- <li class="code">FNname + 1 </li>
-</ul>
-<p>You can configure your output to display traditional, hexadecimal, ascii and/or signed/unsigned decimal. You can also set the size of the rendering columns. </p>
-<p class="note"><b>CAUTION</b> Arbitrarily changing memory contents could degrade the stability of the IDE, another program, or the operating system itself. Understand the consequences of manipulating memory.</p>
-<p>Figure 1 shows the Memory view.</p>
-<p align="center"><img src="images/view_memory.png" alt="Memory view" width="619" height="208"></p>
-<p class="figure">Figure 2 - Memory view showing a memory rendering in traditional format</p>
-<h5>Table 1 Memory view—items </h5>
-<table width="100%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="37%" scope="col">Item</th>
- <th width="11%" scope="col">Icon</th>
- <th width="52%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><a href="../tasks/memory/view_memory_show.htm">New Memory View</a> </td>
- <td><div align="center"><img src="images/view_mem_new_memory_btn.png" width="16" height="17" /></div></td>
- <td>Click to add a new Memory monitor view. </td>
- </tr>
- <tr>
- <td><b>Pin Memory Monitor </b></td>
- <td><div align="center"><img src="images/view_mem_pin_memory_btn.png" width="19" height="18" /></div></td>
- <td>Pin memory view.</td>
- </tr>
- <tr>
- <td><b>Toggle Memory Monitors Pane </b></td>
- <td><div align="center"><img src="images/view_mem_toggle_pane_btn.png" width="19" height="17" /></div></td>
- <td>Toggles the current Memory monitors view between showing only a Memory Monitor pane and a Memory Monitor and Memory Rendering pane. </td>
- </tr>
- <tr>
- <td><b>Toggle Split Pane </b></td>
- <td><div align="center"><img src="images/view_mem_split_pane_btn.png" width="17" height="17" /></div></td>
- <td>Alternately shows and hides the Memory Rendering pane. </td>
- </tr>
- <tr>
- <td><b>Link Memory Monitor Panes </b></td>
- <td><div align="center"><img src="images/view_mem_link_btn.png" width="20" height="19" /></div></td>
- <td><span>Enable to synchronize the current selection between the rendering of the same memory monitor </span>. </td>
- </tr>
- <tr>
- <td><b>Switch Memory Monitor </b></td>
- <td><div align="center"><img src="images/view_mem_switch_monitor_btn.png" width="33" height="20" /></div></td>
- <td>If different memory monitor views have been added, select from list of memory monitor views.</td>
- </tr>
- <tr>
- <td><a href="../tasks/memory/memory_monitor_adding.htm">Add Memory Monitor</a> / <a href="../tasks/memory/memory_rendering_adding.htm">Add Rendering</a> </td>
- <td><div align="center"><img src="../images/icons/mem_add_monitor_icon.png" width="18" height="18" /></div></td>
- <td>Add a new memory address or variable to the Memory Monitors pane, or add a new rendering to the Memory Rendering pane. </td>
- </tr>
- <tr>
- <td><a href="../tasks/memory/memory_monitor_removing.htm">Remove Memory Monitor / Remove Rendering </a></td>
- <td><div align="center"><img src="../images/icons/mem_remove_monitor_icon.png" width="19" height="19" /></div></td>
- <td>Remove the selected memory address or variable from the Memory Monitors pane, or remove the selected rendering from the Memory Rendering pane. </td>
- </tr>
- <tr>
- <td><b>Remove All </b></td>
- <td><div align="center"><img src="../images/icons/mem_remove_all_icon.png" width="21" height="20" /></div></td>
- <td>Remove all memory monitors or renderings from the associated pane. </td>
- </tr>
-</table>
-<p align="left">Each memory monitor rendering pane can be configured independently. Right-click in the Renderings pane to see the rendering options available. The options presented in the context menu may differ if you have not chosen the Traditional rendering view (Figure 2). </p>
-<p align="center"><img src="images/menu_memory_rendering_options.png" width="444" height="380"></p>
-<p class="figure">Figure 2 - Rendering pane options </p>
-<h5>Related tasks</h5>
-<ul>
- <li><a href="../tasks/memory/memory_monitor_adding.htm"> Adding a Memory Monitor</a></li>
- <li><a href="../tasks/memory/memory_rendering_adding.htm">Adding a Memory Rendering </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/reference/view_module.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,24 +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>Modules View</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body >
-<h2>Modules View</h2>
-<p>The <b>Modules</b> view displays a list of modules loaded while debugging your program. The listed modules can be selected to show related information. You can open the Modules view in the <a href="../projects/views/perspective_carbide.htm">Carbide C/C++</a> perspective by selecting <b>Window > Show view > Other...</b>, then expand the Debug folder and select Modules. In the <a href="perspective_debug.htm">Debug</a> perspective select <b>Window > Show view > Modules</b>.</p>
-<p>The Modules view is only loaded during a debug session and closes when the debug session ends. Select the running man icon to list the Type, Symbols, and Symbols file for the executable. Select the stack of books icon to list the Type, Symbols, Symbols file, and Base address for the shared library. </p>
-<p>Figure 1 shows the Modules view.</p>
-<p align="center"><img src="../images/views/view_module.png" width="595" height="181" /></p>
-<p class="figure">Figure 1 - Modules view</p>
-<h5>Related reference </h5>
-<ul>
- <li> <a href="../debugger/debug/viewing_debug.htm">Debug 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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_registers.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,176 +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" />
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Registers view</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body >
-<h2>Registers view</h2>
-<p>The <img src="../images/command_link.png" border="0" alt="" /> <a href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.debug.ui.RegisterView)")' class="command-link"><b>Registers</b></a> view reveals a hierarchical view of all registers of the host computer or target device based on the debugging mode chosen. The view contains two separate panes:</p>
-<ul>
- <li>Registers pane – displays a tree list of register groups, the registers in each group and their values</li>
- <li>Details pane – shows the selected register value</li>
-</ul>
-<p>You can use the <b>Register</b> view to perform these tasks:</p>
-<ul>
- <li>expand the hierarchical items in the window and <a href="../tasks/registers/mem_reg_viewing.htm">view</a> their contents</li>
- <li>select and <a href="../tasks/registers/mem_reg_changing.htm">modify</a> register values</li>
- <li><a href="../tasks/registers/mem_reg_data_views.htm">view</a> documentation for individual registers (depending on the register)</li>
-</ul>
-<p>Figure 1 shows a sample <b>Registers</b> view.</p>
-<p align="center"><img src="images/view_registers.png" width="367" height="370"></p>
-<p class="figure">Figure 1 - Registers view (Register and Detail panes shown)</p>
-<div class="step">
- <h4>To open a Registers view </h4>
- <ul>
- <li>Click the Window > Show View > Registers menu option</li>
- <p>A <b>Registers</b> view appears.</p>
- </ul>
-</div>
-<h2><strong>Executables view toolbar icons</strong></h2>
-<p>The table below lists the unique icons displayed in the <b>Registers</b> view toolbar. </p>
-<h5>Table 1. <span class="figure">Registers</span> toolbar options </h5>
-<table width="88%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="12%" scope="col">Icons</th>
- <th width="36%" scope="col">Item</th>
- <th width="52%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><div align="center"><img src="../images/icons/var_toggle_type_names_icon.png" alt="Toggle Type Names icon" width="19" height="19" /></div></td>
- <td><b>Show Type Names </b></td>
- <td>Toggles the display of type names in the <span class="figure"><b>Registers</b></span> view. </td>
- </tr>
- <tr>
- <td><div align="center"><img src="../images/icons/var_show_logical_struct_icon.png" alt="Logical Structure icon" width="19" height="19" /></div></td>
- <td><b>Show Logical Structure </b></td>
- <td>Not available in C/C++ yet. </td>
- </tr>
- <tr>
- <td><div align="center"><img src="../images/icons/var_collapse_all_icon.png" alt="Collapse All icon" width="17" height="18" /></div></td>
- <td><b>Collapse All </b></td>
- <td>Collapses all expanded variables into the top level.</td>
- </tr>
- <tr>
- <td><div align="center"><img src="images/icon_menu_white.png" alt="View menu icon" width="12" height="12"></div></td>
- <td><b>View Menu</b></td>
- <td><p>Provides access to Layout options for the view. Options include:</p>
- <ul>
- <li>Vertical - shows panes in vertical mode (default)</li>
- <li>Horizontal – show panes in horizontal mode</li>
- <li>Automatic – selects mode</li>
- <li>Registers View Only – hides details pane</li>
- </ul></td>
- </tr>
-</table>
-<h2>Registers view context menu options</h2>
-<p>The <b>Registers</b> view contains these contextual menu options:</p>
-<h5>Table 2. <span class="figure">Registers</span> context menu options – Registers pane</h5>
-<table width="88%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="33%" scope="col">Item</th>
- <th width="67%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Select All</b></td>
- <td>Selects all register values shown.</td>
- </tr>
- <tr>
- <td><b>Copy Registers</b></td>
- <td>Copies the register values to the clipboard.</td>
- </tr>
- <tr>
- <td><b>Enable</b></td>
- <td>Enables the display of register values for the selected register group.</td>
- </tr>
- <tr>
- <td><b>Disable</b></td>
- <td>Disables the display of register values for the selected register group.</td>
- </tr>
- <tr>
- <td><b>Find...</b></td>
- <td>Opens the <b>Find</b> dialog.</td>
- </tr>
- <tr>
- <td><b>Add Register Group</b></td>
- <td>Opens the <b>Register Group</b> dialog where you can define new register groups.</td>
- </tr>
- <tr>
- <td><b>Restore Default Register Groups</b></td>
- <td>Restores the default registers group.</td>
- </tr>
- <tr>
- <td><b>Edit Register Group</b></td>
- <td>Opens the <b>Register Group</b> dialog where you can edit the selected register group.</td>
- </tr>
- <tr>
- <td><b>Remove Register Group</b></td>
- <td>Removes the selected register group.</td>
- </tr>
-</table>
-<h5>Table 3. <span class="figure">Registers</span> context menu options – Details pane</h5>
-<table width="88%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="33%" scope="col">Item</th>
- <th width="67%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Assign Value</b></td>
- <td>Assigns the edited value in the <b>Details</b> pane to the selected register in the Registers pane.</td>
- </tr>
- <tr>
- <td><b>Content Assist</b></td>
- <td>Shows the <b>Content Assist</b> hover pane.</td>
- </tr>
- <tr>
- <td><b>Cut</b></td>
- <td>Cut the selected value and place it on the clipboard.</td>
- </tr>
- <tr>
- <td><b>Copy</b></td>
- <td>Copy the selected value and place it on the clipboard.</td>
- </tr>
- <tr>
- <td><b>Paste</b></td>
- <td>Paste the contents of the clipboard into the selected value.</td>
- </tr>
- <tr>
- <td><b>Select All</b></td>
- <td>Select all values shown.</td>
- </tr>
- <tr>
- <td><b>Find/Replace...</b></td>
- <td>Opens the Find/Replace dialog.</td>
- </tr>
- <tr>
- <td><b>Wrap Text</b></td>
- <td>Toggles whether text is wrapped to the view or not.</td>
- </tr>
- <tr>
- <td><b>Max Length</b></td>
- <td>Opens the <b>Configure Details Pane</b> dialog to specify the maximum number of characters to display in the <b>Details</b> pane.</td>
- </tr>
- <tr>
- <td><b>Symbian Build</b></td>
- <td><p>A sub-menu of build options including:</p>
- <ul>
- <li>Freeze Exports</li>
- <li>Build All Configurations</li>
- </ul></td>
- </tr>
-</table>
-<h5>Other references </h5>
-<ul>
- <li><a href="../concepts/registers.htm">Registers</a></li>
- <li><a href="../tasks/registers/mem_reg_open_wnd.htm">Opening Register View</a></li>
- <li><a href="../tasks/registers/mem_reg_viewing.htm">Viewing Register Values </a></li>
- <li><a href="../tasks/registers/mem_reg_changing.htm">Changing Register Values</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
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_signals.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,45 +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>Signals view</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body >
-<h2>Signals view</h2>
-<p> The Signals view of the Debug perspective lets you view the signals defined on the selected debug target and how the debugger handles each one. Figure 1 shows the Signals view.</p>
-<p align="center"><img src="../images/views/view_signals.png" width="500" height="205" /></p>
-<p class="figure">Figure 1 - Signals view</p>
-<h5>Table 1 Signals view—items </h5>
-<table width="76%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="22%" scope="col">Item</th>
- <th width="78%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Name</b></td>
- <td>Displays the name of the signal.</td>
- </tr>
- <tr>
- <td><b>Pass</b></td>
- <td>Where "yes" is displayed, the debugger lets your program see the signal. Your program can handle the signal, or else it may terminate if the signal is fatal and not handled.</td>
- </tr>
- <tr>
- <td><b>Suspend</b></td>
- <td>Where "yes" is displayed, the debugger suspends your program when this signal is handled.</td>
- </tr>
- <tr>
- <td><b>Description</b></td>
- <td>Displays a description of the signal.</td>
- </tr>
-</table>
-<h5>Related reference </h5>
-<ul>
- <li> <a href="../debugger/debug/viewing_debug.htm">Debug 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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_os_data_chunks.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,44 +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>Symbian OS Data: Chunks</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body >
-<h2>Symbian Data view: Chunks</h2>
-<p>The <img src="../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.edc.ui.SymbianSystemView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. Data to be viewed includes:</p>
-<ul>
- <li><a href="view_sym_os_data_overview.htm">Overview</a></li>
- <li><a href="view_sym_os_data_process.htm">Processes</a></li>
- <li><a href="view_sym_os_data_threads.htm">Threads</a></li>
- <li><a href="view_sym_os_data_chunks.htm">Chunks</a></li>
- <li><a href="view_sym_os_data_libs.htm">Libraries</a></li>
-</ul>
-<p class="note"><b>NOTE</b> Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.</p>
-<hr>
-<h2><a name="chunks" id="chunks"></a>Chunks</h2>
-<p>Chunks are an area of contiguous linear memory. It is the unit of memory allocation where a region of RAM is mapped into contiguous logical addresses. Chunks are allocated during boot for such things as the Kernel's data and stack.</p>
-<p>The Chunks tab (Figure 4) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header.</p>
-<p class="note"> <b>NOTE</b> Chunks data is not available during CODA debugging.</p>
-<p align="center"><img src="images/view_symbianOS_chunks.png" width="530" height="278" alt="" /></p>
-<p class="figure">Figure 4. Chunks Pane of Symbian View</p>
-<h3><a name="attach" id="attach"></a>Attaching to a Process</h3>
-<p>If <span class="note">you double click on a thread item in the Thread tab, or right-click and choose <b>Debug</b>, the owning process of the thread will be attached.</span> The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose <b>Properties</b>.</p>
-<p class="note"><b>NOTE </b>If an executable is not part of a project in the workspace use the Executables view to import an executable to make it visible to the debugger. Once included in the Executables list, the symbolics for that executable can be loaded and breakpoints resolved and hit. Open a source file in an editor view or use the <a href="view_breakpoints.htm">Breakpoints</a> view to verify that the executable breakpoints have been <a href="../concepts/breakpoints.htm">resolved</a>. </p>
-<p class="note"><b>IMPORTANT</b> In stop mode debugging when debugging multiple processes at the same time, selecting a process in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> pane and clicking <b>Terminate</b> disconnects the attached process on the board, leaving all other processes running. It does not terminate the debug session. However, if there is only one debug process when you click <b>Terminate</b> the CPU is suspended until the next debug session.</p>
-<p class="note"><b>WARNING</b> Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device. </p>
-<p><img src="images/symOSData_attachprocess.png" width="1144" height="332" alt="" /></p>
-<h5>Other references</h5>
-<ul>
- <li><a href="../debugger/debug/viewing_debug.htm">Debug view</a></li>
- <li><a href="../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
- </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/reference/view_sym_os_data_libs.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,44 +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>Symbian OS Data: Libraries</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body >
-<h2>Symbian Data view: Libraries</h2>
-<p>The <img src="../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.edc.ui.SymbianSystemView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. </p>
-<p>Data to be viewed includes:</p>
-<ul>
- <li><a href="view_sym_os_data_overview.htm">Overview</a></li>
- <li><a href="view_sym_os_data_process.htm">Processes</a></li>
- <li><a href="view_sym_os_data_threads.htm">Threads</a></li>
- <li><a href="view_sym_os_data_chunks.htm">Chunks</a></li>
- <li><a href="view_sym_os_data_libs.htm">Libraries</a></li>
-</ul>
-<p class="note"><b>NOTE</b> Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.</p>
-<hr>
-<h2><a name="Library" id="Library"></a>Libraries Tab</h2>
-<p> The Libraries pane (Figure 5) in the Symbian view provides information on libraries in the Symbian residing on the target.</p>
-<p class="note"> <b>NOTE</b> Library data is not available during CODA debugging.</p>
-<p align="center"><img src="images/view_symbianOS_Lib.png" width="531" height="278" alt="" /></p>
-<p class="figure">Figure 5. Libraries Pane of Symbian view</p>
-<h3><a name="attach" id="attach"></a>Attaching to a Process</h3>
-<p>If <span class="note">you double click on a thread item in the Thread tab, or right-click and choose <b>Debug</b>, the owning process of the thread will be attached.</span> The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose <b>Properties</b>.</p>
-<p class="note"><b>NOTE </b>If an executable is not part of a project in the workspace use the Executables view to import an executable to make it visible to the debugger. Once included in the Executables list, the symbolics for that executable can be loaded and breakpoints resolved and hit. Open a source file in an editor view or use the <a href="view_breakpoints.htm">Breakpoints</a> view to verify that the executable breakpoints have been <a href="../concepts/breakpoints.htm">resolved</a>. </p>
-<p class="note"><b>IMPORTANT</b> In stop mode debugging when debugging multiple processes at the same time, selecting a process in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> pane and clicking <b>Terminate</b> disconnects the attached process on the board, leaving all other processes running. It does not terminate the debug session. However, if there is only one debug process when you click <b>Terminate</b> the CPU is suspended until the next debug session.</p>
-<p class="note"><b>WARNING</b> Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device. </p>
-<p><img src="images/symOSData_attachprocess.png" width="1144" height="332" alt="" /></p>
-<h5>Other references</h5>
-<ul>
- <li><a href="../debugger/debug/viewing_debug.htm">Debug view</a></li>
- <li><a href="../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
- </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/reference/view_sym_os_data_overview.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,114 +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>Symbian OS Data: Overview</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body >
-<h2>Symbian Data view: Overview</h2>
-<p>The <img src="../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.edc.ui.SymbianSystemView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. To open the Symbian Data view select<b> Window > Show View > Symbian Data</b> when the <a href="perspective_debug.htm">Debug</a> perspective is visible or select <b>Window > Show View > Other...</b>, then expand the Carbide.c++ folder and select <b>Symbian Data</b> when the <a href="../projects/views/perspective_carbide.htm">Carbide C/C++ perspective</a> is visible. Click <b>Ok</b> to display the Symbian Data window (Figure 1).</p>
-<p class="note"><b>NOTE</b> The Symbian Data view works with the debugger and will only display data during a live debug session. The Symbian Data view is not supported for emulator debugging, and will not show anything during emulator debug.</p>
-<p>The <b>Symbian Data</b> view reveals kernel data in the Symbian running on the device being debugged. The kernel data displayed is always that of the device with the currently selected thread or process in <a href="../debugger/debug/viewing_debug.htm">Debug</a> view. If you are debugging two devices at the same time, the content of the view will change when focus is switched from a thread on one device to a thread on another device. The kernel data includes more than just processes and threads. </p>
-<p>For the stop mode debugger and the crash debugger, all the data listed above is supported. For the Application and Symbian Device debuggers, the chunks and libraries views are not supported. The Symbian Data view is not supported for the emulator debugger and will show nothing during an emulator debug session. During a stop mode debug session or a CODA debug session, you are able to select a process or a thread in the Symbian Data view and attach the debugger to it for source level debugging if the binary is listed in the <a href="../projects/views/view_executables.htm">Executables</a> view. Binaries listed in the Executable view can be source level debugged. Binaries not listed in the Executables view can only be assembly code debugged in the <a href="view_disassembly.htm">Disassembly</a> view.</p>
-<p class="note"><b>NOTE</b> Any executable must be included in the <b>Executables</b> view before it can be debugged. </p>
-<p>When the <a href="pref_carb_debugger.htm">Time interval for auto-refreshing OS View</a> option is enabled (which is on by default except for crash debugger), the data in the Symbian Data view will be auto-refreshed. Note that "auto-refresh" has a different meaning in different debuggers. During a stop mode debug session, the view will refresh data whenever the debugged program on the device is stopped and shows data as stale (greyed out) when the program is running. During a CODA debug session, the View will refresh data at a time interval regardless of whether the debugged program is stopped or not. The time interval is specified by an option in the Carbide.c++ global preference panel, which is five seconds by default.</p>
-<p>When auto-refresh is turned off, the debugger will not automatically refresh data in the View and will show the data as stale (greyed out). However you can manually refresh the data by clicking on the "Refresh" button in the View. Usually you may want to turn off the auto-refresh if you think it is slowing down your debug operations such as stepping.</p>
-<h3>Symbian Data pages
-</h3>
-<p>The Symbian Data view consists of five tabs. Each tabbed pane is described below. In all panes, the <b>Name Filter</b> field is a standard Eclipse UI control that allows you to find an item by filtering out items by name using wildcards (*, ?) and camel case naming conventions. Camel case refers to using mixed case multiple names merged together in coding like <span class="code">SecInvInit</span> and <span class="code">DosServer</span>. In all panes, you can select an item and view its properties (attributes). In panes with columns you can click a column title to toggle between ascending and descending sorting. </p>
-<p>Data to be viewed includes:</p>
-<ul>
- <li><a href="view_sym_os_data_overview.htm">Overview</a></li>
- <li><a href="view_sym_os_data_process.htm">Processes</a></li>
- <li><a href="view_sym_os_data_threads.htm">Threads</a></li>
- <li><a href="view_sym_os_data_chunks.htm">Chunks</a></li>
- <li><a href="view_sym_os_data_libs.htm">Libraries</a></li>
-</ul>
-<p class="note"><b>NOTE</b> Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.</p>
-<h4><a name="overview" id="overview"></a>Overview Tab</h4>
-<p>This tab (shown in Figure 1) provides a tree view of ownership of all processes, threads, and chunks in the OS.
- In contrast, the other tabs provide a flat list of corresponding kernel objects such as process, thread, chunk, library, etc.</p>
-<p align="center"><img src="images/view_symbianOSkernel.png" width="602" height="300" alt="" /></p>
-<p class="figure">Figure 1. Symbian Data view</p>
-<h5>Table 1 - Symbian Data view toolbar buttons </h5>
-<table cellpadding="2" cellspacing="0"
-border="0">
- <tr valign="top">
- <th width="209" class="Cell">Button</th>
- <th width="49" class="Cell">Icon</th>
- <th width="534" class="Cell">Function</th>
- </tr>
- <tr valign="top">
- <td class="Cell"><p> <b>Refresh data</b></p></td>
- <td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_refresh.png" width="19" height="19" alt="" /></div></td>
- <td class="Cell"><p> Click this button to force a refresh of data in the view. Use the <a href="pref_carb_debugger.htm">Carbide.c++ Debugger</a> preference panel <b>Time interval for auto-refreshing OS View</b> option to control the automatic refreshing of data. </p></td>
- </tr>
- <tr valign="top">
- <td class="Cell"><p> <b>Enable/disable auto-refresh</b> </p></td>
- <td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_autorefresh.png" width="19" height="21" alt="" /></div></td>
- <td class="Cell"><p> Click this button to turn on/off auto refresh of data.</p></td>
- </tr>
- <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 CODA (run mode) and TCF (stop mode).</p>
- </td>
- </tr>
- <tr valign="top">
- <td class="Cell"><p> <b>Properties</b> </p></td>
- <td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_prop.png" width="21" height="18" alt="" /></div></td>
- <td class="Cell"><p>Click this button to show properties of currently selected item in the <b>Properties</b> view. Or right-click an item and choose <b>Properties</b>.</p></td>
- </tr>
- <tr valign="top">
- <td class="Cell"><p> <b>Timer</b></p></td>
- <td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_timer.png" width="21" height="18" alt="" /></div></td>
- <td class="Cell"><p> Click this button to define the time interval for auto-refreshing data. This applies to run mode debugging only. </p></td>
- </tr>
- <tr valign="top">
- <td class="Cell"><b>Collapse All </b></td>
- <td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_collapse.png" width="17" height="17" alt="" /></div></td>
- <td class="Cell">Click the <b>Collaps All</b> command to collapse all of the currently elements in the view.</td>
- </tr>
-</table>
-<h4><a name="processes" id="processes"></a>Processes</h4>
-<p>The Processes tab (Figure 2) provides a flat list of corresponding kernel objects.
-Click a column title to sort the list by the title attribute in alternating ascending and descending order. For example, you may choose to sort the process list by Name, ID, or by Priority. </p>
-<p align="center"><img src="images/view_symbianOS_PTC.png" width="602" height="291" alt="" /></p>
-<p class="figure">Figure 2. Processes Pane of Symbian View</p>
-<p>The process(es) being debugged will be shown in bold font. You can debug (attach debugger to) any process in the Processes tab by selecting it and clicking the "Debug" button or just by double clicking on it. In that case a new process item will show up in the Debug View if the process is not being debugged. Otherwise, you will get a message saying it's already under debug.</p>
-<h4><a name="threads" id="threads"></a>Threads</h4>
-<p>The Threads tab (Figure 3) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header. The thread(s) being debugged will be shown in bold font.</p>
-<p class="note"><b>NOTE</b> You can debug (attach debugger to) any thread in the Thread tab by double clicking on it or selecting it and clicking the Debug button. In that case, a new thread item will show up in Debug view if the thread is not being debugged.</p>
-<p align="center"><img src="images/view_symbianOS_threads.png" width="602" height="291" alt="" /></p>
-<p class="figure">Figure 3. Threads Pane of Symbian View</p>
-<h4><a name="chunks" id="chunks"></a>Chunks</h4>
-<p>Chunks are an area of contiguous linear memory. It is the unit of memory allocation where a region of RAM is mapped into contiguous logical addresses. Chunks are allocated during boot for such things as the Kernel's data and stack.</p>
-<p>The Chunks tab (Figure 4) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header.</p>
-<p class="note"> <b>NOTE</b> Chunks data is not available during CODA debugging.</p>
-<p align="center"><img src="images/view_symbianOS_chunks.png" width="530" height="278" alt="" /></p>
-<p class="figure">Figure 4. Chunks Pane of Symbian View</p>
-<h4><a name="Library" id="Library"></a>Libraries Tab</h4>
-<p> The Libraries pane (Figure 5) in the Symbian view provides information on libraries in the Symbian residing on the target.</p>
-<p class="note"> <b>NOTE</b> Library data is not available during CODA debugging.</p>
-<p align="center"><img src="images/view_symbianOS_Lib.png" width="531" height="278" alt="" /></p>
-<p class="figure">Figure 5. Libraries Pane of Symbian View</p>
-<h3><a name="attach" id="attach"></a>Attaching to a Process</h3>
-<p>If <span class="note">you double click on a thread item in the Thread tab, or right-click and choose <b>Debug</b>, the owning process of the thread will be attached.</span> The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose <b>Properties</b>.</p>
-<p class="note"><b>NOTE </b>If an executable is not part of a project in the workspace use the Executables view to import an executable to make it visible to the debugger. Once included in the Executables list, the symbolics for that executable can be loaded and breakpoints resolved and hit. Open a source file in an editor view or use the <a href="view_breakpoints.htm">Breakpoints</a> view to verify that the executable breakpoints have been <a href="../concepts/breakpoints.htm">resolved</a>. </p>
-<p class="note"><b>IMPORTANT</b> In stop mode debugging when debugging multiple processes at the same time, selecting a process in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> pane and clicking <b>Terminate</b> disconnects the attached process on the board, leaving all other processes running. It does not terminate the debug session. However, if there is only one debug process when you click <b>Terminate</b> the CPU is suspended until the next debug session.</p>
-<p class="note"><b>WARNING</b> Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device. </p>
-<p><img src="images/symOSData_attachprocess.png" width="1144" height="332" alt="" /></p>
-<h5>Other references</h5>
-<ul>
- <li><a href="../debugger/debug/viewing_debug.htm">Debug view</a></li>
- <li><a href="../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
- </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/reference/view_sym_os_data_process.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,37 +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>Symbian OS Data: Process</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body >
-<h2>Symbian Data view: Process</h2>
-<p>The <img src="../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.edc.ui.SymbianSystemView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. Data to be viewed includes:</p>
-<ul>
- <li><a href="view_sym_os_data_overview.htm">Overview</a></li>
- <li><a href="view_sym_os_data_process.htm">Processes</a></li>
- <li><a href="view_sym_os_data_threads.htm">Threads</a></li>
- <li><a href="view_sym_os_data_chunks.htm">Chunks</a></li>
- <li><a href="view_sym_os_data_libs.htm">Libraries</a></li>
- </ul>
-<hr>
-<h2><a name="processes" id="processes"></a>Processes</h2>
-<p>The Processes tab (Figure 2) provides a flat list of corresponding kernel objects.
-Click a column title to sort the list by the title attribute in alternating ascending and descending order. For example, you may choose to sort the process list by Name, ID, or by Priority. </p>
-<p align="center"><img src="images/view_symbianOS_PTC.png" width="602" height="291" alt="" /></p>
-<p class="figure">Figure 2. Processes Pane of Symbian view</p>
-<p>The process(es) being debugged will be shown in bold font. You can debug (attach debugger to) any process in the Processes tab by selecting it and clicking the "Debug" button or just by double clicking on it. In that case a new process item will show up in the Debug View if the process is not being debugged. Otherwise, you will get a message saying it's already under debug.</p>
-<h4>Other references</h4>
-<ul>
- <li><a href="../debugger/debug/viewing_debug.htm">Debug view</a></li>
- <li><a href="../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
- </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/reference/view_sym_os_data_threads.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,36 +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>Symbian OS Data: Threads</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body >
-<h2>Symbian Data view: Threads</h2>
-<p>The <img src="../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.edc.ui.SymbianSystemView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. Data to be viewed includes:</p>
-<ul>
- <li><a href="view_sym_os_data_overview.htm">Overview</a></li>
- <li><a href="view_sym_os_data_process.htm">Processes</a></li>
- <li><a href="view_sym_os_data_threads.htm">Threads</a></li>
- <li><a href="view_sym_os_data_chunks.htm">Chunks</a></li>
- <li><a href="view_sym_os_data_libs.htm">Libraries</a></li>
-</ul>
-<hr>
-<h2><a name="threads" id="threads"></a>Threads</h2>
-<p>The Threads tab (Figure 3) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header. The thread(s) being debugged will be shown in bold font.</p>
-<p class="note"><b>NOTE</b> You can debug (attach debugger to) any thread in the Thread tab by double clicking on it or selecting it and clicking the Debug button. In that case, a new thread item will show up in Debug view if the thread is not being debugged.</p>
-<p align="center"><img src="images/view_symbianOS_threads.png" width="602" height="291" alt="" /></p>
-<p class="figure">Figure 3. Threads Pane of Symbian view</p>
-<h4>Other references</h4>
-<ul>
- <li><a href="../debugger/debug/viewing_debug.htm">Debug view</a></li>
- <li><a href="../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
- </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/reference/view_symbian_kernel.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,114 +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>Symbian OS Data</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body >
-<h2>Symbian Data view</h2>
-<p>The <img src="../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.debug.kernelaware.ui.SymbianOSView)")'>Symbian Data</a> view displays the processes and threads for the suspended debug session based on the selection in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> view. Read-only data is displayed for ARM build configurations. To open the Symbian Data view select<b> Window > Show View > Symbian Data</b> when the <a href="perspective_debug.htm">Debug</a> perspective is visible or select <b>Window > Show View > Other...</b>, then expand the Carbide.c++ folder and select <b>Symbian Data</b> when the <a href="../projects/views/perspective_carbide.htm">Carbide C/C++ perspective</a> is visible. Click <b>Ok</b> to display the Symbian Data window (Figure 1).</p>
-<p class="note"><b>NOTE</b> The Symbian Data view works with the debugger and will only display data during a live debug session. The Symbian Data view is not supported for emulator debugging, and will not show anything during emulator debug.</p>
-<p>The <b>Symbian Data</b> view reveals kernel data in the Symbian running on the device being debugged. The kernel data displayed is always that of the device with the currently selected thread or process in <a href="../debugger/debug/viewing_debug.htm">Debug</a> view. If you are debugging two devices at the same time, the content of the view will change when focus is switched from a thread on one device to a thread on another device. The kernel data includes more than just processes and threads. </p>
-<p>For the stop mode debugger and the crash debugger, all the data listed above is supported. For the Application and Symbian Device debuggers, the chunks and libraries views are not supported. The Symbian Data view is not supported for the emulator debugger and will show nothing during an emulator debug session. During a stop mode debug session or a CODA debug session, you are able to select a process or a thread in the Symbian Data view and attach the debugger to it for source level debugging if the binary is listed in the <a href="../projects/views/view_executables.htm">Executables</a> view. Binaries listed in the Executable view can be source level debugged. Binaries not listed in the Executables view can only be assembly code debugged in the <a href="view_disassembly.htm">Disassembly</a> view.</p>
-<p class="note"><b>NOTE</b> Any executable must be included in the <b>Executables</b> view before it can be debugged. </p>
-<p>When the <a href="pref_carb_debugger.htm">Time interval for auto-refreshing OS View</a> option is enabled (which is on by default except for crash debugger), the data in the Symbian Data view will be auto-refreshed. Note that "auto-refresh" has a different meaning in different debuggers. During a stop mode debug session, the view will refresh data whenever the debugged program on the device is stopped and shows data as stale (greyed out) when the program is running. During a CODA debug session, the View will refresh data at a time interval regardless of whether the debugged program is stopped or not. The time interval is specified by an option in the Carbide.c++ global preference panel, which is five seconds by default.</p>
-<p>When auto-refresh is turned off, the debugger will not automatically refresh data in the View and will show the data as stale (greyed out). However you can manually refresh the data by clicking on the "Refresh" button in the View. Usually you may want to turn off the auto-refresh if you think it is slowing down your debug operations such as stepping.</p>
-<h3>Symbian Data pages
-</h3>
-<p>The Symbian Data view consists of five tabs. Each tabbed pane is described below. In all panes, the <b>Name Filter</b> field is a standard Eclipse UI control that allows you to find an item by filtering out items by name using wildcards (*, ?) and camel case naming conventions. Camel case refers to using mixed case multiple names merged together in coding like <span class="code">SecInvInit</span> and <span class="code">DosServer</span>. In all panes, you can select an item and view its properties (attributes). In panes with columns you can click a column title to toggle between ascending and descending sorting. </p>
-<p>Data to be viewed includes:</p>
-<ul>
- <li><a href="#overview">Overview</a></li>
- <li><a href="#processes">Processes</a></li>
- <li><a href="#threads">Threads</a></li>
- <li><a href="#chunks">Chunks</a></li>
- <li><a href="#Library">Libraries</a></li>
-</ul>
-<p class="note"><b>NOTE</b> Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.</p>
-<h4><a name="overview" id="overview"></a>Overview Tab</h4>
-<p>This tab (shown in Figure 1) provides a tree view of ownership of all processes, threads, and chunks in the OS.
- In contrast, the other tabs provide a flat list of corresponding kernel objects such as process, thread, chunk, library, etc.</p>
-<p align="center"><img src="images/view_symbianOSkernel.png" width="602" height="300" alt="" /></p>
-<p class="figure">Figure 1. Symbian Data view</p>
-<h5>Table 1 - Symbian Data view toolbar buttons </h5>
-<table cellpadding="2" cellspacing="0"
-border="0">
- <tr valign="top">
- <th width="209" class="Cell">Button</th>
- <th width="49" class="Cell">Icon</th>
- <th width="534" class="Cell">Function</th>
- </tr>
- <tr valign="top">
- <td class="Cell"><p> <b>Refresh data</b></p></td>
- <td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_refresh.png" width="19" height="19" alt="" /></div></td>
- <td class="Cell"><p> Click this button to force a refresh of data in the view. Use the <a href="pref_carb_debugger.htm">Carbide.c++ Debugger</a> preference panel <b>Time interval for auto-refreshing OS View</b> option to control the automatic refreshing of data. </p></td>
- </tr>
- <tr valign="top">
- <td class="Cell"><p> <b>Enable/disable auto-refresh</b> </p></td>
- <td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_autorefresh.png" width="19" height="21" alt="" /></div></td>
- <td class="Cell"><p> Click this button to turn on/off auto refresh of data.</p></td>
- </tr>
- <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 CODA (run mode) and TCF (stop mode).</p>
- </td>
- </tr>
- <tr valign="top">
- <td class="Cell"><p> <b>Properties</b> </p></td>
- <td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_prop.png" width="21" height="18" alt="" /></div></td>
- <td class="Cell"><p>Click this button to show properties of currently selected item in the <b>Properties</b> view. Or right-click an item and choose <b>Properties</b>.</p></td>
- </tr>
- <tr valign="top">
- <td class="Cell"><p> <b>Timer</b></p></td>
- <td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_timer.png" width="21" height="18" alt="" /></div></td>
- <td class="Cell"><p> Click this button to define the time interval for auto-refreshing data. This applies to run mode debugging only. </p></td>
- </tr>
- <tr valign="top">
- <td class="Cell"><b>Collapse All </b></td>
- <td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_collapse.png" width="17" height="17" alt="" /></div></td>
- <td class="Cell">Click the <b>Collaps All</b> command to collapse all of the currently elements in the view.</td>
- </tr>
-</table>
-<h4><a name="processes" id="processes"></a>Processes</h4>
-<p>The Processes tab (Figure 2) provides a flat list of corresponding kernel objects.
-Click a column title to sort the list by the title attribute in alternating ascending and descending order. For example, you may choose to sort the process list by Name, ID, or by Priority. </p>
-<p align="center"><img src="images/view_symbianOS_PTC.png" width="602" height="291" alt="" /></p>
-<p class="figure">Figure 2. Processes Pane of Symbian View</p>
-<p>The process(es) being debugged will be shown in bold font. You can debug (attach debugger to) any process in the Processes tab by selecting it and clicking the "Debug" button or just by double clicking on it. In that case a new process item will show up in the Debug View if the process is not being debugged. Otherwise, you will get a message saying it's already under debug.</p>
-<h4><a name="threads" id="threads"></a>Threads</h4>
-<p>The Threads tab (Figure 3) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header. The thread(s) being debugged will be shown in bold font.</p>
-<p class="note"><b>NOTE</b> You can debug (attach debugger to) any thread in the Thread tab by double clicking on it or selecting it and clicking the Debug button. In that case, a new thread item will show up in Debug view if the thread is not being debugged.</p>
-<p align="center"><img src="images/view_symbianOS_threads.png" width="602" height="291" alt="" /></p>
-<p class="figure">Figure 3. Threads Pane of Symbian View</p>
-<h4><a name="chunks" id="chunks"></a>Chunks</h4>
-<p>Chunks are an area of contiguous linear memory. It is the unit of memory allocation where a region of RAM is mapped into contiguous logical addresses. Chunks are allocated during boot for such things as the Kernel's data and stack.</p>
-<p>The Chunks tab (Figure 4) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header.</p>
-<p class="note"> <b>NOTE</b> Chunks data is not available during CODA debugging.</p>
-<p align="center"><img src="images/view_symbianOS_chunks.png" width="530" height="278" alt="" /></p>
-<p class="figure">Figure 4. Chunks Pane of Symbian View</p>
-<h4><a name="Library" id="Library"></a>Libraries Tab</h4>
-<p> The Libraries pane (Figure 5) in the Symbian view provides information on libraries in the Symbian residing on the target.</p>
-<p class="note"> <b>NOTE</b> Library data is not available during CODA debugging.</p>
-<p align="center"><img src="images/view_symbianOS_Lib.png" width="531" height="278" alt="" /></p>
-<p class="figure">Figure 5. Libraries Pane of Symbian View</p>
-<h3><a name="attach" id="attach"></a>Attaching to a Process</h3>
-<p>If <span class="note">you double click on a thread item in the Thread tab, or right-click and choose <b>Debug</b>, the owning process of the thread will be attached.</span> The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose <b>Properties</b>.</p>
-<p class="note"><b>NOTE </b>If an executable is not part of a project in the workspace use the Executables view to import an executable to make it visible to the debugger. Once included in the Executables list, the symbolics for that executable can be loaded and breakpoints resolved and hit. Open a source file in an editor view or use the <a href="view_breakpoints.htm">Breakpoints</a> view to verify that the executable breakpoints have been <a href="../concepts/breakpoints.htm">resolved</a>. </p>
-<p class="note"><b>IMPORTANT</b> In stop mode debugging when debugging multiple processes at the same time, selecting a process in the <a href="../debugger/debug/viewing_debug.htm">Debug</a> pane and clicking <b>Terminate</b> disconnects the attached process on the board, leaving all other processes running. It does not terminate the debug session. However, if there is only one debug process when you click <b>Terminate</b> the CPU is suspended until the next debug session.</p>
-<p class="note"><b>WARNING</b> Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device. </p>
-<p><img src="images/symOSData_attachprocess.png" width="1144" height="332" alt="" /></p>
-<h5>Other references</h5>
-<ul>
- <li><a href="../debugger/debug/viewing_debug.htm">Debug view</a></li>
- <li><a href="../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian View Refresh Rate</a><br />
- </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/reference/view_variables.htm Wed Oct 06 14:27:34 2010 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,86 +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>Variables View</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body >
-<h2>Variables View </h2>
-<p>The <b>Variables</b> view allows manipulation of the variables or variable hierarchy used in source code. For example, you can change the variable format, change a variables value, add watchpoints, and add global variables. In addition to the standard C/C++, Symbian, and the Qt data types: <span class="code">QString</span>, <span class="code">QByteArray</span>, <span class="code">QSet</span>, <span class="code">QHash</span>, <span class="code">QMap</span>, <span class="code">QVector</span>, <span class="code">QList</span>, <span class="code">QLinkedList</span> and <span class="code">Qvariant</span>.</p>
-<p>Figure 1 shows the Variables view with <b>Show Type Names</b> option enabled.</p>
-<p align="center"><img src="../images/views/view_variables.png" width="544" height="221" /></p>
-<p class="figure">Figure 1 - Variables view showing type names </p>
-<h5>Table 1. Variables view—items </h5>
-<table width="88%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="34%" scope="col">Item</th>
- <th width="14%" scope="col">Icons</th>
- <th width="52%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Show Type Names </b></td>
- <td><div align="center"><img src="../images/icons/var_toggle_type_names_icon.png" width="19" height="19" /></div></td>
- <td>Toggles the display of type names in the Variables view. </td>
- </tr>
- <tr>
- <td><b>Show Logical Structure </b></td>
- <td><div align="center"><img src="../images/icons/var_show_logical_struct_icon.png" width="19" height="19" /></div></td>
- <td>Not available in C/C++ yet. </td>
- </tr>
- <tr>
- <td><b>Collapse All </b></td>
- <td><div align="center"><img src="../images/icons/var_collapse_all_icon.png" width="17" height="18" /></div></td>
- <td>Collapses all expanded variables into the top level. </td>
- </tr>
- <tr>
- <td><b>Add Global Variables </b></td>
- <td><div align="center"><img src="../images/icons/var_add_global_vars_icon.png" width="19" height="19" /></div></td>
- <td>Click to open a window where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list. </td>
- </tr>
- <tr>
- <td><b>Remove Selected Global Variables </b></td>
- <td><div align="center"><img src="../images/icons/var_remove_selected_globals_icon.png" width="18" height="16" /></div></td>
- <td>Click to remove all currently selected global variables from the variables list. </td>
- </tr>
- <tr>
- <td><b>Remove All Global Variables </b></td>
- <td><div align="center"><img src="../images/icons/var_remove_all_globals_icon.png" width="19" height="19" /></div></td>
- <td>Click to remove all global variables from the variables list. </td>
- </tr>
- <tr>
- <td><b>Menu</b></td>
- <td><div align="center"><img src="images/icon_menu_white.png" width="12" height="12"></div></td>
- <td><p>Enables you to modifiy the <b>Layout</b> to change the view orientation between: horizontal, vertical, or variables pane only.</p>
- <p>In addition, use <b>Show All Variables</b> to toggle between showing only those variables that are in scope and live or show all local variables, even if redundant. With this option on you will see all of the variables including the multiple defined variables like “i” for your loops and ones that may no longer have accurate values.</p></td>
- </tr>
-</table>
-<div class="step">
- <h4>To open the Variables view </h4>
- <ul>
- <li>Click Window > Show View > Variables </li>
- <p>The Variables view appears.</p>
- </ul>
-</div>
-<h5>Related concepts</h5>
-<ul>
- <li><a href="../concepts/common_debug_actions.htm">Common Debug Actions </a></li>
- <li><a href="../concepts/working_with_memory.htm">Working with Memory</a></li>
- <li><a href="../concepts/working_with_variables.htm">Working with Variables</a> </li>
-</ul>
-<h5>Related tasks</h5>
-<ul>
- <li><a href="perspective_debug.htm">Showing the Variables View</a> </li>
- <li><a href="perspective_debug.htm">Showing Global Variables</a> </li>
-</ul>
-<h5>Related References </h5>
-<ul>
- <li><a href="view_expressions.htm">Expressions View</a></li>
- <li><a href="../concepts/working_with_variables.htm">Variables 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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/views.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/views.htm Wed Oct 06 14:30:50 2010 -0500
@@ -11,8 +11,8 @@
<h2>Working with Memory</h2>
<p> This section explains how to work with variables in a Carbide.c++ debugging session. The following views show various types of information about variables:</p>
<ul>
- <li><a href="view_variables.htm">Memory</a> view —shows the memory that your project manipulates as it executes</li>
- <li><a href="view_registers.htm">Registers</a> view—shows the register contents of a processor</li>
+ <li><a href="../debugger/views/view_variables.htm">Memory</a> view —shows the memory that your project manipulates as it executes</li>
+ <li><a href="../debugger/views/view_registers.htm">Registers</a> view—shows the register contents of a processor</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/reference/views_overview.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/views_overview.htm Wed Oct 06 14:30:50 2010 -0500
@@ -20,17 +20,17 @@
</ul>
<h4>Debug perspective views:</h4>
<ul>
- <li><a href="view_breakpoints.htm">Breakpoints</a> view</li>
+ <li><a href="../debugger/views/view_breakpoints.htm">Breakpoints</a> view</li>
<li><a href="../projects/views/view_console.htm">Console</a> view</li>
<li><a href="../debugger/debug/viewing_debug.htm">Debug</a> view</li>
- <li><a href="view_disassembly.htm">Disassembly</a> view</li>
- <li><a href="view_expressions.htm">Expressions</a> view</li>
- <li><a href="view_memory.htm">Memory</a> view</li>
- <li><a href="view_module.htm">Modules</a> view</li>
- <li><a href="view_registers.htm">Registers</a> view</li>
- <li><a href="view_symbian_kernel.htm">Symbian Data</a> view</li>
- <li><a href="view_signals.htm">Signels</a> view</li>
- <li><a href="view_variables.htm">Variables</a> view</li>
+ <li><a href="../debugger/views/view_disassembly.htm">Disassembly</a> view</li>
+ <li><a href="../debugger/views/view_expressions.htm">Expressions</a> view</li>
+ <li><a href="../debugger/views/view_memory.htm">Memory</a> view</li>
+ <li><a href="../debugger/views/view_module.htm">Modules</a> view</li>
+ <li><a href="../debugger/views/view_registers.htm">Registers</a> view</li>
+ <li><a href="../debugger/views/view_symbian_kernel.htm">Symbian Data</a> view</li>
+ <li><a href="../debugger/views/view_signals.htm">Signels</a> view</li>
+ <li><a href="../debugger/views/view_variables.htm">Variables</a> view</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/StopModeToc.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/StopModeToc.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
<li><a href="debugger/stop_mode_debug.htm">Stop Mode Debug Example </a></li>
<li><a href="../reference/ROM_build_settings.html">Building a ROM Image File</a></li>
<li><a href="../concepts/arm_registers.htm">ARM Registers</a></li>
- <li><a href="../reference/view_symbian_kernel.htm">Symbian Data View </a></li>
+ <li><a href="../debugger/views/view_symbian_kernel.htm">Symbian Data 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/tasks/breakpoints/pgm_bp_clearing.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_clearing.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2>Removing Breakpoints</h2>
-<p>You can remove one or more breakpoints set for a debug session using the <a href="../../reference/view_breakpoints.htm">Breakpoints</a>, <a href="../../reference/view_disassembly.htm">Disassembly</a>, or editor views.</p>
+<p>You can remove one or more breakpoints set for a debug session using the <a href="../../debugger/views/view_breakpoints.htm">Breakpoints</a>, <a href="../../debugger/views/view_disassembly.htm">Disassembly</a>, or editor views.</p>
<div class="step">
<h4>Removing a Breakpoint</h4>
<ol>
@@ -65,7 +65,7 @@
</ul>
<h5>Related references</h5>
<ul>
- <li><a href="../../reference/perspective_debug.htm">Debug Perspective </a></li>
+ <li><a href="../../debugger/views/perspective_debug.htm">Debug Perspective </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/breakpoints/pgm_bp_conditional.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_conditional.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2>Setting Conditional Breakpoints or Watchpoints </h2>
-<p>You create a conditional (temporary) breakpoint or watchpoint in the<b> Properties for C/C++ breakpoint </b>dialog. Right-click a breakpoint or watchpoint in the <a href="../../reference/view_breakpoints.htm">Breakpoints</a> view, then select <b>Properties</b> from the context menu. A conditional breakpoint or watchpoint has an associated conditional expression. The debugger evaluates the expression to determine whether to halt program execution at that breakpoint.</p>
+<p>You create a conditional (temporary) breakpoint or watchpoint in the<b> Properties for C/C++ breakpoint </b>dialog. Right-click a breakpoint or watchpoint in the <a href="../../debugger/views/view_breakpoints.htm">Breakpoints</a> view, then select <b>Properties</b> from the context menu. A conditional breakpoint or watchpoint has an associated conditional expression. The debugger evaluates the expression to determine whether to halt program execution at that breakpoint.</p>
<p>A conditional breakpoint or watchpoint behaves in two different ways:</p>
<ul>
<li>If the expression evaluates to <span class="code">true</span> (a non-zero value), the debugger halts program execution.</li>
@@ -49,7 +49,7 @@
</ul>
<h5>Related references </h5>
<ul>
- <li><a href="../../reference/view_breakpoints.htm">Breakpoints view</a></li></ul>
+ <li><a href="../../debugger/views/view_breakpoints.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/tasks/breakpoints/pgm_bp_disable.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_disable.htm Wed Oct 06 14:30:50 2010 -0500
@@ -40,7 +40,7 @@
</ul>
<h5>Related references </h5>
<ul>
- <li><a href="../../reference/view_breakpoints.htm">Breakpoints view</a></li>
+ <li><a href="../../debugger/views/view_breakpoints.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/tasks/breakpoints/pgm_bp_enable.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_enable.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2>Enabling Breakpoints</h2>
-<p>Enable a breakpoint to have it halt program execution at the specific line in the source file. You can set a breakpoint using the <a href="../../reference/view_breakpoints.htm">Breakpoints</a>, <a href="../../reference/view_disassembly.htm">Disassembly</a>, or editor views. An enabled breakpoint must still be <a href="../../concepts/breakpoints.htm">resolved</a> during a debug session before it can halt program execution. Enabling a breakpoint that you previously disabled is easier than clearing it and re-creating it from scratch. </p>
+<p>Enable a breakpoint to have it halt program execution at the specific line in the source file. You can set a breakpoint using the <a href="../../debugger/views/view_breakpoints.htm">Breakpoints</a>, <a href="../../debugger/views/view_disassembly.htm">Disassembly</a>, or editor views. An enabled breakpoint must still be <a href="../../concepts/breakpoints.htm">resolved</a> during a debug session before it can halt program execution. Enabling a breakpoint that you previously disabled is easier than clearing it and re-creating it from scratch. </p>
Figure 1 shows some source code and the selected line shows the breakpoint icon that appears in the marker bar when a breakpoint is enabled.
<p align="center"><img src="images/breakpoints_marker_bar.png" width="582" height="230" alt="" /></p>
<p class="figure">Figure 1 - Enabling breakpoint</p>
@@ -41,7 +41,7 @@
</ul>
<h5>Related references </h5>
<ul>
- <li><a href="../../reference/view_breakpoints.htm">Breakpoints view</a></li>
+ <li><a href="../../debugger/views/view_breakpoints.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/tasks/breakpoints/pgm_bp_exporting.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_exporting.htm Wed Oct 06 14:30:50 2010 -0500
@@ -66,7 +66,7 @@
</ul>
<h5>Related references </h5>
<ul>
- <li><a href="../../reference/view_breakpoints.htm">Breakpoints view</a></li>
+ <li><a href="../../debugger/views/view_breakpoints.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/tasks/breakpoints/pgm_bp_importing.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_importing.htm Wed Oct 06 14:30:50 2010 -0500
@@ -64,7 +64,7 @@
</ul>
<h5>Related references </h5>
<ul>
- <li><a href="../../reference/view_breakpoints.htm">Breakpoints view</a></li>
+ <li><a href="../../debugger/views/view_breakpoints.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/tasks/breakpoints/pgm_bp_setting.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_setting.htm Wed Oct 06 14:30:50 2010 -0500
@@ -11,7 +11,7 @@
<h2>Setting Breakpoints</h2>
<p>Use the <b>Set Breakpoint</b> command (<span class="code">Ctrl+Shift+B</span>) to set a breakpoint. A regular breakpoint suspends program execution. The debugger executes the line of source code that contains the regular breakpoint.</p>
<p class="note"><strong>TIP</strong> If you find that a breakpoint is not being hit, verify that the EXE or DLL is listed in the <a href="../../projects/views/view_executables.htm">Executables</a> view. </p>
-<p class="note"><strong>TIP</strong> If debugging a server launched by a client, you must attach to the server process using the <a href="../../reference/view_symbian_kernel.htm">Symbian Data</a> view in order to hit the breakpoints in the server. Alternately, you can launch the server and client as two independent EXEs using the same COM port and debug them that way. </p>
+<p class="note"><strong>TIP</strong> If debugging a server launched by a client, you must attach to the server process using the <a href="../../debugger/views/view_symbian_kernel.htm">Symbian Data</a> view in order to hit the breakpoints in the server. Alternately, you can launch the server and client as two independent EXEs using the same COM port and debug them that way. </p>
<p>Figure 1 shows some source code and the marker bar to the left of the source code. The selected line shows the breakpoint dot that appears in the marker bar when a breakpoint is set.</p>
<p align="center"><img src="images/breakpoints_marker_bar.png" width="582" height="230" /></p>
<p class="figure">Figure 1 - Setting Breakpoints in an editor view </p>
@@ -54,7 +54,7 @@
</ul>
<h5>Related references </h5>
<ul>
- <li><a href="../../reference/view_breakpoints.htm">Breakpoints view</a></li>
+ <li><a href="../../debugger/views/view_breakpoints.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/tasks/breakpoints/pgm_bp_temporary.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_temporary.htm Wed Oct 06 14:30:50 2010 -0500
@@ -39,7 +39,7 @@
</ul>
<h5>Related references </h5>
<ul>
- <li><a href="../../reference/view_breakpoints.htm">Breakpoints view</a></li>
+ <li><a href="../../debugger/views/view_breakpoints.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/tasks/breakpoints/save_breakpoints_view.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/save_breakpoints_view.htm Wed Oct 06 14:30:50 2010 -0500
@@ -30,7 +30,7 @@
</ul>
<h5>Related references </h5>
<ul>
- <li><a href="../../reference/view_breakpoints.htm">Breakpoints view</a></li>
+ <li><a href="../../debugger/views/view_breakpoints.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/tasks/breakpoints/show_breakpoints_view.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/show_breakpoints_view.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2>Opening a Breakpoints View </h2>
-<p>Use the <a href="../../reference/view_breakpoints.htm">Breakpoints</a> view to show a list of breakpoints currently set in your project.</p>
+<p>Use the <a href="../../debugger/views/view_breakpoints.htm">Breakpoints</a> view to show a list of breakpoints currently set in your project.</p>
<p align="center"><img src="../../reference/images/view_breakpoints.png" width="544" height="264" /></p>
<p class="figure">Figure 1 - Breakpoints view </p>
<div class="step">
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/custom/carb_custom_menus.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/custom/carb_custom_menus.htm Wed Oct 06 14:30:50 2010 -0500
@@ -10,7 +10,7 @@
</head>
<body >
<h2>Customizing Carbide: Toolbars and Menus</h2>
-<p> You can customize which commands appear on toolbars and menus using the <img src="../../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.project.ui.views.SymbianProjectNavigatorView)")'>Customize Perspective</a> dialog. For purposes of customizing Carbide there are two perspectives of interest, the <a href="../../projects/views/perspective_carbide.htm">Carbide C/C++</a> perspective where project management and editing occurs and the <a href="../../reference/perspective_debug.htm">Debug</a> perspective used for debugging a project.</p>
+<p> You can customize which commands appear on toolbars and menus using the <img src="../../images/command_link.png" border="0" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=com.nokia.carbide.cpp.project.ui.views.SymbianProjectNavigatorView)")'>Customize Perspective</a> dialog. For purposes of customizing Carbide there are two perspectives of interest, the <a href="../../projects/views/perspective_carbide.htm">Carbide C/C++</a> perspective where project management and editing occurs and the <a href="../../debugger/views/perspective_debug.htm">Debug</a> perspective used for debugging a project.</p>
<p>Click <strong>Window > Customize Perspectve...</strong> to open the <strong>Customize Perspective</strong> dialog which allows you to customize the current perspective. There are four tabs enabling you to customize the Carbide commands in multiple ways. The tabs include:</p>
<ul>
<li><a href="#toolbar">Toolbar Visibility</a></li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/soft_attach_debug.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/soft_attach_debug.htm Wed Oct 06 14:30:50 2010 -0500
@@ -99,9 +99,9 @@
<ul>
<li><a href="../../reference/panel_debug_exceptions.htm">Debug</a> perspective </li>
<li><a href="../../projects/views/view_executables.htm">Executables</a> view</li>
- <li><a href="../../reference/view_symbian_kernel.htm">Symbian Data</a> view</li>
- <li><a href="../../reference/view_registers.htm">Registers</a> view</li>
- <li><a href="../../reference/view_breakpoints.htm">Breakpoint</a> view </li>
+ <li><a href="../../debugger/views/view_symbian_kernel.htm">Symbian Data</a> view</li>
+ <li><a href="../../debugger/views/view_registers.htm">Registers</a> view</li>
+ <li><a href="../../debugger/views/view_breakpoints.htm">Breakpoint</a> view </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/debugger/view_symbian_kernel_set.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/view_symbian_kernel_set.htm Wed Oct 06 14:30:50 2010 -0500
@@ -22,13 +22,13 @@
</div>
<h5>Related concepts</h5>
<ul>
- <li><a href="../../reference/view_symbian_kernel.htm">Symbian Kernel View</a></li>
+ <li><a href="../../debugger/views/view_symbian_kernel.htm">Symbian Kernel View</a></li>
<li><a href="../../concepts/working_with_debugger.htm">Working with the Debugger </a></li>
</ul>
<h5>Related references </h5>
<ul>
<li><a href="../../debugger/debug/viewing_debug.htm">Debug View</a></li>
- <li><a href="../../reference/view_symbian_kernel.htm">Symbian View Window</a></li>
+ <li><a href="../../debugger/views/view_symbian_kernel.htm">Symbian View Window</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/memory/memory_monitor_adding.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_monitor_adding.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2>Adding a Memory Monitor </h2>
-<p>You can add one or more memory monitors to the <a href="../../reference/view_memory.htm">Memory</a> view. A memory monitor shows the contents of a different address or expression. </p>
+<p>You can add one or more memory monitors to the <a href="../../debugger/views/view_memory.htm">Memory</a> view. A memory monitor shows the contents of a different address or expression. </p>
<p class="note"><b>NOTE</b> When using an emulator, the memory addresses are actually based on their location and formats dependent upon the host machine. </p>
<div class="step">
<h4>To add a Memory Monitor</h4>
@@ -49,7 +49,7 @@
</ul>
<h5>Related References </h5>
<ul>
- <li><a href="../../reference/view_memory.htm">Memory View</a></li>
+ <li><a href="../../debugger/views/view_memory.htm">Memory 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/tasks/memory/memory_monitor_removing.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_monitor_removing.htm Wed Oct 06 14:30:50 2010 -0500
@@ -50,7 +50,7 @@
</ul>
<h5>Related References </h5>
<ul>
- <li><a href="../../reference/view_memory.htm">Memory View</a>
+ <li><a href="../../debugger/views/view_memory.htm">Memory 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/tasks/memory/memory_rendering_adding.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_rendering_adding.htm Wed Oct 06 14:30:50 2010 -0500
@@ -42,7 +42,7 @@
</ul>
<h5>Related References </h5>
<ul>
- <li><a href="../../reference/view_memory.htm">Memory View</a></li>
+ <li><a href="../../debugger/views/view_memory.htm">Memory 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/tasks/memory/view_memory_show.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/view_memory_show.htm Wed Oct 06 14:30:50 2010 -0500
@@ -30,7 +30,7 @@
</ul>
<h5>Related References </h5>
<ul>
- <li><a href="../../reference/view_memory.htm">Memory View</a></li>
+ <li><a href="../../debugger/views/view_memory.htm">Memory 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/tasks/processes/attach_to_process.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_to_process.htm Wed Oct 06 14:30:50 2010 -0500
@@ -12,7 +12,7 @@
<div>
<p>Use a <b>Symbian Attach to Process</b> launch configuration to attach the debugger to an already running Symbian process or thread on a target device. This is useful for debugging DLLs where the main process is unknown or for servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate.</p>
<p>One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the <a href="../../projects/views/view_executables.htm">Executables</a> view.</p>
- <p>You can also attach to a process in the <a href="../../reference/view_symbian_kernel.htm">Symbian Data</a> view when debugging.</p>
+ <p>You can also attach to a process in the <a href="../../debugger/views/view_symbian_kernel.htm">Symbian Data</a> view when debugging.</p>
<p class="note"><b>NOTE</b> You cannot attach to a process running on the emulator. It must be a target device running the Symbian and the CODA software.</p>
<p>When attempting to find a process the debugger uses the UID3 to locate the process. </p>
<div class="step">
@@ -33,7 +33,7 @@
<p align="center"><img src="images/sos_processes_choose_thread.png" width="300" height="375" /></p>
<p class="figure">Figure 3 -<b> Attach to Process</b> window </p>
<li>Select a process, click OK.</li>
- <p>In this example we've linked the <span class="code">prefs.dll</span> program to the process <span class="code">BlackFlag.exe</span> on the device. The <b>Attach to Process </b>dialog closes. Open the <a href="../../reference/view_symbian_kernel.htm">Symbian Data</a> view to show the process and thread information.</p>
+ <p>In this example we've linked the <span class="code">prefs.dll</span> program to the process <span class="code">BlackFlag.exe</span> on the device. The <b>Attach to Process </b>dialog closes. Open the <a href="../../debugger/views/view_symbian_kernel.htm">Symbian Data</a> view to show the process and thread information.</p>
<p class="note"><b>NOTE</b> Terminating an Attach to Process session actually kills the process on the device. This means you must restart the process on the device in order to attach to it again. </p>
</ol>
</div>
@@ -41,7 +41,7 @@
<ul>
<li><a href="../../debugger/debug/viewing_debug.htm">Debug View</a></li>
<li><a href="../../reference/wnd_debug_configuration.htm">Debug Window </a></li>
- <li><a href="../../reference/view_symbian_kernel.htm">Symbian View</a> </li>
+ <li><a href="../../debugger/views/view_symbian_kernel.htm">Symbian View</a> </li>
<li><a href="../projects/prj_debug_dlls_any_process.htm">Debugging DLLs with any Process</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_dlls.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_dlls.htm Wed Oct 06 14:30:50 2010 -0500
@@ -19,7 +19,7 @@
<ul>
<li>If the DLL is not built by the project you can import the DLL by clicking the<b> Import an executable file</b> icon (<img src="../../images/icons/btn_import_executables.png" width="18" height="15" align="absmiddle">) in the <a href="../../projects/views/view_executables.htm">Executables</a> view. Then, set your breakpoints and start the debug session.</li>
</ul>
-<p> You can use the <a href="../../reference/view_module.htm">Modules</a> view to determine if a particular DLL or binary is loaded and available for debugging.</p>
+<p> You can use the <a href="../../debugger/views/view_module.htm">Modules</a> view to determine if a particular DLL or binary is loaded and available for debugging.</p>
<h5>Other references</h5>
<ul>
<li><a href="../../projects/views/view_executables.htm">Executables</a> view </li>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_changing.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_changing.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2>Changing Register Values</h2>
-<p> You can change register values in the <a href="../../reference/view_registers.htm">Registers</a> view during program execution in order to examine program behavior.</p>
+<p> You can change register values in the <a href="../../debugger/views/view_registers.htm">Registers</a> view during program execution in order to examine program behavior.</p>
<p class="note"><b>NOTE</b> Changing a register value can cause unpredictable behavior in the running program. </p>
<div class="step">
<h4>Changing a Register Value </h4>
@@ -42,7 +42,7 @@
<li><a href="../../concepts/registers.htm">Registers</a></li>
<li><a href="mem_reg_open_wnd.htm">Opening Register View</a></li>
<li><a href="mem_reg_viewing.htm">Viewing Register Values </a></li>
- <li><a href="../../reference/view_registers.htm">Registers view </a></li>
+ <li><a href="../../debugger/views/view_registers.htm">Registers 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/tasks/registers/mem_reg_data_views.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_data_views.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2>Changing Register Data Views</h2>
-<p> You can change the register data in the <a href="../../reference/view_registers.htm">Registers</a> view to see register contents in a different format. For example, you can change the view of a register from binary to hexadecimal format.</p>
+<p> You can change the register data in the <a href="../../debugger/views/view_registers.htm">Registers</a> view to see register contents in a different format. For example, you can change the view of a register from binary to hexadecimal format.</p>
<div class="step">
<h4>To change register data views</h4>
<ol>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_open_wnd.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_open_wnd.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2>Opening a Registers View </h2>
-<p> Open the <a href="../../reference/view_registers.htm">Registers</a> view to <a href="mem_reg_viewing.htm">inspect</a> and <a href="mem_reg_changing.htm">modify</a> various register contents.</p>
+<p> Open the <a href="../../debugger/views/view_registers.htm">Registers</a> view to <a href="mem_reg_viewing.htm">inspect</a> and <a href="mem_reg_changing.htm">modify</a> various register contents.</p>
<p class="note"><b>NOTE</b> When using an emulator, the registers shown are those of the x86 processor on the host machine, not that of the target device.</p>
<div class="step">
<h4>To open a Registers view </h4>
@@ -23,7 +23,7 @@
<h5>Other references </h5>
<ul>
<li><a href="../../concepts/registers.htm">Register</a></li>
- <li><a href="../../reference/view_registers.htm">Registers view </a></li>
+ <li><a href="../../debugger/views/view_registers.htm">Registers view </a></li>
<li><a href="mem_reg_viewing.htm">Viewing Register Values </a></li>
<li><a href="mem_reg_changing.htm">Changing Register Values</a></li>
</ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_viewing.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_viewing.htm Wed Oct 06 14:30:50 2010 -0500
@@ -9,7 +9,7 @@
</head>
<body >
<h2>Expanding Register Groups</h2>
-<p>You can expand register groups in the <a href="../../reference/view_registers.htm">Registers</a> view to inspect and <a href="mem_reg_changing.htm">modify</a> their contents.</p>
+<p>You can expand register groups in the <a href="../../debugger/views/view_registers.htm">Registers</a> view to inspect and <a href="mem_reg_changing.htm">modify</a> their contents.</p>
<p class="note"><b>NOTE</b> When using an emulator, the registers shown are those of the x86 processor on the host machine, not that of the target device.</p>
<div class="step">
<h4>Viewing Register Groups </h4>
@@ -26,7 +26,7 @@
<ul>
<li><a href="../../concepts/registers.htm">Registers</a></li>
<li><a href="mem_reg_changing.htm">Changing Register Values</a></li>
- <li><a href="../../reference/view_registers.htm">Registers View </a></li>
+ <li><a href="../../debugger/views/view_registers.htm">Registers 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/tasks/start/carbide_example_trk.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Wed Oct 06 14:30:50 2010 -0500
@@ -46,7 +46,7 @@
<p>The SISX file is downloaded and authenticated, then the binaries are installed automatically on the phone. </p>
</ol>
<li>Once the debug session launches, control returns to the Debugger when one of the breakpoints set earlier is hit. </li>
- <p>At this point you can debug the program in the Debug perspective. Look at the <a href="../../reference/view_breakpoints.htm">Breakpoints</a> view to verify that the breakpoints set earlier are resolved. In this case, the breakpoint in the MCServer.exe.</p>
+ <p>At this point you can debug the program in the Debug perspective. Look at the <a href="../../debugger/views/view_breakpoints.htm">Breakpoints</a> view to verify that the breakpoints set earlier are resolved. In this case, the breakpoint in the MCServer.exe.</p>
<p align="center"><img src="../trk/images/trk_debug_perspective_dll.png" width="902" height="629"></p>
<p class="figure">Figure 5 - Debug perspective showing the resolved breakpoint </p>
<li>Click Resume in the Debug view to hit the breakpoint set in the second EXE</li>
@@ -59,12 +59,12 @@
</ol>
</li>
</ol>
- <p>In addition, you can click the <a href="../../reference/view_symbian_kernel.htm">Symbian Data View</a> to examine the processes running on the devise during the debug session. </p>
+ <p>In addition, you can click the <a href="../../debugger/views/view_symbian_kernel.htm">Symbian Data View</a> to examine the processes running on the devise during the debug session. </p>
</div>
<h5>Related references</h5>
<ul>
<li><a href="../trk/trk_troubleshooting.htm">On-device Debugging Troubleshooting</a></li>
- <li><a href="../../reference/view_symbian_kernel.htm">Symbian View</a></li>
+ <li><a href="../../debugger/views/view_symbian_kernel.htm">Symbian 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/tasks/start/carbide_overview_trk.htm Wed Oct 06 14:27:34 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview_trk.htm Wed Oct 06 14:30:50 2010 -0500
@@ -37,7 +37,7 @@
<h5>Related references</h5>
<ul>
<li><a href="../trk/trk_troubleshooting.htm">On-device Debugging Troubleshooting</a></li>
- <li><a href="../../reference/view_symbian_kernel.htm">Symbian View</a></li>
+ <li><a href="../../debugger/views/view_symbian_kernel.htm">Symbian 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>