# HG changeset patch # User fturovic # Date 1271192145 18000 # Node ID e265bbe56eb0fd937c881ab7ca9ef30517771985 # Parent 5310aeaa3526f57a9d4a02898e085bc8a67f911a merge 2.6 changes to 3.0 docs diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/build.properties --- a/core/com.nokia.carbide.cpp.doc.user/build.properties Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/build.properties Tue Apr 13 15:55:45 2010 -0500 @@ -1,22 +1,12 @@ -bin.includes = plugin.xml,\ +bin.includes = book.css,\ debuggerTOC.xml,\ intro/,\ - index.xml,\ tocCarbide.xml,\ - book.css,\ - tocRelease.xml,\ - src.includes = META-INF/,\ - debuggerTOC.xml,\ + plugin.xml,\ + html/ +src.includes = tocCarbide.xml,\ plugin.xml,\ - index.xml,\ - tocRelease.xml,\ - tocCarbide.xml,\ - book.css,\ - META-INF/,\ - html/ -src.includes = book.css,\ + intro/,\ + html/,\ debuggerTOC.xml,\ - html/,\ - intro/,\ - tocCarbide.xml,\ - plugin.xml + book.css diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Tue Apr 13 15:55:45 2010 -0500 @@ -16,14 +16,31 @@

Carbide.c++ bugs fixed

This is a comprehensive list of bugs fixed by release:

+

Bugs Fixed in v2.6.0

+

Bugs Fixed in v2.5.0

Bugs Fixed in v2.4.0

NOTE When launching a program to debug, the Debug perspective appears.

-

+

