Emulation Debugging

# HG changeset patch # User fturovic # Date 1280862325 18000 # Node ID a1e1c11d5a44d0bd39ce6d0a5ff7a0a419372b3d # Parent b0ec278f91fa3a9b3de7a8cbef4ae2f34c71bd00 broken links fixed diff -r b0ec278f91fa -r a1e1c11d5a44 core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Tue Aug 03 13:32:44 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Tue Aug 03 14:05:25 2010 -0500 @@ -23,7 +23,7 @@

11563 - The Build Project dialog now also shows the project name.

v2.7.0

11222 - You can now disable device discovery in the Remote Connection view to avoid conflicts between different connection protocols within Carbide.

+ - - Follow these steps to create a Symbian OS project and debug it using the S60 EPOC Emulator. - + Follow these steps to create and debug a Symbian project and using an emulator. using the S60 EPOC Emulator. diff -r b0ec278f91fa -r a1e1c11d5a44 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 Tue Aug 03 13:32:44 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/common_debug_actions.htm Tue Aug 03 14:05:25 2010 -0500 @@ -9,7 +9,7 @@

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:

Start the debugger
Step into, out of, or over routines
Build Targets
Carbide Macros
Context menu support
Dependency Tracking
Emulation Debugging
External Builds Support
Launch Configurations

The Carbide.c++ tools are built on top of the Eclipse and CDT open source projects (eclipse.org). Carbide can use several popular software configuration management systems including:

Apache Subversive
CVS (plug-in included with Carbide)
CVS (plug-in included with Carbide)
Git
IBM Rational Clearcase
Mercurial

Emulation Debugging

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

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

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

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

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

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

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

Related tasks

- - -

Emulation Debugging

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

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

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

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

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

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

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

Related tasks

Debugging Applications
Debugging DLLs

+ + +

N-Gage Projects

Watchpoints Overview

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:

Related references

Variables View
Setting Variable Formats
Opening a Variables View
Showing Global Variables
Showing Global Variables

Workspace Information

A workspace is the default place to store and create resources like projects, folders, and files. These are then presented to the user in a perspective which enables the presentation and manipulation of the stored resources.

When Carbide is launched it asks for a workspace to open (Figure 1). As you can have multiple workspaces, all independent from each other, choosing the workspace containing the projects to work on is important. Projects within a workspace are shown in the Carbide workbench within the Project Explorer and C/C++ Project views. When you create a new project it is automatically added to the currently open workspace. You can import existing projects into a workspace from INF files.

Workspace Launcher dialog

Figure 1. Workspace Launcher dialog

WARNING Bld.inf imported projects are not copied, so do not delete the contents when deleting the project.

- - Specify Trace32 configuration information. - - - - Specify TRK connection information. diff -r b0ec278f91fa -r a1e1c11d5a44 core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/properties_breakpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/properties_breakpoints.htm Tue Aug 03 13:32:44 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/properties_breakpoints.htm Tue Aug 03 14:05:25 2010 -0500 @@ -12,7 +12,7 @@

Use the Properties for Breakpoint window to examine and modify a specific breakpoints properties. By setting certain options its possible to create both conditional and temporary breakpoints.

The pages available include:

Actions - define one or more specific breakpoint actions like playing a sound or showing an alert message to this breakpoint
Actions - define one or more specific breakpoint actions like playing a sound or showing an alert message to this breakpoint
Common - shows common information including the class, breakpoint type, file location, and other attributes associated with the breakpoint.

diff -r b0ec278f91fa -r a1e1c11d5a44 core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Tue Aug 03 13:32:44 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Tue Aug 03 14:05:25 2010 -0500 @@ -9,7 +9,7 @@

Enabling, Disabling and Removing Breakpoints

Use the Toggle Breakpoint command (Ctrl+Shift+B) to set a regular breakpoint in an Editor or Disassembly view. Only a single breakpoint can exist on a source code line. A regular breakpoint suspends program execution when it is hit, or executed, during a debug session. The debugger executes the line of source code that contains the regular breakpoint, then opens the Debug perspective to allow examination and modification.

If a regular breakpoint already exists on the selected line, as indicated by the enabled breakpoint badge () in the marker bar, use Toggle Breakpoint to remove the breakpoint.

Enabling and Disabling breakpoints

Once a source line is selected in an editor or Disassembly view, the methods of toggling breakpoints to be enabled of disabled include:

diff -r b0ec278f91fa -r a1e1c11d5a44 core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/setting_watchpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/setting_watchpoints.htm Tue Aug 03 13:32:44 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/setting_watchpoints.htm Tue Aug 03 14:05:25 2010 -0500 @@ -37,8 +37,8 @@

Check the appropriate access type to trigger the watchpoint for the specified memory location. This setting is shown as a unique icon in the Breakpoints view next to the listed watchpoint. The following list shows the resolved version of the icons used to indicate the type of watchpoint set:

Read only ()
Write only ()
Read/Write ()
Write only ()
Read/Write ()

diff -r b0ec278f91fa -r a1e1c11d5a44 core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/watchpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/watchpoints.htm Tue Aug 03 13:32:44 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/watchpoints.htm Tue Aug 03 14:05:25 2010 -0500 @@ -10,7 +10,7 @@

Watchpoints Overview

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

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

An enabled watchpoint has a non-gray icon () indicating that program execution halts when encountered.
A disabled watchpoint displays a gray icon () indicating that program execution will not stop when encountered.

In addition, you can use these types of watchpoints:

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

A watchpoint is equivalent to a memory breakpoint.

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

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

All set watchpoints appear in the Breakpoints view list.

Related concepts

Breakpoints
Breakpoints

Related tasks

Related references

Symbian OS Crash Debugger — used to launch an interactive command-line session with the Symbian OS crash debugger when the device crashes
Symbian OS Emulation — used to run or debug executables on an emulator.
Symbian OS System TRK — used to run or debug applications or ROM code on a target device using the System TRK on-device debug agent. System TRK is an application that runs on reference boards and prototype phones and allows you to debug your executables. The debugger will download files to the phone prior to launching.
Symbian OS Trace32 — is an external debugger that the Carbide debugger communicates with, to debug any Symbian OS module on a target using a JTAG connection.

Other references

Attach to Process
Emulation
System TRK
Trace32

Other references

Emulation Debugger page (Emulation)
Run-mode Debugger page (Application TRK)
Stop-mode Debugger page (System TRK, Trace32, Attach to Process)
Stop-mode Debugger page (System TRK, Attach to Process)

Emulation Debugger page

The Symbian OS Emulation launch configurations the Debugger page to specify entry point breaks and which logs to output to the Console view.

Stop-mode Debugger page

In stop-mode launch configurations like System TRK, Trace32, and Attach to Process, use the Startup Options to attach to a target and debug or run from the specified start address. Then use Target Options to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session.

In stop-mode launch configurations like System TRK, and Attach to Process, use the Startup Options to attach to a target and debug or run from the specified start address. Then use Target Options to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session.

Figure 3 - Debugger page showing stop-mode options

Table 3. Debugger page — stop-mode options

Emulation Main page (Emulation)
Run-mode Main page (Application TRK)
Stop-Mode Main page (System TRK, Trace32)
Stop-Mode Main page (System TRK)

Emulation Main page

The Symbian OS Emulation launch configuration uses the Main page to define the process to be launched by the emulator.

Stop-mode Main page

The Symbian OS System TRK and Trace32 launch configurations uses the Main page to defines the project and the executable to launch on the target device.

The Symbian OS System TRK launch configurations uses the Main page to defines the project and the executable to launch on the target device.

Figure 3. Main page (TRACE32 shown)

Figure 3. Main page

Table 3. Stop-mode Main page — items

System TRK Launch Configuration (Stop-mode)

Select the Symbian OS System TRK launch configuration provides C/C++ stop-mode debug options that use a JTAG interface when a Symbian OS Trace32 launch configuration is created. The settings included in these launch configuration are a combination of Carbide, CDT, and Eclipse options.

Select the Symbian OS System TRK launch configuration provides C/C++ stop-mode debug options that use a JTAG interface when a Symbian OS launch configuration is created. The settings included in these launch configuration are a combination of Carbide, CDT, and Eclipse options.

If the New Launch Configuration Wizard was used to create the System TRK launch configuration no changes are usually needed. To modify the launch configuration settings, select the Run > Debug As menu option to open the Debug dialog. Select the System TRK configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.

Figure 1. System TRK launch configuration in the Debug dialog

Trace32 Launch Configuration

Select the Symbian OS Trace32 launch configuration to debug any Symbian OS module on a target using a JTAG connection. The external Trace32 debugger communicates with the Carbide debugger and enables stop mode debugging of the target device.

If the New Launch Configuration Wizard was used to create a Trace32 launch configuration no changes are usually needed. To modify the launch configuration settings, select the Run > Debug As menu option to open the Debug dialog. Select the Trace32 configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.

Figure 1. Trace32 launch configuration in the Debug dialog

The Trace32 launch configuration panes include:

The Main tab defines the project to be launched. Enter the name of the project in the Project field, and the executable name in the Executable field.
The Connection tab
The Debugger tab defines debug configurations, such as entry point to begin debugging and target options.
The ROM Image tab allows you to define startup options and ROM image download information.
The Executables tab allows you to specify which executables that you want to debug that are part of the project.
The Source tab (standard CDT page) defines the location of source files used to display source when debugging an application. By default, these settings are derived from the associated project's build path. You may override these settings here.
The Common tab (standard CDT page) defines general information about the launch configuration. You may choose to store the launch configuration in a specific file.

Other references

Launch Configuration Overview

Related tasks

Related References

What's new
User notes
K nown issues
Bug Fixes
Technical support

Using Soft Attach for On-Device Debugging

You can debug hardware via Trace32 using the soft attach option. This enables you to debug an image flashed to ROM or on a memory card. Soft attach includes all the capabilities fo Stop-mode debugging but can't debug any code loaded before the OS is booted.

NEEDS REWRITING

You can debug hardware via TCF using the soft attach option. This enables you to debug an image flashed to ROM or on a memory card. Soft attach includes all the capabilities fo Stop-mode debugging but can't debug any code loaded before the OS is booted.

There are several components that must be provided to the debugger so that it can communicate with the attached hardware device. They are:

Config_carbide.t32 - a required configuration file used to configure Carbide for soft attach debugging
.cmm file - you must select the correct .cmm script file for the hardware otherwise it will not initialize properly and the debugger will be unable to communicate. The .cmm script files are located in the <Carbide>\plugins\com.nokia.carbide.cpp.support_2.0.x.xxx\Symbian_Support\Trace32\cmm_scripts directory.
+
.cmm file - you must select the correct .cmm script file for the hardware otherwise it will not initialize properly and the debugger will be unable to communicate. The .cmm script files are located in the <Carbide>\plugins\com.nokia.carbide.cpp.support_3.0.x.xxx\Symbian_Support\TCF\cmm_scripts directory.

Also, if there is a specific .cmm file for the device, like H2 or H4, especially if it includes _attach in the name, choose that version over the others to do soft attach on the hardware.
.log file - you must have a valid .log file for the ROM image in order to debug the image
Click Run > Debug to launch the New Launch Configuration Wizard
In the Launch Types page
1. Select the Trace32 Launch Configuration
2. Select the TCF Launch Configuration
3. Click Next
In the Symbian ROM Image Settings page
1. Enter the path to the Trace32 Initialization Script .cmm file
2. Enter the path to the TCF Initialization Script .cmm file
3. Select the Target Processor
4. Click Next
diff -r b0ec278f91fa -r a1e1c11d5a44 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 Tue Aug 03 13:32:44 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Tue Aug 03 14:05:25 2010 -0500 @@ -7,7 +7,13 @@ @@ -49,11 +55,11 @@

+ + Trace32 Initialization Script

+ + View messages between Carbide and Trace32

Trace32

Trace32 Initialization Settings
Symbian ROM Image Settings

Attach to Process

TRK Connection Settings

If you checkmark Advanced settings, the Debug dialog appears instead of launching the project. This enables you to make additional changes to the new launch configuration before starting the debug session. By design and intent, this should seldom be required for the initial launch.

Figure 8 - New Launch Configuration page

Trace32 Initialization Settings

Use the Trace32 Initialization Settings page to specify the initialization script and target processor of the target device.Enter the Trace32 Initialization Script and choose the Target Processor, then click Next.

This page only appears when creating a Trace32 launch configuration.

Figure 9 - Trace32 Initialization Settings page

Symbian ROM Image Settings

Use the Symbian ROM Image Settings page to specify the method of debugging, the start address, and the ROM Image and Log File locations.

This page appears when creating a Trace32 launch configuration.

Figure 10 - Symbian ROM Image Settings page

Other references

Launch Configuration

Debug Configurations Window

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

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

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

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

Table 1. Debug Configuration window — common items

Filter Deleted/Unavailable Projects
Filter Configuration Types
Apply Window Working Set(s)
Filtering Preferences...
Filtering Preferences...

Other references

New Emulation Program Output Console
New TRK Program Output Console
New TRK Communications Log Console
New Trace32 Communications Log Console
New Symbian Rom Log Console
New Emulator Output Console
CVS

Debug process or thread

Click the Debug button to attach to the process and debug the selected process or thread. Or right-click an item and choose Debug. This applies to both TRK (run mode) and Trace32 (stop mode).

Click the Debug button to attach to the process and debug the selected process or thread. Or right-click an item and choose Debug. This applies to both TRK (run mode) and TCF (stop mode).

Explanation

Project

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

Executable

This is the name of the executable that is linked to the project. Click Browse to select a different executable.

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:
@@ -85,17 +95,21 @@ PORT=20000

- 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

Enable to log communications with Trace32 to the console window.

Break at entry point

Break at entry point

When checked, break at the specified entry point entered in the text field. For .EXE targets, the default entry point is set to E32Main. By default, the Break at entry point option is unchecked for all other target types.

Target Processor

Target Processor

+ -

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 specify the initialization file, which can be run after connecting to the target.

- + -

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

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

Default Instructon Set

Default Instructon Set

Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. This can happen at addresses for which we have no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code. The options are:

Auto (examine code at current PC location)

+ -

- - Start Address

+ + Start Address

Enter the physical address in memory where the Symbian OS start code begins execution. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x8000000 is a valid entry.

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.

- + -

- - Debug from Start address

+ + Debug from Start address

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

- Run from start address

+ Run from start address

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

- - Symbian ROM Log file

+ + Symbian ROM Log file

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

- Symbian OS Kit EPOC32 Directory

+ Symbian OS Kit EPOC32 Directory

Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory.

NOTE Always include the epoc32 folder in this path.

- + -

- - Log unresolved modules

+ + Log unresolved modules

Check this box to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session.

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

- + -

- + - Debug non-XIP Executables

+ Debug non-XIP Executables

Check this box to debug a project, or a dynamically loaded module, that is loaded from NAND-Flash or other removable media (MMC, memory stick, etc.) at run time and executed in RAM. Use this option to debug modules that work fine when executed in place as part of the ROM image, but sometimes fail when placed in NAND-Flash or other removable media.

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.

- + -

- - - Symbian ROM Image

+ + + Symbian ROM Image

Controls the logging of communication with Trace32. Enable to log communications with Trace32 to the console window. - + -

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

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 b0ec278f91fa -r a1e1c11d5a44 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_dlls.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_dlls.htm Tue Aug 03 13:32:44 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_dlls.htm Tue Aug 03 14:05:25 2010 -0500 @@ -4,7 +4,7 @@ -Importing Executables for Debugging +Debugging DLLs diff -r b0ec278f91fa -r a1e1c11d5a44 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_multiple_projects.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_multiple_projects.htm Tue Aug 03 13:32:44 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_multiple_projects.htm Tue Aug 03 14:05:25 2010 -0500 @@ -21,9 +21,7 @@

Related Tasks

Importing Executables for Debugging
Working with SDKs

Working with SDKs

NOTE You cannot debug ROM DLLs using Application TRK.

In Trace32 you must specify the ROM log file in the ROM Image tab of the Trace32 launch configuration

Other references

Importing Executables for Debugging
Symbian OS Trace32 Support

Symbian OS Trace32 Support

Importing a Symbian Executable

Use the File > Import > Symbian OS Executable feature to import an executable into the Executables view and debug it. This is useful when the binary is not part of any project in the workspace. An example of this may be a library that is called from an mmp file. The binary must be built with the same build configuration as the current build configuration that is being used (compiler must be the same).

NOTE You also need the symbolics (.sym) file for debugging ARM build configurations.

NOTE Binaries built by the project can be debugged by selecting executables to debug in the Executable tab of the launch configuration Debug window.

To import a Symbian Executable

Select the File > Import... menu item

The Import window appears (Figure 1).

Figure 1 - Import window

Expand Symbian OS and select Symbian OS Executable in the list, then click Next

The Import Executable window appears (Figure 2).

Enter the executable name in the Select Executable field or click Browse to locate the executable

Use the Select executable field to choose a single executable or Search directory field to select one or more Symbian executables to import from the specified directory.

Figure 2 - Import Executable window

Click Finish

The IDE imports the Symbian executable and displays it in the Executables view (figure 3).

Figure 3 - Executables view showing executable and source files

The new project is listed under the Project Explorer view, as shown in Figure 4.

Figure 4 - New executable listed

Related concepts

Projects
Project Resources

Related tasks

Related references

Project Directories
Executables view