AIF File in Concepts

- The AIF, or application information file, is a Symbian OS-specific file - format. An AIF file contains information about captions, icons, capabilities - and MIME priority support used by the application. The MMP editor provides support for the AIF editor in the Sources > Resources group.

Related tasks

Related references

AIF File

+ The AIF, or Application Information File, is a Symbian OS-specific file + format. An AIF file contains information about captions, icons, capabilities + and MIME priority support used by the application. The MMP editor provides support for the AIF editor in the Sources > Resources group.

Related tasks

Related references

Carbide.c++ perspective

- The

Carbide C/C++ perspective is a set of tools and layout of views provided for Symbian OS development. This perspective is designed to work with Symbian OS C++ projects. The commonly used views include:

NOTE Click the

icon to show additional options that may not be visible in the perspective view.

For more information on perspectives see Workbench User Guide > Concepts > Perspectives, and for views see C/C++ Development User Guide > Reference - > C/C++ Views and Editors.

- For more details on the Symbian OS Build Configurations, see - Active Configurations.

Related references

Carbide.c++ perspective

+ The

NOTE Click the

icon to show additional options that may not be visible in the perspective view.

For more information on perspectives see Workbench User Guide > Concepts > Perspectives, and for views see C/C++ Development User Guide > Reference + > C/C++ Views and Editors.

+ For more details on the Symbian OS Build Configurations, see + Active Configurations.

Related references

MBM File

- MBM, or multi-bitmap, is a Symbian OS-specific bitmap file format. This - file contains multiple bitmaps and it can contain both bitmaps with masks and - bitmaps without masks. It optimizes the bitmap handling capability of Symbian - OS. The MMP editor (in Sources tab > Resources > Bitmaps) and Symbian Project Navigator view provide support for creating and editing mbm - files. In the Symbian Project Navigator you can right-click on a scalable icon makefile (for example, Icons_scalable_dc.mk) and select Add MBM/MIF Entry... to open the Edit MBM/MIF Contents window.

Related tasks

Related references

MBM File

+ MBM, or multi-bitmap, is a Symbian OS-specific bitmap file format. This + file contains multiple bitmaps and it can contain both bitmaps with masks and + bitmaps without masks. It optimizes the bitmap handling capability of Symbian + OS. The MMP Editor (in Sources tab > Resources > Bitmaps) and Symbian Project Navigator view provide support for creating and editing MBM + files. In the Symbian Project Navigator view you can right-click on a scalable icon makefile (for example, Icons_scalable_dc.mk) and select Add MBM/MIF Entry... to open the Edit MBM/MIF Contents window.

Related tasks

Related references

Auto-Targeting of Executables

In run-mode debugger now supports the auto-targeting of processes that are already running or are created during the execution of the debug session. Previously, the debugger forced users to explicitly attach to a running process. Now, the debugger attempts to target all the EXEs specified in the Executables tab of the launch configuration.

In run-mode the Carbide debugger now supports the auto-targeting of processes that are already running or are created during the execution of the debug session. Previously, the debugger forced users to explicitly attach to a running process. Now, the debugger attempts to target all the EXEs specified in the Executables tab of the launch configuration.

Other References

Active Build Configuration

Use the Active Configuration option in the Carbide Build Configurations panel to specify the build target. Since a project can contain one or more build targets, the active configuration defines which build configuration to use when the project is run or debugged. A launch configuration consists of the following:

Build configurations are defined when the project is created. A project can have any number of build configurations and more can be added as necessary. Each build configuration can have its own combination of tool settings to precisely control how it is defined and built. Build configurations are maintained in the project Properties window in the Carbide Build Configurations panel. To open the panel, select a project in the Symbian Project Navigator or Project Explorer view and select Project > Properties or right-click and select Properties.

You can select a build configuration in the Active Configuration dropdown list or use the Project > Active Configuration menu option to set which build configuration to launch when running or debugging a program. The currently selected project can be launched by clicking the Run (

) or Debug (

) control on the tool bar to launch the project with the currently active build configuration. When no project is selected the last project debugged will be launched.

If no launch configuration is present in the project, one is created on initial launch. Subsequent launches of the project will use either the last launch configuration or if more than one launch configuration exists, it uses the most correct one.

NOTE The Carbide Run and Debug buttons are shaded in blue to indicate their behavior differs from the standard Eclipse behavior.

Table 1 Carbide Build Configuration items

Build Configuration Naming

Item	Explanation
Active Configuration	The Active Configuration drop down list allows you to select a configuration that is currently available for the selected project. The entries in the related sub-panes will change according to the selected configuration. The Configuration name consists of a target name and an SDK identifier in brackets.
Manage...	Click the Manage... button to add a new SDK/Configuration or remove an existing configuration.

When the Carbide.c++ IDE creates an build configuration it uses a standard naming convention to make it easy to identify. For example, HelloCarbide S60 3.0 Emulator Debug is a typical configuration name. The default name follows the form of:

Other references

Active Build Configuration

) or Debug (

) control on the tool bar to launch the project with the currently active build configuration. When no project is selected the last project debugged will be launched.

NOTE The Carbide Run and Debug buttons are shaded in blue to indicate their behavior differs from the standard Eclipse behavior.

Table 1 Carbide Build Configuration items

Build Configuration Naming

Item	Explanation
Active Configuration	The Active Configuration drop down list allows you to select a configuration that is currently available for the selected project. The entries in the related sub-panes will change according to the selected configuration. The Configuration name consists of a target name and an SDK identifier in brackets.
Manage...	Click the Manage... button to add a new SDK/Configuration or remove an existing configuration.

When the Carbide.c++ IDE creates an build configuration it uses a standard naming convention to make it easy to identify. For example, HelloCarbide S60 5.0 Emulator Debug is a typical configuration name. The default name follows the form of:

Other references

Supported Target Types

Carbide.c++ supports a variety of build targets based upon the SDKs and which version of the Carbide tools used by the project. The table below identifies which build targets are possible for a specific SDK.

NOTE Check the SDK Preferences page to see if an SDK you have installed and whether its build configurations are supported.

Table 1. Supported target types for all versions of Carbide.c++

Related tasks

Supported Target Types

Target Types	Platform Security -(S60 3.1, S60 3.0, UIQ 3.0)
GCCE, ARMV5, ARMV5_ABIV2	WINSCW - (EKA2)
APP (DLL)
DLL	Yes	Yes
EXE (console)	Yes	Yes
EXE (OS 9.1 GUI)	Yes	Yes
Polymorphic DLL	Yes	Yes
STDLIB	Yes	Yes

NOTE Check the SDK Preferences page to see if an SDK you have installed and whether its build configurations are supported.

Table 1. Supported target types for all versions of Carbide.c++

Related tasks

Carbide.c++ Projects

Target Types	Platform Security +(S60 3.2, S60 5.0)
RAPTOR, GCCE, ARMV5, ARMV5_ABIV2	WINSCW + (EKA2)
APP (DLL)
DLL	Yes	Yes
EXE (console)	Yes	Yes
EXE (OS 9.1 GUI)	Yes	Yes
Polymorphic DLL	Yes	Yes
STDLIB	Yes	Yes

Carbide.c++ can import .inf files to create projects. Once imported, those files are forgotten and all changes made to a Carbide.c++ project, like adding files or libraries, are handled by the IDE itself either using the File > New menu item, File > Import, or the Project Properties window.

Related tasks

Carbide.c++ Projects

Carbide.c++ can import .INF files to create projects. Once imported, those files are forgotten and all changes made to a Carbide.c++ project, like adding files or libraries, are handled by the IDE itself either using the File > New, File > Import, or the Properties for project window.

Related tasks

Common Debugging Actions

This section explains how to perform common debugging actions within the Debug perspective to correct source-code errors, control program execution, and observe memory behavior:

The plug-ins simplify Symbian OS development by removing the need to use command line build tools, and provide a graphical interface to Symbian OS specific file formats, such as AIF and MBM.

The plug-ins provide a new perspective, called the Carbide.c++ Perspective, on +

The plug-ins provide a new perspective, called the Carbide.c++ Perspective, on the Eclipse workbench. This perspective enhances the standard CDT C/C++ perspective by allowing you to select easily the SDKs and build target types that you want to use for each project.

- +

Context Menus

A context menu provides a shortcut to frequently used menu commands. The available menu commands change, based on the context of the selected item. For example, the Breakpoints view uses commands that differ from the Editor view.

TIP Experiment using the context menu in various views to discover additional capabilities.

Using Context Menus

Use context menus to apply context-specific commands to selected items.

@@ -39,7 +39,7 @@

Menus

- + diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/cvs.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/cvs.htm Wed Feb 10 15:19:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/cvs.htm Thu Feb 11 15:08:43 2010 -0600 @@ -1,19 +1,19 @@ - - - - - - -Concurrent Versions System (CVS) - - - -

Concurrent Versions System (CVS)

Carbide.c++ supports the Concurrent Versions System (CVS) for immediate version control support. Other revision systems are also supported but require the downloading of an Eclipse plug-in to add that feature to Carbide. Visit the eclipse.org or eclipse-plugins.2y.net sites to locate the plug-ins you need.

For more informaton on using CVS within Carbide, see the Workbench User Guide > Concepts > Team programming with CVS.

- - -

- - + + + + + + +Concurrent Versions System (CVS) + + + +

Concurrent Versions System (CVS)

For more informaton on using CVS within Carbide, see the Workbench User Guide > Concepts > Team programming with CVS.

+ + +

+ + diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/emulators.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/emulators.htm Wed Feb 10 15:19:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/emulators.htm Thu Feb 11 15:08:43 2010 -0600 @@ -1,37 +1,37 @@ - - - - - - -Emulation Debugging - - - -

Emulation Debugging

Symbian SDKs include an emulator that runs Symbian OS on a - Microsoft Windows host computer. The emulator provides the full range of Symbian OS - functionality, letting you do most development tasks on a single desktop computer. The - emulator and the software you build for it with the Carbide.c++ software run natively on the Intel x86 family of processors.

In many cases, you can build and debug a complete application using the emulator, then test the application on the actual device. There are cases however, where you cannot use - the emulator, such as when developing device drivers that access hardware on a device.
- For more information about the emulator, please see the documentation that came with - your SDK under: Developer Library>Tools and Utilities>Emulator.

You will find an emulator to use with Carbide.c++ in:

-
C:\Symbian\<version>\<sdk>\Epoc32\release\winscw\udeb
-

where Symbian is the path containing the subdirectories and version number of the Symbian OS SDK.

NOTE The first time you launch an emulator it may take some time to appear. Remember that it is implementing the operating system on the target device and that some setup time is required.

Related tasks

- - -

- - + + + + + + +Emulation Debugging + + + +

Emulation Debugging

Symbian SDKs include an emulator that runs Symbian OS on a + Microsoft Windows host computer. The emulator provides the full range of Symbian OS + functionality, letting you do most development tasks on a single desktop computer. The + emulator and the software you build for it with the Carbide.c++ software run natively on the Intel x86 family of processors.

In many cases, you can build and debug a complete application using the emulator, then test the application on the actual device. There are cases however, where you cannot use + the emulator, such as when developing device drivers that access hardware on a device.

For more information about the emulator, please see the documentation that came with + your SDK under: Developer Library > Tools and Utilities > Emulator.

You will find an emulator to use with Carbide.c++ in:

+
C:\Symbian\<version>\<sdk>\Epoc32\release\winscw\udeb
+

where Symbian is the path containing the subdirectories and version number of the Symbian OS SDK.

NOTE The first time you launch an emulator it may take some time to appear. Remember that it is implementing the operating system on the target device and that some setup time is required.

Related tasks

+ + +

+ + diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/ext_build_support.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/ext_build_support.htm Wed Feb 10 15:19:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/ext_build_support.htm Thu Feb 11 15:08:43 2010 -0600 @@ -1,50 +1,50 @@ - - - - - - -External Builds Support - - - -

External Builds Support

The IDE will perform the following tasks on external makefiles:

Build
Debug
File Management in Project Manager window
Source Browsing
Error Lookup

The IDE can build an external makefile and debug its output. A linker plugin will enable the IDE to manage a command line and targets associated with a makefile. The command line is executed when a build step is initiated. The linker plugin will also supply the executable to use for debugging.

The linker plugin will provide a preference panel named External Build that is used to configure a target. The preference panel provides text fields for you to configure the command line for the target (which will enable building), specify the working directory and the output file used to launch a debugging session, and the debug platform.

The linker plugin is generic so that it can be used regardless of the target CPU and OS. The list of available debugger preference panels will be updated by the IDE when you select the debug platform.

The External Build Target preference panel will collect the following information:

Build command line to be executed in the build step

-
The command line will be sent to the OS shell and will contain all parameters and/or switches that are necessary for proper building of the make file.
-

Build directory in which command line will be executed.
Output file name - Executable to be launched in the debug step. The file will be relative to the output directory specified in the Target Settings preference panel.
Debug platform - The debugger platform represents the combination of OS and CPU that your build is targeting. “Unspecified/Remote debugging” is the default, which indicates you have not specified a debug platform. In most cases, not specifying a platform will result in not being able to debug. However, some platforms may allow debugging if no additional debugger preference panel is used. If only one platform entry exists with the “Unspecified” option, then it will become the default entry.

-
After the IDE converts the makefile into a Carbide project, source files can be added in the project manager window. Files that appear in the project manager will be parsed by the language parser and will supply Source Browsing information, such as code completion.
-
When a build step is initiated, the linker plugin will gather output after the command line begins executing. Output is directed to the IDE and displayed in a read-only Build Output Window. A build output window is displayed for each target. The build output window can be displayed manually by selecting the menu command View > Build Output (Windows) or Window > Build Output (Linux/Solaris/Mac). This command is enabled for targets that use the external build linker.
-
If multiple build steps are performed on the same target, the output from each build step will be appended to the build output window. Each block of output will be separated by “----Build started----” and “----Done----” tags.
-
The build output window will allow users to navigate directly to the location of a compilation error. Double-click a line that contains an error message or press Enter when the cursor is in the line. If the IDE determines that a valid error message exists on the selected line, the source file is opened to the line on which the error occurred.
-
Click the right mouse button in the build output window to display a context menu.
-

The Copy command will copy selected text to the clipboard. If no text is selected then the line that contains the cursor will be copied.
The Clear All command will clear contents of output window.
The Go To Error command will navigate to the error location. This is identical to double-clicking.

- - - - + + + + + + +External Builds Support + + + +

External Builds Support

The IDE will perform the following tasks on external makefiles:

Build
Debug
File Management in Project Manager window
Source Browsing
Error Lookup

The IDE can build an external makefile and debug its output. A linker plugin enables the IDE to manage a command line and targets associated with a makefile. The command line is executed when a build step is initiated. The linker plugin will also supply the executable to use for debugging.

The linker plugin provides a preference panel named External Build that is used to configure a target. The preference panel provides text fields for you to configure the command line for the target (which will enable building), specify the working directory and the output file used to launch a debugging session, and the debug platform.

The External Build Target preference panel collects the following information:

Build command line to be executed in the build step

+
The command line will be sent to the OS shell and will contain all parameters and/or switches that are necessary for proper building of the make file.
+

Build directory in which command line will be executed.
Output file name - Executable to be launched in the debug step. The file will be relative to the output directory specified in the Target Settings preference panel.
Debug platform - The debugger platform represents the combination of OS and CPU that your build is targeting. “Unspecified/Remote debugging” is the default, which indicates you have not specified a debug platform. In most cases, not specifying a platform will result in not being able to debug. However, some platforms may allow debugging if no additional debugger preference panel is used. If only one platform entry exists with the “Unspecified” option, then it will become the default entry.

+
After the IDE converts the makefile into a Carbide project, source files can be added in the project manager window. Files that appear in the project manager will be parsed by the language parser and will supply Source Browsing information, such as code completion.
+
When a build step is initiated, the linker plugin will gather output after the command line begins executing. Output is directed to the IDE and displayed in a read-only Build Output Window. A build output window is displayed for each target. The build output window can be displayed manually by selecting the menu command View > Build Output (Windows) or Window > Build Output (Linux/Solaris/Mac). This command is enabled for targets that use the external build linker.
+
If multiple build steps are performed on the same target, the output from each build step will be appended to the build output window. Each block of output will be separated by “----Build started----” and “----Done----” tags.
+
The build output window allows users to navigate directly to the location of a compilation error. Double-click a line that contains an error message or press Enter when the cursor is in the line. If the IDE determines that a valid error message exists on the selected line, the source file is opened to the line on which the error occurred.
+
Click the right mouse button in the build output window to display a context menu.
+

The Copy command copies selected text to the clipboard. If no text is selected then the line that contains the cursor will be copied.
The Clear All command clears the contents of output window.
The Go To Error command navigates to the error location. This is identical to double-clicking.

+ + + + diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/images/breakpt_popup_menu.png Binary file core/com.nokia.carbide.cpp.doc.user/html/concepts/images/breakpt_popup_menu.png has changed diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/images/build_configs.png Binary file core/com.nokia.carbide.cpp.doc.user/html/concepts/images/build_configs.png has changed diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/images/view_registers.png Binary file core/com.nokia.carbide.cpp.doc.user/html/concepts/images/view_registers.png has changed diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/images/workbench.png Binary file core/com.nokia.carbide.cpp.doc.user/html/concepts/images/workbench.png has changed diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/mmpfiles.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/mmpfiles.htm Wed Feb 10 15:19:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/mmpfiles.htm Thu Feb 11 15:08:43 2010 -0600 @@ -1,22 +1,22 @@ - - - - - - -MMP Files - - - -

MMP Files

Symbian projects are defined by an .mmp file which specifies the essential elements of the project. All details of the project lifecycle are handled by the IDE. There is no editable makefile the user can edit to modify the build behavior of the project.

Related reference

MMP Editor

- - -

- + + + + + + +MMP Files + + + +

MMP Files

Symbian projects are defined by an .MMP file which specifies the essential elements of the project. All details of the project lifecycle are handled by the IDE. There is no editable makefile the user can edit to modify the build behavior of the project.

Related reference

MMP Editor

+ + +

+ \ No newline at end of file diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/precompiled_headers.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/precompiled_headers.htm Wed Feb 10 15:19:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/precompiled_headers.htm Thu Feb 11 15:08:43 2010 -0600 @@ -1,37 +1,36 @@ - - - - - - -Precompiled Headers - - - -

Precompiled Headers

Precompiled header support is available for Symbian OS projects that use the Nokia x86 -compiler. Precompiled header files use the .pch++ extension and are only supported by emulator targets.

By default, the x86 compiler compiles the .pch++ file before compiling any .cpp files in a project.

A precompiled header file (.pch++) outputs to a new identically named file with the .mch extension. For example, HelloWorld.pch++ outputs as HelloWorld.mch. C++ source files must use the .pch++ extension.

Listing 1 shows an example of a precompiled header source file called -pch_test.pch++.

Listing 1 .pch Precompiled Header example

#include <e32def.h>
- #pragma precompile_target "pch_test.mch"
-
- #define FOO 1
- #define LATIDA 345

typedef struct foo
- {
- int i, j, k, l, m;
- char foobar[256];
-} foo;

The resultant output file, pch_test.mch can be included in other source or prefix files as:

#include pch_test.mch

- - - + + + + + + +Precompiled Headers + + + +

Precompiled Headers

Precompiled header support is available for Symbian OS projects that use the Nokia x86 +compiler. Precompiled header files use the .pch++ extension and are only supported by emulator targets.

By default, the x86 compiler compiles the .pch++ file before compiling any .cpp files in a project.

Listing 1 shows an example of a precompiled header source file called +pch_test.pch++.

Listing 1 .pch Precompiled Header example

#include <e32def.h>
+ #pragma precompile_target "pch_test.mch"
+
+ #define FOO 1
+ #define LATIDA 345

typedef struct foo
+ {
+ int i, j, k, l, m;
+ char foobar[256];
+} foo;

The resultant output file, pch_test.mch can be included in other source or prefix files as:

#include pch_test.mch

+ + + \ No newline at end of file diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/registers.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/registers.htm Wed Feb 10 15:19:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/registers.htm Thu Feb 11 15:08:43 2010 -0600 @@ -1,31 +1,35 @@ - - - - - - -Registers - - - -

Registers

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 Registers view. When debugging projects on a device, only the target device registers are visible.

In most cases, the contents of all the registers can be modified. However, when debugging applications on a target device with Application TRK, you cannot change the LR and SP registers.

The types of registers include:

general—the register contents of the central processing unit (CPU) of the host computer
FPU—register contents of the floating-point unit (FPU) of the host computer
host-specific—additional register contents for registers specific to the host (for example ARM registers)

NOTE When opening the Registers view, the list of available registers will vary depending upon the target devices being debugged.

Other references

- - - - + + + + + + +Registers + + + +

Registers

In most cases, the contents of all the registers can be modified. However, when debugging applications on a target device with Application TRK, you cannot change the LR and SP registers.

Figure 1. Registers view with possible register types

The types of registers can include:

general — the register contents of the central processing unit (CPU) of the host computer
FPU — register contents of the floating-point unit (FPU) of the host computer
MMX — 64-bit MultiMedia eXtension (MMX) registers
SSE — 128-bit Streaming SIMD Extension registers
host-specific—additional register contents for registers specific to the host (for example ARM registers)

NOTE When opening the Registers view, the list of available registers will vary depending upon the target devices being debugged.

Other references

+ + + + diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/symbol_hints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/symbol_hints.htm Wed Feb 10 15:19:41 2010 -0600 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,34 +0,0 @@ - - - - - - -Symbol Hint - - - -

Symbol Hint

The symbol hint shows information about variable values. This information appears automatically while the debugger is active.
-Select the Show variable values in the source code option in the Display Settings preference panel to use the symbol hint.

Toggling the Symbol Hint

Turn on the symbol hint to view information about program variables in source views.

To toggle the symbol hint

Click Edit > Preferences.

The IDE Preferences window appears.

Select Display Settings in the IDE Preference Panels list.
Check or clear the Show variable values in source code checkbox.

Check the checkbox to use the symbol hint. Clear the checkbox to stop using the symbol hint.

Click Apply or Save to confirm your changes to the preference panel.
Close the IDE Preferences window.

Using the Symbol Hint

During a debugging session, use the symbol hint to view information about program variables.

To use the symbol hint, rest the cursor over a variable in a source view. After a brief pause, the symbol hint appears and shows the current variable value.

- - - - \ No newline at end of file diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/watchpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/watchpoints.htm Wed Feb 10 15:19:41 2010 -0600 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,117 +0,0 @@ - - - - - - -Watchpoints Overview - - - -

Watchpoints Overview

Use watchpoints (sometimes referred to as access breakpoints) to halt program execution when a specific global location is accessed. After you set a watchpoint at a key point in memory, you can halt program execution whenever that point in memory is written to or read from. You can then examine the call chain, check register and variable values, and step through your code. You can also change values and alter the flow of normal program execution.

A watchpoint must be both enabled and resolved during a debug session in order to halt program execution. The Breakpoints view indicates the status of any watchpoint using a set of common icons and checkmark status badge. These include:

An enabled watchpoint has a non-gray icon () indicating that program execution halts when encountered.
A disabled watchpoint displays a gray icon () indicating that program execution will not stop when encountered.
A resolved watchpoint has a small checkmark badge ( ) indicating that the debugger has located it in memory during program launch. When resolved, the debugger can halt program execution if the watchpoint is encountered.

In effect, a watchpoint that is enabled by the user and resolved by the debugger during program launch can halt program execution. The table below shows the various states that cause the debugger to halt program execution:

Table 1 Watchpoint—stop execution chart

- - - - - - - - - - - - - - - - -

Watchpoint	Resolved	Unresolved
Enabled	Stops execution	No
Disabled	No	No

In addition, you can use these types of watchpoints:

regular watchpoints—halt program execution
conditional watchpoints—halt program execution after meeting a condition that you specify (same as for breakpoints)

A watchpoint is equivalent to a memory breakpoint.

Unlike a breakpoint, a watchpoint can detect when any part of your program affects memory. For example, if a write or write/read watchpoint is set, when the program writes a new value to the address or area of memory that has the watchpoint, the debugger suspends program execution.

NOTE You cannot set a watchpoint on a local variable, because the debugger cannot detect watchpoints for variables stored on the stack or in registers.

Table 2 Watchpoint—types and states

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Type	State	Explanation
Write	enabled	The watchpoint is activated for write access operations on the specific memory location and if resolved, will halt program execution on a write operation at the watchpoint. -
Write	disabled	Watchpoint is disabled for the source line, debugger does not halt program execution on a write operation. -
Read	enabled	The watchpoint is activated for read access operations on the specific memory location and if resolved, will halt program execution on a read operation at the watchpoint. -
Read	disabled	Watchpoint is disabled for the source line, debugger does not halt program execution on a read operation. -
Write/Read	enabled	The watchpoint is activated for both read and write access operations on the specific memory location and if resolved, will halt program execution on any read or write operation at the watchpoint. -
Write/Read	disabled	Watchpoint is disabled for the source line, debugger does not halt program execution on a read or write operation. -

A project can have a different maximum number of watchpoints, depending on the build target. The IDE generally limits the acceptable range for watchpoints to memory that it can write-protect. This range also depends on the host and on the application.

All set watchpoints appear in the Breakpoints view list.

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

- - - - diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_programs.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_programs.htm Wed Feb 10 15:19:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_programs.htm Thu Feb 11 15:08:43 2010 -0600 @@ -1,35 +1,35 @@ - - - - - - -Controlling Program Execution - - - -

Controlling Program Execution

This section explains how to use breakpoints, breakpoint actions, and watchpoints to manipulate execution of your program in the Carbide™ IDE:

Breakpoints—halt program execution on a line of source code that you specify. You can set a breakpoint that always halts program execution, or you can set a breakpoint that halts program execution if a condition that you specify is true.
Breakpoint actions—perform a task during program execution on a line of source - code that you specify. Breakpoint actions can play sounds, run scripts, log data, and perform other operations.
Watchpoints—halt program execution after a location in memory changes - value

After you set these items in your source code, you start a debugging session to use them. As program execution arrives at each of these items, the debugger can halt execution, perform a task, or update data.

Related concepts

Related references

Breakpoints View
Breakpoint Actions Preferences

- - - - + + + + + + +Controlling Program Execution + + + +

Controlling Program Execution

This section explains how to use breakpoints, breakpoint actions, and watchpoints to manipulate execution of your program in the Carbide™ IDE:

Breakpoints—halt program execution on a line of source code that you specify. You can set a breakpoint that always halts program execution, or you can set a breakpoint that halts program execution if a condition that you specify is true.
Breakpoint actions—perform a task during program execution on a line of source + code that you specify. Breakpoint actions can play sounds, run scripts, log data, and perform other operations.
Watchpoints—halt program execution after a location in memory changes + value

Related concepts

Related references

Breakpoints View
Breakpoint Actions Preferences

+ + + + diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/reference/MBMEditor.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MBMEditor.html Wed Feb 10 15:19:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/MBMEditor.html Thu Feb 11 15:08:43 2010 -0600 @@ -1,112 +1,110 @@ - -MBM Editor - - - -

MBM Editor

- -

- The MBM Editor allows you to specify the bitmaps that - should be included in a Symbian OS multi-bitmap (MBM) file. Use of MBM files for general purpose graphics is restricted to using .bmp files and works for versions 2.x and later releases of the Symbian OS SDKs. For more - information, see MBM File and Creating a MBM File. -

- The MBM Editor is shown when an MBM file is - opened for editing:

Figure 1 - MBM Editor

Table 1. MBM Editor —Items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Target File	Specifies the EPOCROOT relative path for the compiled images. Click the Default button to set the target file based on the SDK and project name.
Header File	Shows the generated header file. Select the Header option in the Header Generation group to create a default .mbg file. The path cannot be edited in this field.
Header Generation	Options include: - - No header - If selected, no .mbg header will be generated. - Header - If selected, a .mbg header will be generated. -
Up	Select an image in the list and click Up to move the selection one position up in the list.
Down	Select an image in the list and click Down to move the selection one position down in the list.
Pair Image and Mask	Select two adjacent unpaired BMP image entries in the list and click this button to combine the images together into image/mask pairs.
Split Image and Mask	Select a paired BMP image in the list and click this button to split the image into image and mask entries.
Swap Image and Mask	Select a paired BMP image in the list and click this button to swap the image and mask files and format information in paired image entries.
Add From Project	Click this button to open an Add Images from Project dialog to reference available images in the project.
Add From Filesystem	Click this button to open an Add Images From Filesystem dialog to locate and reference existing images in the filesystem or copy images to the project.
Remove	Select an image and click Remove to remove image entry from the list. This does not delete file from directory.
Color depth	Select the bit depth used to encode the image at build time.
Mask depth	Select the bit depth used to encode the mask at build time. Options include: - - n/a - Do not apply mask depth to images - 1 - A 1-bit mask treats pixels as "on/off" bits, where black is opaque and white is transparent. - 8 - An 8-bit mask is treated as alpha values, where black is transparent and white is opaque. -
Color format	Select Color to encode the image(s) as color or select Grayscale to encode the image(s) as grayscale.
Set from image	Click this button to auto-detect the image depth, mask depth, and color/grayscale setting from the image contents.
Preview	A preview of the image as it will appear at runtime.

Related concepts

- -

MBM File

Related tasks

Creating an MBM File

- - - - + +MBM Editor + + + +

MBM Editor

+ +

+ The MBM Editor allows you to specify the bitmaps that + should be included in a Symbian OS multi-bitmap (MBM) file. Use of MBM files for general purpose graphics is restricted to using .bmp files and works for versions 2.x and later releases of the Symbian OS SDKs. For more + information, see MBM File and Creating a MBM File.

+ The MBM Editor is shown when an MBM file is + opened for editing:

Figure 1 - MBM Editor

Table 1. MBM Editor —Items

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
Target File	Specifies the EPOCROOT relative path for the compiled images. Click the Default button to set the target file based on the SDK and project name.
Header File	Shows the generated header file. Select the Header option in the Header Generation group to create a default .mbg file. The path cannot be edited in this field.
Header Generation	Options include: + + No header - If selected, no .mbg header will be generated. + Header - If selected, a .mbg header will be generated. +
Up	Select an image in the list and click Up to move the selection one position up in the list.
Down	Select an image in the list and click Down to move the selection one position down in the list.
Pair Image and Mask	Select two adjacent unpaired BMP image entries in the list and click this button to combine the images together into image/mask pairs.
Split Image and Mask	Select a paired BMP image in the list and click this button to split the image into image and mask entries.
Swap Image and Mask	Select a paired BMP image in the list and click this button to swap the image and mask files and format information in paired image entries.
Add From Project	Click this button to open an Add Images from Project dialog to reference available images in the project.
Add From Filesystem	Click this button to open an Add Images From Filesystem dialog to locate and reference existing images in the filesystem or copy images to the project.
Remove	Select an image and click Remove to remove image entry from the list. This does not delete file from directory.
Color depth	Select the bit depth used to encode the image at build time.
Mask depth	Select the bit depth used to encode the mask at build time. Options include: + + n/a - Do not apply mask depth to images + 1 - A 1-bit mask treats pixels as "on/off" bits, where black is opaque and white is transparent. + 8 - An 8-bit mask is treated as alpha values, where black is transparent and white is opaque. +
Color format	Select Color to encode the image(s) as color or select Grayscale to encode the image(s) as grayscale.
Set from image	Click this button to auto-detect the image depth, mask depth, and color/grayscale setting from the image contents.
Preview	A preview of the image as it will appear at runtime.

Related concepts

+ +

MBM File

Related tasks

Creating an MBM File

+ + + + \ No newline at end of file diff -r bbee10bb6733 -r 47d3ca29d054 core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_libraries.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_libraries.html Wed Feb 10 15:19:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_libraries.html Thu Feb 11 15:08:43 2010 -0600 @@ -1,51 +1,51 @@ - - -MMP Editor Libraries - - - -

MMP Editor Libraries Window

- -

- The MMP editor libraries window lists the libraries used by the currently selected build configuration in the selected project. The MMP editor libraries window is shown in Figure 1. Click on a library group to expand the list of libraries and show the related control buttons. You can add, remove or edit the list of libraries for each group. You can also move libraries up or down in the list.

Figure 1 - MMP Editor Libraries window

- - - - - - - - - - - - - - -

Name	Function
- - Libraries	- - Specify import libraries to be included in all builds.
- - Static libraries	- - Specify additional static libraries to be used in all builds.
Debug libraries	Specify additional libraries to be used for debug builds only.
Win32 libraries	Specify additional libraries for Win32 builds only.
ASSP libraries	Specify libraries for ASSP builds. If you are not linking to the Symbian OS kernel you can ignore this section.

Related references

- - - - - - + + +MMP Editor Libraries + + + +

MMP Editor > Libraries

+ +

+ The MMP editor libraries window lists the libraries used by the currently selected build configuration in the selected project. The MMP editor libraries window is shown in Figure 1. Click on a library group to expand the list of libraries and show the related control buttons. You can add, remove or edit the list of libraries for each group. You can also move libraries up or down in the list.

Figure 1 - MMP Editor Libraries window

+ + + + + + + + + + + + + + +

Name	Function
+ + Libraries	+ + Specify import libraries to be included in all builds.
+ + Static libraries	+ + Specify additional static libraries to be used in all builds.
Debug libraries	Specify additional libraries to be used for debug builds only.
Win32 libraries	Specify additional libraries for Win32 builds only.
ASSP libraries	Specify libraries for ASSP builds. If you are not linking to the Symbian OS kernel you can ignore this section.

Related references

+ + + + + + \ No newline at end of file