Figure 1 - Carbide C/C++ perspective

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 @@ -40,7 +40,7 @@

  • C/C++ Projects view
  • Symbian Project Navigator view
    • - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/MBMDefWizard.html --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/MBMDefWizard.html Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/MBMDefWizard.html Tue Apr 13 15:55:45 2010 -0500 @@ -1,7 +1,7 @@ MBM File in Concepts - +

    MBM File

    @@ -9,9 +9,9 @@ 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.

    -

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

    +

    The following information is required to add a bitmap without a mask:

    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.

    @@ -35,12 +35,12 @@
    Build Configuration Naming
    -

    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:

    +

    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:

    You can use the Debug window to edit the default build configuration names.

    Other references
    @@ -50,7 +50,7 @@
  • Creating Launch Configurations
  • Adding/Removing Build Configurations
    • - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/build_targets.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/build_targets.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/build_targets.htm Tue Apr 13 15:55:45 2010 -0500 @@ -21,10 +21,10 @@ Target Types Platform Security
    -(S60 3.1, S60 3.0, UIQ 3.0) +(S60 3.2, S60 5.0) -
    GCCE, ARMV5, ARMV5_ABIV2
    +
    RAPTOR, GCCE, ARMV5, ARMV5_ABIV2
    WINSCW
    (EKA2)
    @@ -65,7 +65,7 @@
  • Setting Build Configurations
  • Creating a Launch Configuration
    • - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/carbide_projects.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/carbide_projects.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/carbide_projects.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,14 +9,14 @@

    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 menu item, File > Import, or the Project Properties window.

    -

    Carbide.c++ can not export changes back to an .inf file.

    +

    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.

    +

    Carbide.c++ can not export changes back to an .INF file.

    Related tasks
    - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/common_debug_actions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/common_debug_actions.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/common_debug_actions.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,7 +9,7 @@

    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:

    +

    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:

    - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/concepts.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/concepts.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/concepts.htm Tue Apr 13 15:55:45 2010 -0500 @@ -17,7 +17,7 @@

    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.

    @@ -41,13 +41,11 @@
  • Precompiled Headers
  • Registers
  • SDK Support
    • -
  • Symbol Hint
  • Symbols, .pkg
    • -
  • Watchpoints
  • Workspace Information
    • - +
    diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/contextual_menus.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/contextual_menus.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/contextual_menus.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,7 +9,7 @@

    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.

    +

    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.

    Sample uses of the context menu for different tasks include:

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

    Figure 1 shows a sample context menu in the Breakpoints view.

    -

    -

    Figure 1 - Context menu in Breakpoints view

    +

    +

    Figure 1 - Example context menu in Breakpoints view

    Using Context Menus

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

    @@ -39,7 +39,7 @@ - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/emulators.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/emulators.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/emulators.htm Tue Apr 13 15:55:45 2010 -0500 @@ -14,9 +14,9 @@ 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.

    + 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

    @@ -30,7 +30,7 @@
  • Importing Executables for Debugging
    • - +
    diff -r 5310aeaa3526 -r e265bbe56eb0 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 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/mmpfiles.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/mmpfiles.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/mmpfiles.htm Tue Apr 13 15:55:45 2010 -0500 @@ -15,7 +15,7 @@
  • MMP Editor
    • - +
    diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm Tue Apr 13 15:55:45 2010 -0500 @@ -68,7 +68,7 @@

    With your game file installed on the device, create a launch configuration for the project. In Carbide:

    1. OpenWindow > Preferences > Run/Debug > Launching preference panel and disable the Build (if required) before launching option
      2. -
    2. Right-click the project and choose Debug As > Open Debug Dialog to open the Debug window
      3. +
    3. Right-click the project and choose Debug As > Debug As to open the Debug window
    4. Create an Application TRK launch configuration
      • In the Connection tab select the COM port used to connect to the device.
        • @@ -85,7 +85,7 @@

        With your game file installed to the emulator, create a launch configuration for the project. In Carbide:

        1. Open Window > Preferences > Run/Debug > Launching and disable the Build (if required) before launching option
          2. -
        2. Right-click the project and choose Debug As > Open Debug Dialog to open the Debug window
          3. +
        3. Right-click the project and choose Debug As > Debug As to open the Debug window
        4. Create an Symbian OS Emulation launch configuration
        5. Click Debug to launch the emulator
        6. In the emulator, select File > Open, locate and select the .N-GAGE installation file and click Open to install the project
          7. diff -r 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/precompiled_headers.htm Tue Apr 13 15:55:45 2010 -0500 @@ -30,7 +30,6 @@

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

    #include pch_test.mch

    -

     

    diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/registers.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/registers.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/registers.htm Tue Apr 13 15:55:45 2010 -0500 @@ -11,10 +11,14 @@

    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:

    +

    +

    Figure 1. Registers view with possible register types

    +

    The types of registers can include:

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

    @@ -25,7 +29,7 @@
  • Changing Register Values
  • ARM Registers
    • - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/concepts/watchpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/watchpoints.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/watchpoints.htm Tue Apr 13 15:55:45 2010 -0500 @@ -5,113 +5,20 @@ 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:

    - -

    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:

    +

    A watchpoint 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 Breakpoints view.

    +

    When a watchpoint is encountered during program execution, the debugger suspends execution and the Debug 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.

    +

    The following topics cover various breakpoint concepts and actions:

    -

    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
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    TypeStateIconExplanation
    Writeenabled

    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.

    -
    disabled

    Watchpoint is disabled for the source line, debugger does not halt program execution on a write operation.

    -
    Readenabled

    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.

    -
    disabled

    Watchpoint is disabled for the source line, debugger does not halt program execution on a read operation.

    -
    Write/Readenabled

    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.

    -
    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
    - -
    Related tasks
    - -
    Related references
    - - diff -r 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_programs.htm Tue Apr 13 15:55:45 2010 -0500 @@ -22,7 +22,7 @@
    Related references
    - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm Tue Apr 13 15:55:45 2010 -0500 @@ -15,7 +15,7 @@
  • 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 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm Tue Apr 13 15:55:45 2010 -0500 @@ -14,7 +14,7 @@

    To access the Launch Configurations Filter Window

      -
    1. Select the Run > Open Debug Dialog... menu item
      2. +
    2. Select the Run > Debug As menu item

      3. The Debug window appears.

    3. Select the Filter icon in the toolbar above the list of configuration types and defined configurations.

      4. The Preferences (Filtered) window appears (Figure 1).

      diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm Tue Apr 13 15:55:45 2010 -0500 @@ -35,9 +35,9 @@

      Figure 1 - Remote Connections view

      -

      When the view is closed or another perspective opened, a small display item appears in the lower-left corner of the perspective. Click the connection name to open the drop-down menu where you can open the Remote Connections view or switch between connections.

      -

      -

      Figure 2. Remote Connections tab

      +

      When the view is closed or another perspective opened, a small display appears in the trim area in the lower-right corner of the workspace showing the current active remote connection. Click the connection name to open the drop-down menu where you can open the Remote Connections view or switch between connections.

      +

      +

      Figure 2. Available remote connection trim indicator

      Remote Connections view toolbar icons

      The following commands appear on the toolbar within the Remote Connections view:

      diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_install_tab.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_install_tab.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_install_tab.htm Tue Apr 13 15:55:45 2010 -0500 @@ -10,9 +10,9 @@ -

      Install Remote Agents pane

      +

      Install Remote Agents

      Use the Install remote agents pane to select the latest remote agent version to download and install to the device.

      -

      +

      Figure 2 - New Connection wizard Install remote agents page

      Table 1. Install Remote Agents pane

      @@ -22,7 +22,7 @@ - @@ -32,15 +32,18 @@ +

      NOTE Drivers installed by PC Suite or Ovi Suite are required in order for Install to download a remote agent onto the target device.

      +

      NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite or Ovi Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

      Install remote agents

      A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.2.0 needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 3.0.4.

      +

      A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 5.0 needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 3.2.6.

      Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.

      Install

      Click Install to download and install the TRK selected in the Install remote agents list. A progress bar is shown if the install operation requires more than a few seconds to complete.

      -

      NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

      Related references
      - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_connection_wizard.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_connection_wizard.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_connection_wizard.htm Tue Apr 13 15:55:45 2010 -0500 @@ -5,38 +5,42 @@ -New Connection Wizard +Setup Connection -

      New Connection Wizard

      -

      Use the Remote Connections view to monitor, create, edit, or remove common remote connection settings.

      - -

      Edit connection name and type

      -

      Use the Edit connection name and type page to assign a name and connection type to the new connection setup.

      -

      -

      Figure 1 - New Connection wizard Edit connection name and type page

      -

      Table 1. Edit connection name and type page - options

      +

      Setup Connection

      +

      Use the Edit Connection page to assign a connection type, name, and connection settings to the new connection setup.

      +

      +

      Figure 1 - New Connection wizard Setup Connection tab

      +

      Table 1. Setup Connection page - options

      + + + + - - - - - +
      Item Explanation
      Connection Type

      Select the type of connection and its supported services from the drop down list of options. The types of connections include:

      +
        +
      • Bluetooth - serial port connection through Bluetooth
        • +
      • Serial - serial port connection through a COM serial port
        • +
      • USB - serial port connection through USB that supports TRK 3.x
        • +
      +

      And the supported services may include:

      +
        +
      • TRK
        • +
      • Tracing
        • +
      • and others
        • +
      Connection Name

      Enter a name for the connection.
      Connection TypeSelect the type of connection this setup will use.
      Supported ServicesConnection Settings

      Shows a list of services supported by the connection type chosen.

      • Bluetooth - serial port connection through Bluetooth
        • @@ -45,84 +49,13 @@
      -

      Set Connection Settings pane

      -

      Use the Set Connection Settings pane to compare the version of remote agent installed on the device with the latest version available for Carbide. In this pane you can:

      -
        -
      • Set the device OS used by the device and supported by the selected remote agent
        • -
      • Allow easy serial port selection when connecting to a device
        • -
      • Verify that you have the latest remote agent installed on a device
        • -
      -

      -

      Figure 2 - New Connection wizard Serial Connection Settings page

      -

      Table 2. Serial Connection Setting page - Set Connection Settings tab

      - - - - - - - - - - - - - - - - - - - - - - - - - -
      ItemExplanation
      Serial Port A dropdown list of serial ports with known identifiers for selecting the communication port used by the PC to communicate with the device. A named COM port (COM4 - BthModem0) indicates an active port. Unnamed port numbers have usually not been opened and assigned by the PC.
      Baud Ratea dropdown list of baud rates common to serial connections.
      Device OS

      A dropdown list of device OSes that are supported by the remote agent software. Select the OS used by the device before running a check.

      Select a service to testClick to select a listed service for testing.
      Test Service Status

      Click Test Service Status to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Test Service Status version operation requires more than a few seconds.

      -

      NOTE The PC must have an internet connection to perform a remote agent version check.

      -

      Once the comparison is complete the Status text is updated with the result and further instructions as required.

      -

      -

      If a connection fails, the errors normally fall into these two categories:

      -
        -
      • connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response.
        • -
      • remote agent not responding - this indicates that the COM port is open but the remote agent is not responding. First, verify that remote agent is up and running on the device. Second, the remote agent may be listening on a different COM port, so choose another named COM port and try again.
        • -
      -

       

      -

      Install Remote Agents pane

      -

      Use the Install Remote Agents pane to select the latest remote agent version to download and install to the device.

      -

      -

      Figure 2 - New Connection wizard Bluetooth Settings page

      -

      Table 3. Serial Connection Setting page - Install Remote Agents tab

      - - - - - - - - - - - - - - - - - -
      ItemExplanation
      Install remote agents

      A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 2.8.7.

      -

      Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.

      -

      NOTE Requires a network connection to query the remote agent site.

      SaveClick Save to store a local copy of the currently selected TRK to disk. You can then manually install the file to your devices using the method of your choice.
      Install

      Click Install to download and install the TRK selected in the Install latest TRK list. A progress bar is shown if the install operation requires more than a few seconds to complete.

      -

      NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

      Related references
      - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_on_device_check_tab.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_on_device_check_tab.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_on_device_check_tab.htm Tue Apr 13 15:55:45 2010 -0500 @@ -5,30 +5,21 @@ -Initiate Service Testing +Test Connection - -

      Initiate Service Testing

      -

      Use the Set Connection Settings pane to compare the version of remote service installed on the device with the latest version available for Carbide. A remote service is any software on the device that can communicate with Carbide. This includes TRK, Performance Investigator, and other services. In this pane you can:

      -
        -
      • Specify the Connection Settings to connect to the device
        • -
      • Set the device OS used by the device and supported by the remote service
        • +

        Test Connection

        +

        Use the Set Connection Settings pane to compare the version of remote service installed on the device with the latest version available for Carbide. A remote service is any software on the device that can communicate with Carbide. This includes TRK, Trace, Performance Investigator, and other services. In this pane you can:

        +
        • Set the device OS used by the device and supported by the remote service
          • +
        • Verify that Carbide can communicate with the remote service via the chosen connection setting
        • Verify that you have the latest version of the remote service installed on the device
        -

        Options presented may differ based on the connection setting type chosen.

        -

        -

        Figure 1 - Set Connection Settings pane in the New Connection dialog

        -
        Table 1 Set Connection Settings pane — items
        +

        Options presented may differ based on the type of connection setting chosen.

        +

        +

        Figure 1 - Test Connection pane in the New Connection dialog

        +
        Table 1 Test Connection pane — items
        @@ -39,15 +30,11 @@ - - - - - + +
        Item

        A dropdown list of device OSes that are supported by the TRK debug agent software. Select the OS used by the device before running a check.

        Serial Port A dropdown list of serial ports with known identifiers for selecting the communication port used by the PC to communicate with the device. A named COM port (COM4 - BthModem0) indicates an active port. Unnamed port numbers have usually not been opened and assigned by the PC.
        Select a service to test Select the remote service type to query on the remote device.
        Initiate service testingInitiate service testing

        Click Initiate service testing to query the remote software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear when the operation requires more than a few seconds.

        NOTE The PC must have an internet connection to perform a remote service version check.

        Once the comparison is complete the Status text is updated with the result and further instructions as required.

        @@ -56,15 +43,16 @@
        • connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response.
        • Service not responding - this indicates that the COM port is open but the remote service is not responding. First, verify that remote service is up and running on the device. Second, the remote service may be listening on a different COM port, so choose another named COM port and try again.
          • -
        -
        Related references
        - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_on_device_setup.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_on_device_setup.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_on_device_setup.htm Tue Apr 13 15:55:45 2010 -0500 @@ -11,18 +11,21 @@

        On-Device Connections

        -

        Use the New Connection wizard to verify and update Carbide software services on a device. Click the Help > On-Device Connections... menu option to open. Currently, the only service available is TRK, but look for others in future releases. The following tabs are present:

        +

        Use the New Connection wizard to verify and update Carbide software services on a device. Click the Help > On-Device Connections... menu option to open. Current services available include TRK, Tracing, and others. The following tabs are present:

        -

        +

        Figure 1 - New Connection dialog

        Related references
        - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/reference/view_disassembly.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_disassembly.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_disassembly.htm Tue Apr 13 15:55:45 2010 -0500 @@ -23,61 +23,84 @@
      • 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.
      • Set breakpoints at the start of any assembler instruction by right-clicking the left hand column to view the context menu options (Figure 2)
      -

      Figure 1 shows the Dissassembly view and the PC context menu that appears when you right-click in the data pane. Right-clicking the left border opens the breakpoint context menu.

      -

      -

      Figure 1 - Repositioning the PC in the Disassembly view

      -

      -

      Figure 2 - Setting Breakpoints in the Disassembly view

      -
      Table 1. Disassembly view —context menu
      +

      Figure 1 shows the Dissassembly view stopped at a breakpoint.

      +

      +

      Figure 1 - Disassembly view

      +

      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.

      +

      +

      Figure 2 - Disassembly pane context menu

      +
      Table 1. Disassembly pane — context menu
      - - - + + + + + + + + - - - - + + + + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + +
      ItemIconExplanationItemIconExplanation
      Run to Line
      + +
      		Select Run to Line to execute the program from the currently executed line (the green line) to the selected line (the blue line).
      Run to Line
      - -
      		Select Run to Line to execute the program from the currently executed line (the green line) to the selected line (the blue line).
      Move to Line
      + +

      Select Move to Line 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.

      +

      WARNING Using this command can leave a program in an unstable state. Use at your own risk.

      Resume at Line
      + +

      Select Resume at Line to begin program execution at the selected line (the blue line), skipping all lines between it and the currently executed line (the green line).

      +

      WARNING Using this command can leave a program in an unstable state. Use at your own risk.

      ABLD Use the ABLD menu option to invoke an specific abld command on the selected project or file.
      Move to Line
      - -
      -

      Select Move to Line 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.

      -

      WARNING Using this command can leave a program in an unstable state. Use at your own risk.

      Resume at Line
      - -

      Select Resume at Line to begin program execution at the selected line (the blue line), skipping all lines between it and the currently executed line (the green line).

      -

      WARNING Using this command can leave a program in an unstable state. Use at your own risk.

      Toggle Breakpoint
      -
      		Right-click in left-hand column of the Disassembly view and select this option to toggle the breakpoint state between setting and removing the breakpoint.
      Disable/Enable Breakpoint
      -
      		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.
      Breakpoint Properties
      -
      		Select this option to open the Breakpoint Properties dialog.
      Freeze Exports
      + +
      +       		Calls the appropriate abld command to generate a .def file.
      Build All Configurations
      + +
      +       		Click Build All Configurations to build all enabled build configurations in the current project.
      Toggle Breakpoint
      +
      		Right-click in left-hand column of the Disassembly view and select this option to toggle the breakpoint state between setting and removing the breakpoint.
      Disable/Enable Breakpoint
      +
      		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.
      Breakpoint Properties
      +
      		Select this option to open the Breakpoint Properties dialog.
      +

      +

      Figure 3 - Setting Breakpoints in the Disassembly view

      Opening the Disassembly view

        @@ -96,6 +119,6 @@ - + diff -r 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_expressions.htm Tue Apr 13 15:55:45 2010 -0500 @@ -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,22 @@ + + + + +
        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

        +

        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 +84,7 @@
      • Adding & Removing Expressions
      • Editing Expressions
      - + diff -r 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_global_variables.htm Tue Apr 13 15:55:45 2010 -0500 @@ -10,7 +10,7 @@

      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 shows the Global Variables window.

      Figure 1 Global Variables window

      Table 1 Global Variables window—items
      @@ -19,11 +19,11 @@ - + - +
      Explanation
      FileFile 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.
      VariablesVariables Lists variables according to the file selected in the File pane. Double-click a variable to display it in a separate Variable window.
      @@ -47,7 +47,7 @@

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

    - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/reference/view_mem_array.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_mem_array.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_mem_array.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,7 +9,7 @@

    Array Window

    -

    An Array window allows manipulation of a contiguous block of memory, displayed as an array of elements. The window lists array contents sequentially, starting at +

    The Array window allows manipulation of a contiguous block of memory, displayed as an array of elements. The window lists array contents sequentially, starting at element 0.

    The Array window title shows the base address bound to the array. The base address can bind to an address, a variable, or a register. An array bound to a local variable closes after the routine that defines the variable returns to the calling routine.

    For array elements cast as structured types, a hierarchical control appears to the left of each element. Use these hierarchical controls to expand or collapse the display of each element’s contents.

    @@ -70,7 +70,7 @@

    TIP Drag and drop a register or variable name into an Array window to set the base address. Use the View Memory As command to interpret memory displayed in an Array window as a different type.

    Alternatively, use a contextual menu to open an Array window, as explained in Table 2.

    -
    Table 2 Opening an Array window by using a contextual menu
    +
    Table 2 Opening an Array window by using a context menu
    @@ -91,7 +91,7 @@
    On this host…


    - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_memory_wnd.htm Tue Apr 13 15:55:45 2010 -0500 @@ -18,8 +18,8 @@

    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 1 shows the Memory view.

    +

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

    Table 1 Memory view—items
    @@ -39,6 +39,11 @@ + + + + + @@ -75,14 +80,14 @@
    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.

    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
    - + diff -r 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_mifdef_editor.htm Tue Apr 13 15:55:45 2010 -0500 @@ -8,18 +8,16 @@

    MBM/MIF Editor

    -

    The MIF Editor allows you to create or edit the .mif files list of scalable icons (.svg) +

    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

    +

    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.

    +

    +

    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
    @@ -28,7 +26,7 @@ - + @@ -64,15 +62,15 @@ - + - + - + @@ -101,7 +99,7 @@
    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.

    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
    Add From Project Click this button to open an Add Images from Project dialog to reference available images in the 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 an Add Images From Filesystem dialog to locate and reference existing images in the filesystem or copy images to the project.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.
    RemoveSelect an image and click Remove to remove image entry from the list. This does not delete file from directory.Select an image and click Remove to remove image entry from the list. This does not delete file from directory.
    Color depth

     

    - + diff -r 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_registers.htm Tue Apr 13 15:55:45 2010 -0500 @@ -16,7 +16,7 @@
  • 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
    @@ -57,7 +57,7 @@
  • Viewing Register Values
  • Changing Register Values
    • - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_signals_wnd.htm Tue Apr 13 15:55:45 2010 -0500 @@ -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
    -
    +
    - - + + - + - + - + - +
    ItemExplanationItemExplanation
    NameName Displays the name of the signal.
    PassPass 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.
    SuspendSuspend Where "yes" is displayed, the debugger suspends your program when this signal is handled.
    DescriptionDescription Displays a description of the signal.
    -

     

    Related reference
    - + diff -r 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Tue Apr 13 15:55:45 2010 -0500 @@ -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 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_system_browser.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,7 +9,7 @@

    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:

    +

    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:

    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.

    +

    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
    - - + + - + - + - + - + - + @@ -56,7 +56,7 @@
  • Opening a System Browser View
  • Attaching Debugger to a Process
    • - + diff -r 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_build_prefs.htm Tue Apr 13 15:55:45 2010 -0500 @@ -128,12 +128,11 @@
    ItemIconItemIcon Explanation
    Attach to ProcessAttach to Process   Click to have the debugger control the selected process.
    Stack Crawl viewStack Crawl view   Click to open a Thread window for the selected process.
    RefreshRefresh   This icon indicates that information for selected item is periodically updated. Click this icon to toggle between refresh and no refresh.
    No RefreshNo Refresh   This icon indicates that information is not updated for the selected item.
    ExpandExpand   Click to expand a process and list related tasks.
    Check this box to enable an edit box to specify the make engine to use, for example, eMake from Electric Cloud.
    -

     

    Related references
    - + diff -r 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref.htm Tue Apr 13 15:55:45 2010 -0500 @@ -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 5310aeaa3526 -r e265bbe56eb0 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 Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debug_configuration.htm Tue Apr 13 15:55:45 2010 -0500 @@ -4,17 +4,18 @@ -Debug Window - +Carbide Debug dialog + -

    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.

    -

    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
    +

    Debug dialog

    +

    Use the Debug dialog to create, edit, and manage a project's launch configurations. A launch configuration defines the settings used by the Carbide debugger to launch (Run) or debug programs. A project must have at least one launch configuration in order to debug a project and can have many more. Projects that have no launch configuration invoke the New Launch Configuration Wizard when either the Run or Debug command is selected.

    +

    Select the Run > Debug Configuration... menu option to open the Debug dialog.

    +

    The tabs shown in the Debug dialog vary depending upon the type of launch configuration highlighted in the configurations list. See Launch Configuration Overview for more information on the various launch configuration types.

    +

    Click Debug to start a new debug session using the selected launch configuration.

    +

    +

    Figure 1 - Debug dialog (Symbian OS Emulation configuration shown)

    +
    Table 1. Debug dialog — common items
    Item Explanation
    @@ -51,30 +52,15 @@
  • Filter Deleted/Unavailable Projects
  • Filter Configuration Types
  • Apply Window Working Set(s)
    • -
  • Filtering Preferences...
    • +
  • Filtering Preferences...
    • Icon
    -
    -

    To open the Debug window

    -
      -
    • Select the Run > Open Debug Dialog... menu item
      • -
    -
      - The Debug window (Figure 1) appears.
    -
      -
    • Select Run > Open Run Dialog... to open a Run window to create a launch configuration for a release build.
      • -
    -
    -
    Other references
    +

    Other references

    - \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/release_notes.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/release_notes.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/release_notes.htm Tue Apr 13 15:55:45 2010 -0500 @@ -12,11 +12,11 @@ .style1 {font-family: "Courier New", Courier, mono} .style5 {color: #FF0000} .style6 {font-weight: bold} - .style8 {color: #000000; font-weight: bold; } +.style8 {color: #000000; font-weight: bold; } -

    Carbide.c++ Release Notes 2.5.0

    +

    Carbide.c++ Release Notes 2.6.0

    The Carbide.c++ is a comprehensive development tool suite for Symbian OS that is based on the Eclipse framework. The C++ Development Toolkit (CDT), provides the foundation for project and build tools management, as well as the primary interface for the debugger to communicate with the IDE.

    This is a collection of important information concerning last-minute changes and other topics that deserve special attention. Please @@ -35,25 +35,38 @@ Updating the CDT feature in Carbide.c++/Eclipse will wipe out our changes making the tools unusable!

    See the Tips & tricks page for more helpful information.

    -

    What's New in 2.5.0

    +

    What's New in 2.6.0

    The following features for Symbian development are provided within Carbide.c++:

    -

    2.4.0

    +

    2.5.0

    + +

    2.4.0

    -

    2.3.0

    +

    2.3.0

    -

    2.2.0

    +

    2.2.0

    -

    2.1.0

    +

    2.1.0

    - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingProjectsToc.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingProjectsToc.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingProjectsToc.htm Tue Apr 13 15:55:45 2010 -0500 @@ -11,7 +11,7 @@
  • Importing Projects from a BLD.INF File
  • Importing Projects with Inter-Dependencies
    • - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/EmulatorToc.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/EmulatorToc.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/EmulatorToc.htm Tue Apr 13 15:55:45 2010 -0500 @@ -7,9 +7,9 @@

    The topics include:

    - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/ExportingtoMMP_BLDinf.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ExportingtoMMP_BLDinf.html Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/ExportingtoMMP_BLDinf.html Tue Apr 13 15:55:45 2010 -0500 @@ -33,7 +33,7 @@
  • Select Symbian MMP/Bld.Inf and click Next to go to the Symbian Projects page: -

    +

    @@ -92,16 +92,16 @@ file based on the chosen build configuration. If more than one build configuration which require different build settings are chosen, guard macros are used to determine the build settings. For example, if you want to change - the SECUREID option for all the EKA2 build + the SECUREID option for all the EKA2 build configurations, the wizard will append the following lines into the - MMP file:

    + MMP file:

    #if def EKA2
      SECUREID 0x00301
    #endif

    - Where EKA2 is the guard macro for all the build + Where EKA2 is the guard macro for all the build configurations designed for the EKA2 kernel. The above MMP file - statements check whether the EKA2 guard macro is defined, and if - it is, change the SECUREID option accordingly.

    -
    • + statements check whether the EKA2 guard macro is defined, and if + it is, change the SECUREID option accordingly.

    +
  • Click Next to go to the MMP File and Bld.inf File page: @@ -168,9 +168,9 @@ epoc32\include directory.

    Note that the contents of the PRJ_EXPORTS list is - exactly the same as it appears in the PRJ_EXPORTS section of the - Bld.Inf file.

    -
    • + exactly the same as it appears in the PRJ_EXPORTS section of the + Bld.Inf file.

    +
  • If you want to modify or delete any entry from the PRJ_EXPORTS list, select the entry and click @@ -189,7 +189,7 @@ contents if required.
  • Click Finish to complete the export process. The - wizard will create the managed MMP file and Bld.inf + wizard will create the managed MMP file and Bld.inf file in their specified locations.

    A managed MMP file contains the same content as a @@ -223,9 +223,9 @@ You will be notified in case of any errors during the updated process, which results in not creating the MMP or Bld.Inf files.

    -
    • - - + +     +

    The following MMP file generated by the wizard, shows how its content is organised using managed sections:

    @@ -266,6 +266,6 @@ /*& END_LINKAGE_INFORMATION &*/

    - +     \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/Multi-BitmapFile.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/Multi-BitmapFile.html Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/Multi-BitmapFile.html Tue Apr 13 15:55:45 2010 -0500 @@ -14,11 +14,11 @@
    1. - In the Symbian Project Navigator view double-click a .mmp file (Figure 1) to open the MMP Editor (Figure 2). -

      + In the Symbian Project Navigator view double-click a .mmp file (Figure 1) to open the MMP Editor (Figure 2). +

      Figure 1- MMP File

      2. -
    2. +
    3. In the Sources tab under the Resources group, select Bitmaps

      4. diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/RmvngandVwngPropsosSDK.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/RmvngandVwngPropsosSDK.html Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/RmvngandVwngPropsosSDK.html Tue Apr 13 15:55:45 2010 -0500 @@ -27,7 +27,7 @@
      -

      +

      NOTE SDKs shown in red indicate a problem, for example no EPOCROOT.

      diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,61 +9,28 @@

      Run Mode On-Device Debugging

      -

      To implement run mode on-device debugging the following tasks need to be completed.

      +

      Run mode on-device debugging enables you to download and launch a project on a phone or target device and debug it using the Carbide debugger. Before you can do that, some setup requirements are required. Once the setup is done, Carbide can then use plug-and-play (PnP) with USB to create a remote connection that connects with the TRK agent on the target device to download, launch, and debug the program.

        -
      1. Install device connection software
        2. -
      2. Install Perl
        3. -
      3. Install an SDK
        4. -
      4. Setup environment variables
        5. -
      5. Setup a virtual drive for Techview and Cust Kits
        6. -
      6. Set the default kit in Devices.xml
        7. -
      7. Install the SISX file on the target device
        8. -
      8. Configure TRK connection on the device
        9. -
      9. Create a launch configuration
        10. +
      10. Setup system and development requirements (below)
        11. +
      11. Install Application or System TRK v3.2.6 or later on the target device
        12. +
      12. Connect USB cable to phone or target device for PnP connectivity
        13. +
      13. Create or import a project in the Carbide C/C++ workspace
        14. +
      14. Build the project
        15. +
      15. Debug the project on a phone or target device
      -

      Install Device Connection Software

      -

      The two choices for connecting are Bluetooth and PC Suite.

      -
      BlueTooth
      -
        -
      1. System requirements:
        2. +

        Setup system and development requirements

        +

        All of the following requirements are required to build, communicate, and control programs on a phone or target device.

          -
        • Administration rights on your computer
          • -
        • BT dongle attached to your computer
          • -
        • Bluetooth installer to install the drivers
          • +
        • Install PC Suite or Ovi Suite on your PC to ensure the correct drivers are installed for connecting to the phone or target device.
          • +
        • Install the correct version of Perl on your PC to support Symbian OS builds
          • +
        • Install a supported SDK and make sure its the default
          • +
        • Configure the environmental variables
          • +
        • (Optional) Setup a virtual drive to use Techview and Cust Kits
        -
      2. Install the Bluetooth dongle to a USB port
        3. -
      3. Install the drivers from the Bluetooth CD
        4. -
      4. Click on the Bluetooth icon in your system tray and run the Bluetooth setup
        5. -
      5. Right click on the Bluetooth icon in the System tray and select Advanced Configuration
        6. -
      6. Click the Accessibility tab -
          -
        1. Check the option “Let other Bluetooth devices discover this computer”
          2. -
        2. Set the option under “Allow” to “All Devices”
          3. -
        -
        7. -
      -

      NOTE The Nokia PC image includes the Microsoft Bluetooth drivers which do not support serial emulation over Bluetooth. You need to download and install the drivers provided by the Bluetooth manufacturer to connect to a device.

      -
      Nokia PC Suite 6.8
      -
        -
      1. Install PC Suite (or later version) -

        Launch the PC Suite installer and follow the onscreen instructions to install the software. When finished, a Get Connected wizard should appear

        -
        2. -
      2. Press Next
        3. -
      3. In the "Select your connection type" window select "Cable Connection" and press Next
        4. -
      4. You will be prompted to connect the phone via the USB cable
        5. -
      5. Connect the phone and continue with onscreen instructions
        6. -
      6. After installation your phone should be listed
        7. -
      7. Click Finish
        8. -
      8. Select PC suite on your phone
        9. -

        The Nokia PC Suite window should appear

        -
      9. Select the Manage Connections icon
        10. -
      10. Uncheck all the connections available
        11. -
      11. Click Ok
        12. -

        PC Suite is now ready to use.

        -
      +

      Once you've setup your environment, its time to verify that the TRK agent is on the phone or target device.

      - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_01.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_01.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_01.htm Tue Apr 13 15:55:45 2010 -0500 @@ -4,34 +4,27 @@ -Debugger Settings +Installing PERL -

      Run Mode On-Device Debugging

      -

      To implement run mode on-device debugging the following tasks need to be completed.

      -
        -
      1. Install device connection software
        2. -
      2. Install Perl
        3. -
      3. Install an SDK
        4. -
      4. Setup environment variables
        5. -
      5. Setup a virtual drive for Techview and Cust Kits
        6. -
      6. Set the default kit in Devices.xml
        7. -
      7. Install the SISX file on the target device
        8. -
      8. Configure TRK connection on the device
        9. -
      9. Create a launch configuration
        10. -
      +

      Installing PERL

      +

      PERL is required for many Symbian OS utilities and commands.

      -

      Install PERL

      +

      Installing PERL

      • Install ActivePERL version 5.6.1 b638

      Software can be downloaded from: http://www.activestate.com/Products/ActivePerl/.

      NOTE Later releases of Perl are not yet supported by the Symbian utilities and can cause unknown compiling errors.

      -
      +
      - +
      Other references
      + + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm Tue Apr 13 15:55:45 2010 -0500 @@ -4,40 +4,58 @@ -Debugger Settings +Installing an SDK -

      Run Mode On-Device Debugging

      -

      To implement run mode on-device debugging the following tasks need to be completed.

      -
        -
      1. Install device connection software
        2. -
      2. Install Perl
        3. -
      3. Install an SDK
        4. -
      4. Setup environment variables
        5. -
      5. Setup a virtual drive for Techview and Cust Kits
        6. -
      6. Set the default kit in Devices.xml
        7. -
      7. Install the SISX file on the target device
        8. -
      8. Configure TRK connection on the device
        9. -
      9. Create a launch configuration
        10. -
      +

      Installing an SDK

      +

      To create projects an SDK must be installed. If more than one SDK is installed one must be specified as the default.

      -

      Install an SDK

      -

      The following SDKs can be downloaded from forum Nokia at: http://www.forum.nokia.com/.

      -
        -
      • Install at least one of the following SDKs:
        • +

        Installing an SDK

        +

        The following SDKs can be downloaded from Nokia at: http://www.forum.nokia.com/.

        +
          +
        1. Install at least one of the following SDKs using the install directions that accompany the SDK: +
            +
          • Series 60 5.0
            • +
          • Qt for S60
            • +
          • Series80
            • +
          • Series 60 cust kits
            • +
          • Techview Development kits
            • +
          +
          2. +
        2. Set the default SDK to use for projects +
            +
          1. In Carbide.c++ +
              +
            1. Click Window > Preferences > Carbide.c++ > SDK Preferences to open the SDK Preferences panel
              2. +
            2. Select the SDK and click SDK Properties to open the SDK Properties dialog
              3. +
            3. Set the Default SDK value to Yes
              4. +
            4. Close all the dialogs
              5. +
            +
            2. +
          2. In a command-line prompt: +
              +
            1. Set the default device devkit by typing on the command line:
              +
              + > devices –setdefault @device id: name
              2. +

              The device id and name can be found in the devices.xml file. For example, for a Techview 9.2 kit you might type
              +
              + > devices –setdefault @ SymbianOS_92_2006_wk40:com.symbian.techview

              +
            2. Now ensure the default device is set by entering:
              +
              + > devices
              3. +
            +
            3. +
          3. Make sure the correct SDK default is set.
            4. +
          +
          3. +
        +
      + +
      Other references
      - - - diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_03.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_03.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_03.htm Tue Apr 13 15:55:45 2010 -0500 @@ -4,25 +4,14 @@ -Debugger Settings +Configuring Environment Variables -

      Run Mode On-Device Debugging

      +

      Configuring Environment Variables

      To implement run mode on-device debugging the following tasks need to be completed.

      -
        -
      1. Install device connection software
        2. -
      2. Install Perl
        3. -
      3. Install an SDK
        4. -
      4. Setup environment variables
        5. -
      5. Setup a virtual drive for Techview and Cust Kits
        6. -
      6. Set the default kit in Devices.xml
        7. -
      7. Install the SISX file on the target device
        8. -
      8. Configure TRK connection on the device
        9. -
      9. Create a launch configuration
        10. -
      -

      Setup Environment Variables

      +

      Configuring Environment Variables

      1. Set EPOCROOT variable
          @@ -50,7 +39,11 @@
      - +
      Other references
      + + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_04.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_04.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_04.htm Tue Apr 13 15:55:45 2010 -0500 @@ -4,26 +4,14 @@ -Debugger Settings +Setup a Virtual Drive for Techview and Cust Kits -

      Run Mode On-Device Debugging

      -

      To implement run mode on-device debugging the following tasks need to be completed.

      -
        -
      1. Install device connection software
        2. -
      2. Install Perl
        3. -
      3. Install an SDK
        4. -
      4. Setup environment variables
        5. -
      5. Setup a virtual drive for Techview and Cust Kits
        6. -
      6. Set the default kit in Devices.xml
        7. -
      7. Install the SISX file on the target device
        8. -
      8. Configure TRK connection on the device
        9. -
      9. Create a launch configuration
        10. -
      +

      Setup a Virtual Drive for Techview and Cust Kits (optional)

      +

      Techview Kits and cust kits have kernel components, kernel extensions and device drivers that are typically built on a virtual drive. So if you want to debug them the debugger will need to load files from the virtual drive that the binaries were built on. If you do not know the virtual drive the kit was built on you should first pick a drive letter randomly.

      Setup a Virtual Drive for Techview and Cust Kits

      -

      Techvew Kits and cust kits have kernel components, kernel extensions and device drivers that are typically built on a virtual drive. So if you want to debug them the debugger will need to load files from the virtual drive that the binaries were built on. If you do not know the virtual drive the kit was built on you should first pick a drive letter randomly.

      1. To subst a drive, type on a command line:
        > subst drive_letter: path_to_kit
        @@ -37,7 +25,11 @@
      2. Make sure when you set up your default SDK in the Carbide IDE that you use the virtual drive.
      - +
      Other references
      + + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_05.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_05.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_05.htm Tue Apr 13 15:55:45 2010 -0500 @@ -4,7 +4,7 @@ -Debugger Settings +Run Mode On-Device Debugging @@ -37,7 +37,7 @@
    4. Make sure the correct default is set.
    - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_06.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_06.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_06.htm Tue Apr 13 15:55:45 2010 -0500 @@ -4,7 +4,7 @@ -Debugger Settings +Run Mode On-Device Debugging @@ -64,7 +64,7 @@
  • Select the green arrow pointing from My Computer to My Device. The SISX file should then be transferred to the device and installed.
    • - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_07.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_07.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_07.htm Tue Apr 13 15:55:45 2010 -0500 @@ -4,7 +4,7 @@ -Debugger Settings +Run Mode On-Device Debugging @@ -70,7 +70,7 @@ - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm Tue Apr 13 15:55:45 2010 -0500 @@ -4,7 +4,7 @@ -Debugger Settings +Run Mode On-Device Debugging @@ -181,7 +181,7 @@

    Figure 9. Debug windows File Transfer pane

    - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Tue Apr 13 15:55:45 2010 -0500 @@ -8,14 +8,12 @@

    Defining a Stop Mode Debug Configuration

    -

    After installing all necessary software such as Perl, JTAG, compilers, Devkits and SDKs and creating your project, you will need to define a Debug launch configuration for your project. For this example, we'll define a Trace32 launch configuration. For new projects that do not have a launch configuration, a New Launch Configuration Wizard will appear and allow you to define settings. You can also cancel the wizard and define a launch configuration from the following instructions.

    +

    After installing all necessary software such as Perl, JTAG, compilers, Devkits and SDKs and creating your project, you will need to define a Debug launch configuration for your project. For this example, we will define a Trace32 launch configuration. For new projects that do not have a launch configuration, a New Launch Configuration Wizard will appear and allow you to define settings. You can also cancel the wizard and define a launch configuration from the following instructions.

    Define a Launch Configuration

      @@ -51,11 +49,11 @@ Explanation - Project + Project

      The project to associate with this debug launch configuration. Click Browse to select a different project.

      - Executable + Executable This is the name of the executable that is linked to the project. Click Browse to select a different executable. @@ -71,17 +69,13 @@ Explanation - - - -

      Trace32 Executable

      + +

      Trace32 Executable

      Specify the path to the Trace32 executable. The default path assumes that the Trace32 executable is installed in the default location: C:\T32\T32marm.exe.

      - - - -

      Trace32 Configuration File

      + +

      Trace32 Configuration File

      Specify the path to the config.t32 file or other custom configuration file. The default path assumes that the Trace32 configuration file is installed in the default location: C:\T32\config.t32.

      For arm11 processors copy the trace32 configuration file for non-ARM11 processor (config_arm11.t32) to your C:\T32 folder and specify it in the edit box.

      You can modify the config.t32 file to support UDP (User Datagram Protocol) connections by adding the following lines:
      @@ -91,21 +85,17 @@ PORT=20000

      - - - -

      + +

      - Trace32 Initialization Script

      + Trace32 Initialization Script

      Specify the path to the initialization cmm file. This script will be run in T32 after connecting to T32. You can specify your own scripts for the targets used.

      - - - -

      + +

      - View messages between Carbide and Trace32

      + View messages between Carbide and Trace32

      Enable to log communications with Trace32 to the console window. @@ -129,27 +119,27 @@ - + -

      Target Initialization File

      +

      Target Initialization File

      Check this box to have the debugger run an initialization script when the debug session starts. For example, if a target device requires initialization for the debugger to be able to read and write memory or registers, you can specify an initialization script here. Click Browse to select a script file using a standard file selection dialog box.

      -

      When using T32, most of the initialization is done in the CMM script file. With other debug protocols you can specify the initialization file, which can be run after connecting to the target.

      +

      When using T32, most of the initialization is done in the CMM script file. With other debug protocols you specify the initialization file, which can be run after connecting to the target.

      - + -

      Memory Configuration File

      +

      Memory Configuration File

      Controls whether the debugger uses a memory configuration file when a debug session starts. The Carbide debugger uses this configuration file to know which memory is accessible, readable, and writable on the target. - + -

      Reset target at the start of each debug session

      +

      Reset target at the start of each debug session

      Forces the Carbide IDE to reset the target at the start of each debug session. This ensures that the debugging session uses the most up-to-date program code. @@ -174,8 +164,7 @@ Explanation - - +

      @@ -185,8 +174,7 @@

      NOTE The address entered in this field must match the start address specified in the source code used to build the Symbian OS ROM image to be debugged. The Start address must match the Download address.

      - - +

      @@ -195,8 +183,7 @@ Select this option to have the debugger halt the program at the address specified in Start Address once the target initialization is done and the OS is downloaded; if the user has chosen to download the OS. You can then step through start-up code or run the target in bare-board mode. - - +

      @@ -206,10 +193,9 @@ Select this option to have the debugger start the code at the address specified in Start Address once the target initialization is done. If you have breakpoints set, the debugger stops at the first breakpoint encountered. You can click the Break button to halt the device. - - + - +

      @@ -218,10 +204,9 @@ Check the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images. In the first text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built. - - + - +

      @@ -230,10 +215,9 @@

      NOTE Always include the epoc32 folder in this path.

      - - + - +

      @@ -244,10 +228,9 @@

      NOTE You cannot perform source-level debugging on components that do not include symbolic information.

      - - + - +

      @@ -258,8 +241,7 @@

      NOTE Selecting this option will affect debugging performance. When the debugger needs to load a module (DLL, EXE, etc.) it will stop the target, read information from it, then restart it.

      - - +

      @@ -270,20 +252,18 @@ Controls the logging of communication with Trace32. Enable to log communications with Trace32 to the console window. - - + -

      Download Address (hex)

      +

      Download Address (hex)

      Enter the physical address in memory at which the debugger should place the ROM image. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x000FFF00 is a valid entry.

      NOTE The address entered in this field must match the download address specified in the source code used to build the Symbian OS ROM image to be debugged. If you leave this field blank, the debugger does not download the ROM image to the device at the beginning of the debug session. The Download address must match the Start address.

      - - + -

      Ask for download at the start of each debug session

      +

      Ask for download at the start of each debug session

      Check this box to have the debugger display a dialog box at the beginning of every debug session that lets you choose whether or not you want the debugger to download the ROM image to the device. diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_disabling.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_disabling.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_disabling.htm Tue Apr 13 15:55:45 2010 -0500 @@ -22,7 +22,7 @@

    - +Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
    License: http://www.eclipse.org/legal/epl-v10.html diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_enabling.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_enabling.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_enabling.htm Tue Apr 13 15:55:45 2010 -0500 @@ -21,7 +21,7 @@
  • The disabled eventpoint icon changes to its original eventpoint icon. The enabled eventpoint icon indicates that the eventpoint will perform its specified action.
    • - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_clear.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_clear.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_clear.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,7 +9,7 @@

    Log Point

    -

    A Log Point logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.

    +

    A Log Point logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.

    Related tasks
    • Setting a Pause Point
      • @@ -24,7 +24,7 @@
    • Click Debug > Clear Eventpoint > Clear Log Point.
      • - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_set.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_set.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_set.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,7 +9,7 @@

      Log Point

      -

      A Log Point logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.

      +

      A Log Point logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.

      Related tasks
      • Setting a Pause Point
        • @@ -34,7 +34,7 @@

        Example use: If you want to display the value of a variable each time some code is executed, set a log point, check the Log Message and Treat as expression boxes and enter the variable name in the edit box, then click OK.

        - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_clear.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_clear.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_clear.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,7 +9,7 @@

        Pause Point

        -

        A Pause Point suspends program execution long enough to refresh debugger data. For example, without setting a pause point, you must wait for the debugger to halt program execution before it can refresh data. Setting a Pause Point, however, lets you pause the debugging session to give the debugger time to refresh the data.

        +

        A Pause Point suspends program execution long enough to refresh debugger data. For example, without setting a pause point, you must wait for the debugger to halt program execution before it can refresh data. Setting a Pause Point, however, lets you pause the debugging session to give the debugger time to refresh the data.

        Related tasks
        • Setting a Log Point
          • @@ -28,7 +28,7 @@

          - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_set.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_set.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_set.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,7 +9,7 @@

          Pause Point

          -

          A Pause Point suspends program execution long enough to refresh debugger data. For example, without setting a pause point, you must wait for the debugger to halt program execution before it can refresh data. Setting a Pause Point, however, lets you pause the debugging session to give the debugger time to refresh the data.

          +

          A Pause Point suspends program execution long enough to refresh debugger data. For example, without setting a pause point, you must wait for the debugger to halt program execution before it can refresh data. Setting a Pause Point, however, lets you pause the debugging session to give the debugger time to refresh the data.

          Related tasks
          • Setting a Log Point
            • @@ -26,7 +26,7 @@

            - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_clear.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_clear.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_clear.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,7 +9,7 @@

            Clearing a Trace Collection

            -

            Clear a Trace Collection eventpoint when you are finished collecting trace data.

            +

            Clear a Trace Collection eventpoint when you are finished collecting trace data.

            Clearing a Trace Collection On Eventpoint

            To clear a Trace Collection eventpoint, follow these steps:

            @@ -19,7 +19,7 @@
          • Click Debug > Clear Eventpoint > Clear Trace Collection On
            • - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_off.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_off.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_off.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,7 +9,7 @@

            Trace Collection Off

            -

            A Trace Collection Off eventpoint stops the collection of trace data. This eventpoint is useful when you want trace collection to stop when program execution reaches a line of source code that you specify.

            +

            A Trace Collection Off eventpoint stops the collection of trace data. This eventpoint is useful when you want trace collection to stop when program execution reaches a line of source code that you specify.

            Setting a Trace Collection Off Eventpoint

            To set a Trace Collection Off eventpoint, follow these steps:

            @@ -18,7 +18,7 @@
          • Click Debug > Set Eventpoint > Set Trace Collection Off
            • - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_on.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_on.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_on.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,16 +9,16 @@

            Trace Collection On

            -

            A Trace Collection On eventpoint starts the collection of trace data. This eventpoint is useful when you want trace collection to start when program execution reaches a line of source code that you specify.

            +

            A Trace Collection On eventpoint starts the collection of trace data. This eventpoint is useful when you want trace collection to start when program execution reaches a line of source code that you specify.

            Setting a Trace Collection On Eventpoint

            -

            To set a Trace Collection On eventpoint, follow these steps:

            +

            To set a Trace Collection On eventpoint, follow these ssteps:

            1. Click the cursor on the line of source code at which you want to set the Trace Collection On eventpoint
            2. Click Debug > Set Eventpoint > Set Trace Collection On
            - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/images/wnd_chooseBaseClass.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/images/wnd_chooseBaseClass.png has changed diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html Tue Apr 13 15:55:45 2010 -0500 @@ -54,6 +54,6 @@ - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/open_log_view.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/open_log_view.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/open_log_view.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,18 +9,20 @@

            Opening a Log View

            -

            Use the Debugger Settings preference panel to enable the message logging option. The Log view records these types of messages for a program during a debugging session:

            +

            Use the Debugger Settings preference panel to enable the message logging option. The Log view records these types of messages for a program during a debugging session:

            • the start of new tasks
            • routine entry and exit
            • Windows: DLL loading and unloading, and debug printf() messages
            -

            Select the Log System Messages option in the Debugger Settings target settings preference panel.

            -

            Select Project > Debug.

            +

            Select the Log System Messages option in the Debugger Settings target settings preference panel.

            +
              +
            • Select Project > Debug
              • +
              -

              The Log view appears. It allows you to select, copy, and save logged text to a file for later analysis.

              +

              The Log view appears. It allows you to select, copy, and save logged text to a file for later analysis.

            - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm Tue Apr 13 15:55:45 2010 -0500 @@ -24,7 +24,7 @@

            Building a Project

              -
            • Right-click the project name in the C/C++ Projects view and select Build Project (Figure 1)
              • +
            • Right-click the project name in the Project Explorer view and select Build Project (Figure 1)

              @@ -39,7 +39,7 @@
          • Click the Build icon in the tool bar (Figure 2) to build the current build configuration
            • -

            +

            Figure 2 - Build icon

            or

            @@ -48,16 +48,16 @@
          • Select a build configuration using the Build icon’s dropdown list in the tool bar (Figure 2)
            -

            Carbide.c++ builds the project. During the build a build dialog will appear on screen and a task bar is shown at the bottom right of the perspective when the build is run in the background. All output as the build progresses is shown in the Console view and all build errors and warnings appear in the Problems view.

            +

            Carbide.c++ builds the project. A build dialog and a task bar appear during a build process. All build output is shown in the Console view while build errors and warnings appear in the Problems view.

            Whether a full build or incremental build is requested, Carbide forwards the request to the SDK make system. The SDK make system determines if anything needs to be - built. So Carbide will always check that makefiles are up-to-date and - check dependencies.

            -

            A project is also built if you make a change to a project and then click Debug. It may be useful to automatically save modified resources before a manual build process by enabling the Save automatically before build option in the Window > Preferences > General > Workspace preference panel.

            + built. Carbide always checks that makefiles are up-to-date and + dependencies present.

            +

            Project is also built if you make a change to it and then click Debug. It may be useful to automatically save modified resources before a manual build process by enabling the Save automatically before build option in the Window > Preferences > General > Workspace preference panel.

            NOTE If you want to turn off building before launching, uncheck the Build (if required) before launching option in the Window > Preferences > Run/Debug > Launching preference panel.

          -

          When performing a build, output is displayed in the Console window. If you do not want to clear the console before each build you need to uncheck the option Always clear console before building in the Build Console panel. This option is enabled by default. You can access this panel by selecting Window > Preferences > C/C++ > Build Console preference panel (figure 2).

          -

          Not clearing the console can be useful when you are performing multiple builds, such as a regular project build, building a project package (.pkg) file, and building a ROM image. For example, if you do not clear the console before each build, then a subsequent build will not overwrite information from a previous build.

          -

          +

          When performing a build, output is displayed in the Console window. If you do not want to clear the console before each build you need to uncheck the option Always clear console before building in the Build Console panel. This option is enabled by default. You can access this panel by selecting Window > Preferences > C/C++ > Build Console preference panel (figure 2).

          +

          Not clearing the console is useful when you are performing multiple builds, such as a regular project build, building a project package (.pkg) file, and building a ROM image. For example, if you do not clear the console before each build, then a subsequent build will not overwrite information from a previous build.

          +

          Figure 4 - Build Console Preference Panel

           

          @@ -77,7 +77,7 @@
        • Build Package (.pkg) File
        • Importing BLD.INF Files
        - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm Tue Apr 13 15:55:45 2010 -0500 @@ -38,7 +38,7 @@ SIS Properties

        Complete the PKG File, and Signing Options settings in the SIS Properties dialog. By default, SIS files are output in the directory of the original SIS file.

        -

        +

        Figure 2 - SIS Properties dialog

        @@ -57,7 +57,7 @@ - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Tue Apr 13 15:55:45 2010 -0500 @@ -18,42 +18,40 @@

      Creating a Default Launch Configuration

      -

      NOTE Carbide.c++ only creates a new default launch configuration when it cannot find one in the project. If the project already contains a launch configuration, Carbide.c++ launches that instead.

      +

      NOTE Carbide only creates a new default launch configuration when it cannot find one in the project. If the project already contains a launch configuration, Carbide launches that instead.

      • Click the Run (Run icon) or Debug (Debug icon) icon in the tool bar

        or

      • Choose Select Run > Run menu option to launch the project or Run > Debug menu option to debug the project
        • -

        Carbide.c++ creates a default launch configuration for the project and begins running or debugging the project. If the project already has a defined launch configuration, clicking Run or Debug uses it instead of creating a new one. There are two possible scenarios when creating a default launch configuration:

        +

        Carbide creates a default launch configuration for the project that is used to run or debug the project. If the project already has a defined launch configuration, clicking Run or Debug uses it instead of creating a new one. There are two possible scenarios when creating a default launch configuration:

          -
        • for emulator targets - an emulator launch configuration is created based on the project settings
          • +
        • for emulator targets - an emulator launch configuration is created based on the project settings
        • for target devices - the New Launch Configuration Wizard appears asking for additional information
      -

      NOTE To see if a project already has a launch configuration, open a Run or Debug window using the Run > Open Run Dialog... or Run > Open Debug Dialog... menu items. - -

      -

      In the event that the default launch configuration settings need to be changed, it is possible to edit them in the Debug window, or create a new launch configuration for the project that deviates from the default settings.

      +

      NOTE To see if a project already has a launch configuration, open a Run or Debug window using the Run > Run As or Run > Debug As menu items.

      +

      In the event that the default launch configuration settings must be changed, edit them in the Debug window, or simply create a new launch configuration for the project that deviates from the default settings.

      Creating a Custom Launch Configuration

      1. Open the Run or Debug launch configuration window
          -
        • Select the Run> Open Run Dialog... or Run > Open Debug Dialog... menu item +
        • Select the Run> Run As or Run > Debug As menu item

          The appropriate Run or Debug launch configuration window appears (Figure 1).

        -

        Undefined launch configuration

        +

        Undefined launch configuration

        Figure 1 - Initial blank Debug launch configuration window

      2. Select a type of launch configuration (for example, Symbian OS Emulation), then click the New launch configuration icon to create a new configuration of that type.

        A new configuration appears in the Configuration list under the appropriate section using the project name and target to create the configuration name.

        -

        NOTE By default, when you click New, the project information is used to fill in the Project and Process to launch text boxes. You normally should not have to edit these for a run/debug a project. If a bld.inf has multiple MMPS then the first executable named in the list of MMP files is used to fill in the executable field. Therefore, for projects with multiple MMPs you may need to change the executable field.

        +

        NOTE Project information is used to fill in the Project and Process to launch text boxes by default when you click New. You should not have to edit these for a normal run/debug project. If a bld.inf has multiple MMP files listed, then the first executable in the list is used to fill in the executable field. Therefore, for projects with multiple MMPs you may need to change the executable field.

        3. -

        New launch configuration

        +

        New launch configuration

        Figure 2 - New launch configuration with name and settings filled in (emulator)

      3. View the information to define the project and executable @@ -94,7 +92,7 @@
      4. Building Projects
      5. Debugging DLLs
    - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_console.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_console.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_console.htm Tue Apr 13 15:55:45 2010 -0500 @@ -24,7 +24,7 @@

    In the Debug window or launch configuration, simply point both the Executable and Remote process to launch options to the application. This launches the application when you start a debug session from the application project.

    -

    +

    Figure 2 - Assign Executable and Remote Process

    Related concepts
    @@ -43,7 +43,7 @@
  • Project Directories
    • - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_search.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_search.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_search.htm Tue Apr 13 15:55:45 2010 -0500 @@ -10,7 +10,7 @@

    Searching for SDKs

    Use the SDK Preferences panel to search for installed Symbian OS SDKs.

    -

    +

    Figure 1. SDK Preferences panel

    Searching for SDKs

    diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_debugging.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_debugging.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_debugging.htm Tue Apr 13 15:55:45 2010 -0500 @@ -10,38 +10,28 @@

    Debugging a Symbian OS Program

    Use the Carbide.c++ debugger to debug a compiled Symbian OS program in an emulator or on-device. The same process works for other emulators and target devices as well.

    -

    NOTE This example uses an emulator. The steps are identical for on-device debugging, although a .sym file is not needed for emulator builds.

    +

    NOTE This example uses the emulator included with the S60 5th Edition SDK. The steps are identical for on-device debugging, although a .sym file is not needed for emulator builds.

    Debugging a Symbian OS program

    -

    NOTE You can only debug compiled programs. Use the Build Project command to compile project sources into a binary file if you do not already have an executable in the project. You will also need a symbolics ( .sym) file for debugging on a target device. Ensure that a .sym file has been created. If you are importing an existing application, you may have to rebuild the application and create a related .sym file. Make sure a .sym file has been created in the output directory.

    +

    NOTE You can only debug compiled programs. Use the Build Project command to compile project sources into a binary file if you do not already have an executable in the project. A symbolics (.sym) file is also required for debugging on a target device. Ensure that a .sym file has been created. If you are importing an existing application, you may have to rebuild the application and create a related .sym file. Make sure a .sym file has been created in the output directory.

      -
    1. Set a breakpoint in the HelloCarbide program
      2. -

      Open the \src\CHelloCarbideAppUI.cpp file and set a breakpoint in the HandleCommandL routine.

      -

      -

      Figure 1 - Breakpoint set in CHelloCarbideAppUI::HandleCommandL routine.

      -
    2. Launch the Carbide.c++ debugger and S60 EPOC Emulator
      3. -

      Start the Carbide debugger which launches the S60 EPOC Emulator and installs the HelloCarbide application. For on-device debugging, your application will be installed on your target device.

      -

      -

      Figure 2 - S60 Emulator launches

      -
    3. Open the Installed directory within the S60 Emulator or your target device
      4. - Use the S60 Emulator controls to locate and open the Installation directory. Select Open from the Options menu (Figure 3). -

      -

      Figure 3 - Open the Installed directory

      -
    4. Launch the HelloCarbide application
      5. -

      Use the S60 Emulator or target device controls to launch the HelloCarbide application (Figure 4). -

      -

      -

      Figure 4 - Launch the HelloCarbide application

      -

      The HelloCarbide application launches (Figure 5).

      -

      -

      Figure 5 - HelloCarbide application running on S60 Emulator

      -
    5. Click the Options soft-key on the S60 Emulator to display the Select menu.
      6. -
    6. Choose the Message menu item and press the Select soft-key to send a message (Figure 6).
      7. -

      -

      Figure 6 - Send Message to HelloCarbide application

      -

      The HandleCommandL breakpoint is hit in the program and control returns to the Carbide.c++ debugger (Figure 7). You can now set additional breakpoints, examine variables, or use the Debug view buttons to control the program.

      -

      -

      Figure 7 - Back in the CHelloCarbideAppUI::HandleCommandL routine

      +
    7. Set a breakpoint in the MyProject program
      8. +

      Open the \src\MyProjectAppUI.cpp file and set a breakpoint in the HandleCommandL routine.

      +

      +

      Figure 1 - Breakpoint set in MyProjectAppUI::HandleCommandL routine.

      +
    8. Launch the Carbide debugger and S60 SDK Emulator
      9. +

      Start the Carbide debugger which launches the S60 SDK Emulator, installs and launches the executable. For on-device debugging, the application is installed on the target device.

      +

      The HelloCarbide application launches (Figure 2).

      +

      +

      Figure 2 - MyProject application running on S60 Emulator

      +

      NOTE For SDKs prior to the S60 5th Edition it may be necessary to locate the installed application and manually launch it in the emulator or on the target device.

      +
    9. Click the Options soft-key on the S60 Emulator to display the Options menu.
      10. +
    10. Choose the Message menu item and press the Select soft-key to send a message (Figure 3).
      11. +

      +

      Figure 3 - Send Message to MyProject application

      +

      The HandleCommandL breakpoint is hit in the program and control returns to the Carbide debugger (Figure 4). You can now set additional breakpoints, examine variables, or use the Debug view buttons to control the program.

      +

      +

      Figure 4 - Back in the CMyProjectAppUI::HandleCommandL routine

    That's it for this basic introduction to debugging with Carbide.c++.

    @@ -55,7 +45,7 @@
  • Building Projects
  • Creating a Launch Configuration
    • - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm Tue Apr 13 15:55:45 2010 -0500 @@ -26,12 +26,12 @@

    An SDK or OS developer kit (DevKit) including:

    • 9.x or higher for Platform Security
    -

    Targets: S60 5th and 3rd Ed., Qt, UIQ

    +

    Targets: S60 5th Ed., Qt

    Debugger: Emulators, on-device debugging

    UI Designer: create graphical interfaces quickly using standard UI components

    -

    Targets: S60 5th and 3rd Ed., Qt, UIQ

    +

    Targets: S60 5th Ed., Qt

    Debugger: Emulators, on-device debugging, device debugging in ROM, kernel debugging

    Performance Investigator: application performance data, memory usage, power usage, button event reporting

    @@ -42,7 +42,7 @@ Hardware
    • x86-based personal computer
      • -
    • 1800MHz
      • +
    • 2GHz
    • 1GB of RAM minimum, recommend 2GB or more
    • CD-ROM drive
    @@ -50,8 +50,8 @@ Operating System -

    Microsoft® Windows® XP (Service Pack 2) recommended, Microsoft® Windows® Vista® supported

    -

    NOTE While Carbide.c++ supports many different OS configurations, only the ones listed here provide for optimal Symbian development.

    +

    Microsoft® Windows® XP (Service Pack 2/3) recommended, Microsoft® Windows® Vista® and Microsoft® Windows® 7 supported

    +

    NOTE While Carbide.c++ supports many different OS configurations, only the ones listed here provide for optimal Symbian development.

    NOTE If you experience any VM issues, see the Tips & Hints page for info on modifying Carbide's default memory setup.

    @@ -63,7 +63,6 @@
  • S60 5th Edition
  • S60 3rd Edition, FP1
  • S60 3rd Edition, MR
    • -
  • S60 3rd Edition
  • Qt @@ -72,12 +71,6 @@
  • Qt SDK for S60
    • -
  • UIQ SDKs (www.uiq.com) -
      -
    • UIQ 3.1
      • -
    • UIQ 3.0
      • -
    -
    • Perl (www.activestate.com) (required) @@ -91,8 +84,8 @@ Disk Space
        -
      • 700 MB for Carbide.c++
        • -
      • Up to 1.5 GB for each S60 SDK installation
        • +
      • 800 MB for Carbide.c++
        • +
      • Up to 2.0 GB for each S60 SDK installation
      @@ -100,7 +93,7 @@ - + \ No newline at end of file diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/p2_available_sw.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/p2_available_sw.png has changed diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/p2_install_details_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/p2_install_details_01.png has changed diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/p2_install_details_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/p2_install_details_02.png has changed diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/p2_review_licenses.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/p2_review_licenses.png has changed diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm Tue Apr 13 15:55:45 2010 -0500 @@ -20,7 +20,7 @@

      Defining a Customized Launch Configuration

        -
      1. Choose the Run > Open Debug Dialog... menu item
        2. +
      2. Choose the Run > Debug As menu item

        3. The Debug window appears.

      3. Select a Configuration type for on-device debugging and click New

        4. Choose the Symbian OS Application TRK or System TRK configuration based on which debug agent is installed on the device, then click New. A new debug launch configuration appears in the Configuration list and the Main tab appears.

        diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm Tue Apr 13 15:55:45 2010 -0500 @@ -43,11 +43,7 @@ -
        Related tasks
        - - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_usb.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_usb.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_usb.htm Tue Apr 13 15:55:45 2010 -0500 @@ -14,42 +14,28 @@
      4. DKU-2
      5. CA-53
    +

    Carbide uses plug-and-play (PnP) to create a remote connection for the phone or target device once it's plugged in. Once a remote connection is created the Remote Connections view appears in Carbide. In addition, the current available connection is shown in the workspace's lower-right trim area.

    +

    +

    Figure 1. Current available connection shown in workspace trim area

    +

    NOTE PC Suite or Ovi Suite must be installed on your PC for the following steps to work.

    Setting up a USB Connection for On-device Debugging

      -
    1. Install the latest USB connectivity software, for example, S60 devices use Nokia PC Suite
      2. -
    2. Connect the USB connectivity cable to your PC and then the target device
      3. -
    3. For S60 devices, select PC-Suite from the USB Mode list when the target device is connected
      4. -
    4. Download the Application TRK or System TRK SISX file to the device
      5. -
    5. On the PC - (optional)
      6. -
    -
      -
        -
      1. Open the Windows Computer Management (Windows XP)
        2. -

        Right-click My Computer and select Manage from the context menu to open the Computer Management window. Select System Tools > Device Manager > Ports (COM & LPT) to display all active ports.

        -
      2. Locate the S60 Phone USB (COMx) item in the list (Figure 2)
        3. -

        -

        Figure 2. Device Manager showing Ports (COM & LPT) section

        -
      3. The USB COM Port number should match the COM port used in the Connections tab of the TRK launch - configuration.
        4. -
      4. Close the Device Manager window
        5. -
      +
    1. Connect the USB connectivity cable to your PC and then the phone or target device
      2. +
    2. On the phone or target device, select PC-Suite from the USB Mode options when asked
      3. +
    3. In Carbide.c++, verify the current available connection is shown in the Remote Connections view or the indicator in the trim area
    Related concepts
    Related references
    -
    Related tasks
    - - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm Tue Apr 13 15:55:45 2010 -0500 @@ -9,13 +9,14 @@

    Installing an On-device Debug Agent

    -

    To use any version of the on-device debug agent on a target device it must be installed. We highly recommend using the On-Device Connections dialog to help connect and verify that the latest version of TRK is installed on the device. Or, to manage this manually, follow the instructions to install the TRK debug agent software using Bluetooth or USB.

    +

    To use any version of the on-device debug agent on a target device it must be installed. We highly recommend using the On-Device Connections dialog to help connect and verify that the latest version of TRK (3.2.6+) is installed on the device, especially to support plug-and-play (PnP) connections.

    +

    Refer to the Bluetooth Connection Setup page for more information on using Bluetooth or the USB Connection Setup page if using USB.

    Related references
    - + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/index.xml --- a/core/com.nokia.carbide.cpp.doc.user/index.xml Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/index.xml Tue Apr 13 15:55:45 2010 -0500 @@ -340,22 +340,10 @@ - - - - - - - - - - - - @@ -473,6 +461,14 @@ + + + + + + + + @@ -568,6 +564,10 @@ + + + + @@ -576,6 +576,7 @@ + @@ -727,6 +728,7 @@ + diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/intro/tutorialsCarbideExtContent.xml --- a/core/com.nokia.carbide.cpp.doc.user/intro/tutorialsCarbideExtContent.xml Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/intro/tutorialsCarbideExtContent.xml Tue Apr 13 15:55:45 2010 -0500 @@ -29,7 +29,7 @@ Learn how create and build an application and debug it on a device using the App TRK on-device debug agent. diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/intro/whatsnew_IntroExt.xml --- a/core/com.nokia.carbide.cpp.doc.user/intro/whatsnew_IntroExt.xml Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/intro/whatsnew_IntroExt.xml Tue Apr 13 15:55:45 2010 -0500 @@ -10,7 +10,7 @@ diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/plugin.xml --- a/core/com.nokia.carbide.cpp.doc.user/plugin.xml Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/plugin.xml Tue Apr 13 15:55:45 2010 -0500 @@ -14,11 +14,23 @@ file="tocRelease.xml" primary="false"/> --> + - + + + + + + + + + + + + @@ -221,13 +233,6 @@ - - - - - - - diff -r 5310aeaa3526 -r e265bbe56eb0 core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml --- a/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Mon Apr 12 14:47:08 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Apr 13 15:55:45 2010 -0500 @@ -2,20 +2,28 @@ - + + + + + + + + + + - - - - - - - + + + + + + @@ -231,6 +239,69 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -260,65 +331,16 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + +