Adding and Removing Expressions

An expression 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 Expressions 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 Enable and Disable options in the context menu to control which expressions are automatically evaluated.

You add expressions in the Add Watch Expression dialog using a variety of views, including Expressions, Variables, and editor views. Right-click in the view and select the Add Watch Expression... command from the context menu.

are all valid expressions that the Expressions view can monitor and display. However, an expression cannot call a function or execute code. The following example will not work:

Removing Expressions

Right-click the expression in the Expressions view and select the Remove menu option. This removes the selected expression from the Expression list.

Other references

Adding and Removing Expressions

are all valid expressions that the Expressions view can monitor and display. However, an expression cannot call a function or execute code. The following example will not work:

Removing Expressions

Right-click the expression in the Expressions view and select the Remove menu option. This removes the selected expression from the Expression list.

Other references

Editing Expressions

Use the Edit Watch Expression dialog to change a previously defined expression. Right-click in the Expressions view and select the Edit Watch Expression... command from the context menu. When editing an expression, the same rules used to create it apply. Mainly, the edited expression must be a valid C/C++ expression that evaluates to a value and does not call a function nor execute code.

Use the Enable control to set whether this expression should be automatically evaluated during a debug session.

Other references

Editing Expressions

Use the Enable control to set whether this expression should be automatically evaluated during a debug session.

are all valid expressions that the Expressions view can monitor and display. However, an expression cannot call a function or execute code. The following example will not work:

Other references

To change the settings only for a particular file, right-click the file from the Project Explorer, C/C++ Project, or Symbian Project Navigator views, and choose Properties from the context menu. The Properties for <file_name> window shows the settings that are @@ -30,7 +32,7 @@

You can set the SDKs and Build Configurations in this page. The available SDKs shown are determined by the settings in the SDK Preferences page.

@@ -55,7 +55,7 @@

Working with SDKs

SDK Preferences

- + diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/ROM_build_settings.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/ROM_build_settings.html Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/ROM_build_settings.html Fri Feb 12 14:45:16 2010 -0600 @@ -1,42 +1,42 @@ - -ROM Builder pane - - - - -

ROM Builder pane

Use the ROM Builder pane to specify commands and a working directory for building a GUI ROM Image. The tool used to build GUI ROM images is called buildrom and can typically be found in your SDK path, for example in the \Symbian\9.1\S60_3rd\Epoc32\tools directory. The tool used to build text shell images is called ROM. The ROM image generated from the ROM building process specifies a base address for the image to run at. This might be an address in RAM or ROM. The image must be downloaded to the device at this address.

Building a ROM requires that the following are available, or have been successfully created:

Symbian OS components making up a set of releasables
a Bootstrap binary image
a text file specifying how the ROM image is to be built.

Rom build assembles executable and data files into a ROM image.

Executables are pre-processed, relocated, and have their imports and exports bound for a ROM image based at some given virtual address. The files, base address of the ROM, and various other parameters are specified by means of the obey file. This is a file of type .oby and is a text file containing statements that specify how the ROM image is to be built. A .oby file can include other files in the same way that files containing C++ source can #include other C++ files. By convention, the included files have the .iby file type. This structure allows flexibility in the way that ROM images are defined.

NOTE The ROM image will be rebuilt for any target whenever a change to the project occurs; except for WINSCW targets.

Figure 1. ROM Builder pane

Table 1. ROM Build Settings —items

- - - - - - - - - - -

Name	Function
ROM Build Command Line	Enter commands to build the GUI ROM Image. For example, the following sample command is used for building a techview - rom image for a H4 reference board. - buildrom -D_FULL_DEBUG -DRVCT -DSTOP_MODE_DEBUGGING -D_EABI=ARMV5 h4hrp techview -oh4.img
Working Directory	Specify the working directory for building the ROM Image. Typically, the working directory is the folder where you need to have your rom image built. -Note that your sdk and working directory should be on -the same drive, otherwise some of the rombuild scripts will fail. -

Name

Function

ROM Build Command Line

Enter commands to build the GUI ROM Image. For example, the following sample command is used for building a techview - rom image for a H4 reference board.

buildrom -D_FULL_DEBUG -DRVCT -DSTOP_MODE_DEBUGGING -D_EABI=ARMV5 h4hrp techview -oh4.img

Working Directory

Specify the working directory for building the ROM Image. Typically, the working directory is the folder where you need to have your rom image built. -Note that your sdk and working directory should be on -the same drive, otherwise some of the rombuild scripts will fail.

- - - - + +ROM Builder pane + + + + +

ROM Builder pane

Building a ROM requires that the following are available, or have been successfully created:

Symbian OS components making up a set of releasables
a Bootstrap binary image
a text file specifying how the ROM image is to be built.

Rom build assembles executable and data files into a ROM image.

NOTE The ROM image will be rebuilt for any target whenever a change to the project occurs; except for WINSCW targets.

Figure 1. ROM Builder pane

Table 1. ROM Build Settings —items

+ + + + + + + + + + +

Name	Function
ROM Build Command Line	Enter commands to build the GUI ROM Image. For example, the following sample command is used for building a techview + rom image for a H4 reference board. + buildrom -D_FULL_DEBUG -DRVCT -DSTOP_MODE_DEBUGGING -D_EABI=ARMV5 h4hrp techview -oh4.img
Working Directory	Specify the working directory for building the ROM Image. Typically, the working directory is the folder where you need to have your rom image built. +Note that your sdk and working directory should be on +the same drive, otherwise some of the rombuild scripts will fail. +

Name

Function

ROM Build Command Line

Enter commands to build the GUI ROM Image. For example, the following sample command is used for building a techview + rom image for a H4 reference board.

buildrom -D_FULL_DEBUG -DRVCT -DSTOP_MODE_DEBUGGING -D_EABI=ARMV5 h4hrp techview -oh4.img

Working Directory

Specify the working directory for building the ROM Image. Typically, the working directory is the folder where you need to have your rom image built. +Note that your sdk and working directory should be on +the same drive, otherwise some of the rombuild scripts will fail.

+ + + + \ No newline at end of file diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/SDKPreferences.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/SDKPreferences.html Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/SDKPreferences.html Fri Feb 12 14:45:16 2010 -0600 @@ -24,8 +24,8 @@

NOTE This panel serves as a devices.xml file editor. The devices.xml file stores information about the installed SDKs used for Symbian OS development.

SDK preferences panel

Figure 1. SDK Preferences preference panel

SDK preferences panel

Figure 1. SDK Preferences preference panel

@@ -38,14 +38,14 @@

Click on a SDK name to see its EPOCROOT location and build configuration status in the SDK Information area.

+ + + + - - - - @@ -59,16 +59,14 @@

NOTE Carbide.c++ scans for available SDKs each time it is started.

Remove SDK	Click to remove the selected SDK from the Available Symbian OS SDK's list.
Add New SDK	Click to add an SDK to the Available Symbian OS SDKs list.
Remove SDK	Click to remove the selected SDK from the Available Symbian OS SDK's list.
SDK Properties	Click to view and edit the properties of the currently selected SDK in the Available Symbian OS SDKs list.

Legacy SDK's

For legacy SDK's the OS/SDK version is determined from the SDK id. Some older SDK's have two verisons, one where the emulator was built with MSVC and the other built with CodeWarrior. We support those SDK's built with CodeWarrior. The id of that SDK is S60_2nd_FP2_CW.

Related tasks

- + diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/images/menu_mem_rendering_options.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/menu_mem_rendering_options.png has changed diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_expressions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_expressions.png has changed diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_debug_overview.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_debug_overview.png has changed diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm Fri Feb 12 14:45:16 2010 -0600 @@ -1,21 +1,21 @@ - - - - - - -Reference - - - -

Reference

This section provides reference information on the Carbide IDE including:

Debugger settings — shows the Carbide debugger setting panels used to control debug sessions
Expression views — shows how to work with expressions in a debugging session
Variable views — shows how to work with variables in a debugging session

- - - - + + + + + + +Reference + + + +

Reference

This section provides reference information on the Carbide IDE including:

Debugger settings — shows the Carbide debugger setting panels used to control debug sessions
Expression views — shows how to work with expressions in a debugging session
Variable views — shows how to work with variables in a debugging session

+ + + + diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/view_expressions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_expressions.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_expressions.htm Fri Feb 12 14:45:16 2010 -0600 @@ -9,19 +9,19 @@

Expressions View

The Expressions view helps you monitor and manipulate these items:

Use the Expressions view to monitor and manipulate:

global and local variables
structure members
array elements

The Expressions view displays these columns:

The Expressions view displays these panes:

Expression column—Lists expressions and expression hierarchies. Click the hierarchical controls to expand or collapse the expression view.
Value column—Shows the current value of each corresponding expression. Double-click a value to change it.
Expression pane (left) — Lists expressions and expression hierarchies. Click the hierarchical controls to expand or collapse the expression view.
Value pane (right) — Shows the current value of each corresponding expression. Double-click a value to change it.

Figure 1 shows the Expressions view. Table 1 explains items in view.

Figure 1 shows the Expressions view.

Figure 1 - Expressions view

Table 1. Expressions view —items

@@ -46,6 +46,11 @@ + + + + + @@ -55,15 +60,20 @@ + + + + +

Collapses all expanded expressions into the top level.
New Watch Expression	Click to open the Add Watch Expression dialog.
Remove Selected Expression	Click to remove all currently selected expressions from the expressions list.	Click to remove all expressions from the expressions list.
Refresh	Click to refresh view display.

Opening the Expressions View

Use the Expressions view to inspect frequently used variables as their values change during a debugging session.

Opening an Expressions view

Select Window > Show View > Expressions
OR
Right-click a variable in the Variables or editor view and choose the Add Watchpoint command
Right-click a variable in the Variables or editor view and choose the Add Watchpoint (C/C++) menu item

An Expressions view appears in the current perspective.

@@ -72,7 +82,7 @@

Adding & Removing Expressions

Editing Expressions

- + diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/view_global_variables.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_global_variables.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_global_variables.htm Fri Feb 12 14:45:16 2010 -0600 @@ -1,53 +1,53 @@ - - - - - - -Global Variables Window - - - -

Global Variables Window

The Global Variables window shows all global and static variables for each process that you debug. You can open separate Global Variables windows for each process in the same build target. Use the window to observe changes in variable values as the program executes.

Figure 1 shows the Global Variables window. Table 1 explains the items in the window.

Figure 1 Global Variables window

Table 1 Global Variables window—items

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

Item	Explanation
File	Lists source files that declare global or static variables. Click a source file to view its static variables. Click Global Variables to view all global variables declared in the program.
Variables	Lists variables according to the file selected in the File pane. Double-click a variable to display it in a separate Variable window.

Opening the Global Variables Window

Use the Global Variables window to display global variables declared in a program or static variables declared in source files that comprise the program.

To open the Global Variables window, select View > Global Variables or Window > Global Variables Window.

Viewing Global Variables for Different Processes

You can open a separate Global Variables window for each process that the same parent application creates.

To open the Global Variables window for a particular process, follow these steps:

Click Project > Debug.

A debugging session starts.

In the Thread window toolbar, use the Process list box to specify the process that has the global variables that you want to examine.
Click View > Global Variables or Window > Global Variables Window.

Repeat these steps for each process that has global variables that you want to examine.

- - - + + + + + + +Global Variables Window + + + +

Global Variables Window

Figure 1 shows the Global Variables window.

Figure 1 Global Variables window

Table 1 Global Variables window—items

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

Item	Explanation
File	Lists source files that declare global or static variables. Click a source file to view its static variables. Click Global Variables to view all global variables declared in the program.
Variables	Lists variables according to the file selected in the File pane. Double-click a variable to display it in a separate Variable window.

Opening the Global Variables Window

Use the Global Variables window to display global variables declared in a program or static variables declared in source files that comprise the program.

To open the Global Variables window, select View > Global Variables or Window > Global Variables Window.

Viewing Global Variables for Different Processes

You can open a separate Global Variables window for each process that the same parent application creates.

To open the Global Variables window for a particular process, follow these steps:

Click Project > Debug.

A debugging session starts.

In the Thread window toolbar, use the Process list box to specify the process that has the global variables that you want to examine.
Click View > Global Variables or Window > Global Variables Window.

Repeat these steps for each process that has global variables that you want to examine.

+ + + \ No newline at end of file diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/view_memory_wnd.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_memory_wnd.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_memory_wnd.htm Fri Feb 12 14:45:16 2010 -0600 @@ -1,88 +1,93 @@ - - - - - - -Memory View - - - -

Memory View

Use the Memory view to inspect and change process memory. You can address memory using expressions such as:

0x0847d3c
(&y)+1024
*ptr
FNname + 1

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.

CAUTION Arbitrarily changing memory contents could degrade the stability of the IDE, another program, or the operating system itself. Understand the consequences of manipulating memory.

Figure 1 shows the Memory view. Table 1 explains the items in the view.

Figure 2 - Memory view showing a memory rendering in traditional format

Table 1 Memory view—items

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

Item	Icon	Explanation
New Memory View		Click to add a new Memory monitor view.
Pin Memory Monitor		Pin memory view.
Toggle Memory Monitors Pane		Toggles the current Memory monitors view between showing only a Memory Monitor pane and a Memory Monitor and Memory Rendering pane.
Toggle Split Pane		Alternately shows and hides the Memory Rendering pane.
Link Memory Monitor Panes		Enable to synchronize the current selection between the rendering of the same memory monitor .
Switch Memory Monitor		If different memory monitor views have been added, select from list of memory monitor views.
Add Memory Monitor / Add Rendering		Add a new memory address or variable to the Memory Monitors pane, or add a new rendering to the Memory Rendering pane.
Remove Memory Monitor / Remove Rendering		Remove the selected memory address or variable from the Memory Monitors pane, or remove the selected rendering from the Memory Rendering pane.
Remove All		Remove all memory monitors or renderings from the associated pane.

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).

Figure 2 - Rendering pane options

Related tasks

- - - - + + + + + + +Memory View + + + +

Memory View

Use the Memory view to inspect and change process memory. You can address memory using expressions such as:

0x0847d3c
(&y)+1024
*ptr
FNname + 1

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.

CAUTION Arbitrarily changing memory contents could degrade the stability of the IDE, another program, or the operating system itself. Understand the consequences of manipulating memory.

Figure 1 shows the Memory view.

Figure 2 - Memory view showing a memory rendering in traditional format

Table 1 Memory view—items

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

Item	Icon	Explanation
New Memory View		Click to add a new Memory monitor view.
Pin Memory Monitor		Pin memory view.
Refresh		Click to refresh the memory display.
Toggle Memory Monitors Pane		Toggles the current Memory monitors view between showing only a Memory Monitor pane and a Memory Monitor and Memory Rendering pane.
Toggle Split Pane		Alternately shows and hides the Memory Rendering pane.
Link Memory Monitor Panes		Enable to synchronize the current selection between the rendering of the same memory monitor .
Switch Memory Monitor		If different memory monitor views have been added, select from list of memory monitor views.
Add Memory Monitor / Add Rendering		Add a new memory address or variable to the Memory Monitors pane, or add a new rendering to the Memory Rendering pane.
Remove Memory Monitor / Remove Rendering		Remove the selected memory address or variable from the Memory Monitors pane, or remove the selected rendering from the Memory Rendering pane.
Remove All		Remove all memory monitors or renderings from the associated pane.

Figure 2 - Rendering pane options

Related tasks

+ + + + diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/view_mifdef_editor.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_mifdef_editor.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_mifdef_editor.htm Fri Feb 12 14:45:16 2010 -0600 @@ -1,108 +1,106 @@ - - -MIF Editor - - - - -

MBM/MIF Editor

- -

The MIF Editor allows you to create or edit the .mif files list of scalable icons (.svg) - included in a S60 v3.0 and later GUI projects as well as standard .bmp files. A .mif file is a MSX Interchange Format (MIF) file that should be built by the project. MIF files replace the functionality of AIF (and MBM) files.

NOTE This editor is only supported by the S60 3.0 and later SDKs.

NOTE For resources that are included after creating a project, you should ensure that the output location is set correctly by viewing the file properties. The output location is set to "{EPOCROOT}\epoc32\include" by default, so if an alternate location is required you can set this in the file properties.

The MIF Editor appears when a MIF file is - opened for editing. To open the editor double-click on a .mif file in the Symbian Project Navigator view (figure 1), or select a scalable icon makefile (for example, Icons_scalable_dc.mk), right-click and select the Add MBM/MIF Entry command.

Figure 1 - MIF File in Symbian Project Navigator

Figure 2 - MBM/MIF Editor

Table 1. MBM/MIF 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.

- - - - + + +MIF Editor + + + + +

MBM/MIF Editor

+ +

The MIF Editor allows you to create or edit the .mif files list of scalable icons (.svg) + included in a S60 v3.0 and later GUI projects as well as standard .bmp files. A .mif file is a MSX Interchange Format (MIF) file that should be built by the project. MIF files replace the functionality of AIF (and MBM) files.

NOTE This editor is only supported by the S60 3.0 and later SDKs.

Figure 1 - MIF File in the Symbian Project Navigator view

The MIF Editor appears when a MIF file is + opened for editing. To open the editor double-click on a .mif file in the Symbian Project Navigator view (figure 1), or select a scalable icon makefile (for example, Icons_scalable_dc.mk), right-click and select the Add MBM/MIF Entry command.

Figure 2 - MBM/MIF Editor

Table 1. MBM/MIF 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 the Add Images from Project dialog to reference available images in the project.
Add From Filesystem	Click this button to open the 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.

+ + + + \ No newline at end of file diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/view_registers.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_registers.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_registers.htm Fri Feb 12 14:45:16 2010 -0600 @@ -1,63 +1,63 @@ - - - - - - -Registers View - - - -

Registers View

The Registers view reveals a hierarchical view of general, FPU, and host-specific registers of the host computer or target device. You can use the Register view to perform these tasks:

expand the hierarchical items in the window and view their contents
select and modify register values
view documentation for individual registers (depending on the register)

Figure 1 shows a sample Registers view.

Figure 1 - Registers View

Table 1. Registers view—items

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

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Registers view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded variables into the top level.

For more information, see the C/C++ Development User Guide > Reference > Debug View > Registers view.

To open a Registers view

Click Window > Show View > Registers

A Registers view appears.

Other references

- - - + + + + + + +Registers View + + + +

Registers View

The Registers view reveals a hierarchical view of general, FPU, and host-specific registers of the host computer or target device. You can use the Register view to perform these tasks:

expand the hierarchical items in the window and view their contents
select and modify register values
view documentation for individual registers (depending on the register)

Figure 1 shows a sample Registers view.

Figure 1 - Registers View

Table 1. Registers view—items

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

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Registers view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded variables into the top level.

For more information, see the C/C++ Development User Guide > Reference > Debug View > Registers view.

To open a Registers view

Click Window > Show View > Registers

A Registers view appears.

Other references

+ + + \ No newline at end of file diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/view_signals_wnd.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_signals_wnd.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_signals_wnd.htm Fri Feb 12 14:45:16 2010 -0600 @@ -11,39 +11,37 @@

Signals View

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.

NOTE Currently Carbide.c++ does not support this CDT feature.

Figure 1 shows the Signals view.

Figure 1 - Signals view

Table 1 Signals view—items

- +

- - + + - + - + - + - +

Item	Explanation	Item
Name	Name	Displays the name of the signal.
Pass	Pass	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.
Suspend	Suspend	Where "yes" is displayed, the debugger suspends your program when this signal is handled.
Description	Description	Displays a description of the signal.

Related reference

Debug view

- + diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Fri Feb 12 14:45:16 2010 -0600 @@ -29,6 +29,9 @@

Libraries

NOTE Information for the Chunks and Libraries tabs is not available when debugging with the TRK debug agent.

Overview Tab

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.

Figure 1. Symbian OS Data view

Table 1 - Symbian OS Data view toolbar buttons

@@ -71,9 +74,6 @@ Click the Collaps All command to collapse all of the currently elements in the view. -

Overview Tab

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.

Processes

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.

diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/view_system_browser.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_system_browser.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_system_browser.htm Fri Feb 12 14:45:16 2010 -0600 @@ -1,62 +1,62 @@ - - - - - - -System Browser View - - - -

System Browser View

The System Browser view shows system level information about processes executing on various machines, like the host computer or the hardware under debugger control. The view shows this information:

running processes
tasks for selected processes
some hidden processes

Click on the expand icon for a process to view all tasks assigned to the selected process. Processes under debugger control appear in bold. Double-click a task to open it in a new Thread window, or choose the task name and click the Stack Crawl View button.

Table 1 explains items in the window.

NOTE If the System Browser view does not show processes for a sepcific machine, you will need to start a debugging session for that machine. For example, you might need to debug a project that runs on external hardware in order to see executing processes for that hardware.

Table 1 System Browser view—items

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

Item	Icon	Explanation
Attach to Process		Click to have the debugger control the selected process.
Stack Crawl view		Click to open a Thread window for the selected process.
Refresh		This icon indicates that information for selected item is periodically updated. Click this icon to toggle between refresh and no refresh.
No Refresh		This icon indicates that information is not updated for the selected item.
Expand		Click to expand a process and list related tasks.

Related concepts

- - - - + + + + + + +System Browser View + + + +

System Browser View

The System Browser view shows system level information about processes executing on various machines, like the host computer or the hardware under debugger control. The view shows this information:

running processes
tasks for selected processes
some hidden processes

Table 1 explains items in the window.

NOTE If the System Browser view does not show processes for a specific machine, you will need to start a debugging session for that machine. For example, you might need to debug a project that runs on external hardware in order to see executing processes for that hardware.

Table 1 System Browser view—items

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

Item	Icon	Explanation
Attach to Process		Click to have the debugger control the selected process.
Stack Crawl view		Click to open a Thread window for the selected process.
Refresh		This icon indicates that information for selected item is periodically updated. Click this icon to toggle between refresh and no refresh.
No Refresh		This icon indicates that information is not updated for the selected item.
Expand		Click to expand a process and list related tasks.

Related concepts

+ + + + diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_build_prefs.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_build_prefs.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_build_prefs.htm Fri Feb 12 14:45:16 2010 -0600 @@ -128,12 +128,11 @@ Check this box to enable an edit box to specify the make engine to use, for example, eMake from Electric Cloud. -

Related references

Carbide Project Settings

- + diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref.htm Fri Feb 12 14:45:16 2010 -0600 @@ -15,7 +15,7 @@

Figure 1 - Carbide.c++ preferences page

Table 1 Carbide.c++ Preferences —items

- +

@@ -56,7 +56,7 @@

Platform Filtering Preferences

SDK Preferences

- + diff -r 248e161fd5cd -r 57698352558c core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debug_configuration.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debug_configuration.htm Thu Feb 11 16:46:41 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debug_configuration.htm Fri Feb 12 14:45:16 2010 -0600 @@ -4,17 +4,17 @@ -Debug Window +Debug Configurations Window -

Debug Window

The Debug or launch configuration window provides C/C++ debugger options. A launch configuration defines the settings used by the Carbide debugger to launch and debug programs. A project must have at least one debug launch configuration in order to debug a project and can have many more.

Debug Configurations Window

The Debug Configurations or launch configuration window provides C/C++ debugger options. A launch configuration defines the settings used by the Carbide debugger to launch and debug programs. A project must have at least one debug launch configuration in order to debug a project and can have many more.

By default, Carbide creates a debug launch configuration the first time you launch the debugger based on current project settings. If additional information is required, like a port ID, the New Launch Configuration Wizard appears asking for the additional information.

The tabs in the window vary depending upon the currently selected launch configuration.

-Figure 1 - Debug or launch configuration window (Symbian OS emulation view)

Table 1. Debug window — common items

Figure 1 - Debug or launch configuration window (Symbian OS emulation view)

Table 1. Debug Configuration window — common items

Item	Explanation

@@ -74,7 +74,7 @@

Run-mode overview

Stop-mode overview

- + \ No newline at end of file

Icon