Applications Launch Configuration

Launch Configuration	Wizard Pages
Common pages	- Category Type - Launch Type - Build Option Selection - Executable Selection - New Launch Configuration -
Emulation	- Executable Selection - Build Option Selection - New Launch Configuration -
Application TRK and System TRK	- TRK Connection Settings - TRK SIS Selection (Application TRK only) -
Attach to Process	- TRK Connection Settings -
Launch Configuration	Wizard Pages
Common pages	+ Debug As + Launch Types + Build Option Selection + Executable Selection + New Launch Configuration +
Simulator	+ Executable Selection + Build Option Selection + New Launch Configuration +
Application TRK and System TRK	+ TRK Connection Settings + TRK SIS Selection (Application TRK only) +
Attach to Process	+ TRK Connection Settings +

Use the Debug command (

) to execute a program under debugger control using the current launch configuration settings.

Use the Debug command (

) to execute a program under debugger control using the current launch configuration settings.

If this is the first time the program is launched for debugging, a new debug launch configuration is automatically created for you based on current project settings and assigned a name. If a debug launch configuration is already available, the Debug command launches using the last debug launch configuration used with the project.

Launching a Program for Debugging

Click the Debug button () in the C/C++ perspective
Click the Debug button () in the C/C++ perspective

Select Run > Debug from the menu bar

Both of these methods create a new debug launch configuration if none previously existed in the project or uses the last one launched for debugging.

Attaching to a Symbian OS Process

Use the Symbian OS Attach to Process launch configuration to attach the debugger to an already running Symbian OS process or thread on a target device. This is useful for debugging servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate as one example.

You can also attach to a process in the Symbian OS Data view when debugging.

NOTE You cannot attach to a process running on the emulator. It must be a target device running the Symbian OS and the TRK debug agent.

When attempting to find a process the debugger uses the UID3 to locate the process.

Attaching to a Symbian OS Process

Import an executable to import it into the Executables view
Select any project in the workspace or the binary to attach to in the Executables view

In this example, we select the Executables project created when the binary was imported from the Project Explorer view (Figure 1).

Figure 1 - Executables project created when importing an executable

Click Debug () to launch the New Configuration Launch Wizard
Select the Attach to Process Launch Configuration option and fill in the requested information
Click Debug

The Attach to Process window appears. Click a column title to sort the processes in ascending or descending order to help you locate a specific process or use the filter text box to show specific processes.

Figure 2 - Attach to Process window

Select a process, click OK

The Attach to Process window closes. Open a Symbian OS view to show the process and thread information.

NOTE Terminating an Attach to Process session actually kills the process on the device. This means you must restart the process on the device in order to attach to it again.

Related references

Attaching to a Process

Use a Symbian OS Attach to Process launch configuration to attach the debugger to an already running Symbian OS process or thread on a target device. This is useful for debugging DLLs where the main process is unknown or for servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate.

One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the Executables view.

You can also attach to a process in the Symbian OS Data view when debugging.

NOTE You cannot attach to a process running on the emulator. It must be a target device running the Symbian OS and the TRK debug agent.

When attempting to find a process the debugger uses the UID3 to locate the process.

Attaching to any Running Process

In the Executables view, click the Import an executable file icon () to add an executable to the Executables view for debugging. +
The executable added appears in the Project Explorer view under an Executables project. This group includes all executables listed in the Executables view that are not linked to any project in the workspace.
+
+
Figure 1 - Executables list in Project Explorer view
+
NOTE The executable must include symbolics in order for debugging to work.
+
Click Debug () to launch the New Configuration Launch Wizard.

Select the Symbian OS Attach to Process launch configuration option and fill in the requested information.

Attach to Process launch config

Figure 2 - Attach to Process launch configuration

Click Debug.

The Attach to Process dialog appears. Click a column title to sort the processes in ascending or descending order to help you locate a specific process or use the filter text box to show specific processes.

Figure 3 - Attach to Process window

Select a process, click OK.

In this example we've linked the prefs.dll program to the process BlackFlag.exe on the device. The Attach to Process dialog closes. Open the Symbian OS Data view to show the process and thread information.

NOTE Terminating an Attach to Process session actually kills the process on the device. This means you must restart the process on the device in order to attach to it again.

Related references

+ + + + diff -r d8b5c1e3a21e -r a77f12f0a631 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/attach_to_process_launch_config.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/attach_to_process_launch_config.png has changed diff -r d8b5c1e3a21e -r a77f12f0a631 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/attach_to_process_proj_explorer.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/attach_to_process_proj_explorer.png has changed diff -r d8b5c1e3a21e -r a77f12f0a631 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 Tue Aug 31 14:13:15 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Tue Aug 31 16:18:02 2010 -0500 @@ -20,7 +20,7 @@

Creating a Default Launch Configuration

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 () or Debug () icon in the tool bar +
Click the Run () or Debug () 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
If the DLL appears in the Executables view it can be debugged. Just set breakpoints inside the DLL sources before you start the debug session. The next time the project is debugged, the DLL is loaded and made available for debugging.

-
NOTE Breakpoints inside a DLL will not be resolved until the DLL is loaded into memory by the calling binary.
+
NOTE Breakpoints inside a DLL are not resolved until the DLL is loaded into memory by the calling binary.

If the DLL is not built by the project you can import the DLL by clicking the Import an executable file icon () in the Executables view. Then, set your breakpoints and start the debug session.

NOTE The symbolics are automatically loaded for the binaries that appear in the Executables view.

Set breakpoints in the project source files

In this example we will set one breakpoint in two different EXEs. The first is set in the file called MCEngine.cpp (MCServer.exe) and the second is set in MPlayerAppUI.cpp (MusicPlayer.exe).

Click the Debug icon () to launch the New Launch Configuration wizard +
Click the Debug icon () to launch the New Launch Configuration wizard
1. Select the Application TRK Launch Configuration from the Launch Types page, then click Next

	Import an executable file	Click to import an executable not in the workspace into the executables list.	Click to select and import an executable not in the workspace into the executables list.
@@ -96,6 +96,8 @@ Other references Debug perspective + Auto-Targeting of Executables + Attaching to a Process Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. License: http://www.eclipse.org/legal/epl-v10.html diff -r d8b5c1e3a21e -r a77f12f0a631 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm Tue Aug 31 14:13:15 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm Tue Aug 31 16:18:02 2010 -0500 @@ -9,12 +9,12 @@ Debugging a Program - Use the Debug command () to execute a program under debugger control using the current launch configuration settings. + Use the Debug command () to execute a program under debugger control using the current launch configuration settings. If this is the first time the program is launched for debugging, a new debug launch configuration is automatically created for you based on current project settings and assigned a name. If a debug launch configuration is already available, the Debug command launches using the last debug launch configuration used with the project. Launching a Program for Debugging - Click the Debug button () in the C/C++ perspective + Click the Debug button () in the C/C++ perspective or Select Run > Debug from the menu bar Both of these methods create a new debug launch configuration if none previously existed in the project or uses the last one launched for debugging. diff -r d8b5c1e3a21e -r a77f12f0a631 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_debugger_to_process.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_debugger_to_process.htm Tue Aug 31 14:13:15 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,46 +0,0 @@ - - - - - - -Attaching to a Symbian OS Process - - - - Attaching to a Symbian OS Process - - Use the Symbian OS Attach to Process launch configuration to attach the debugger to an already running Symbian OS process or thread on a target device. This is useful for debugging servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate as one example. - You can also attach to a process in the Symbian OS Data view when debugging. - NOTE You cannot attach to a process running on the emulator. It must be a target device running the Symbian OS and the TRK debug agent. - When attempting to find a process the debugger uses the UID3 to locate the process. - - Attaching to a Symbian OS Process - - Import an executable to import it into the Executables view - Select any project in the workspace or the binary to attach to in the Executables view - In this example, we select the Executables project created when the binary was imported from the Project Explorer view (Figure 1). - - Figure 1 - Executables project created when importing an executable - Click Debug () to launch the New Configuration Launch Wizard - Select the Attach to Process Launch Configuration option and fill in the requested information - Click Debug - The Attach to Process window appears. Click a column title to sort the processes in ascending or descending order to help you locate a specific process or use the filter text box to show specific processes. - - Figure 2 - Attach to Process window - Select a process, click OK - The Attach to Process window closes. Open a Symbian OS view to show the process and thread information. - NOTE Terminating an Attach to Process session actually kills the process on the device. This means you must restart the process on the device in order to attach to it again. - - - - Related references - - Debug View - Debug Window - Symbian OS View - - Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. License: http://www.eclipse.org/legal/epl-v10.html - - - diff -r d8b5c1e3a21e -r a77f12f0a631 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_to_process.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_to_process.htm Tue Aug 31 16:18:02 2010 -0500 @@ -0,0 +1,50 @@ + + + + + + +Attaching to a Process + + + + Attaching to a Process + + Use a Symbian OS Attach to Process launch configuration to attach the debugger to an already running Symbian OS process or thread on a target device. This is useful for debugging DLLs where the main process is unknown or for servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate. + One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the Executables view. + You can also attach to a process in the Symbian OS Data view when debugging. + NOTE You cannot attach to a process running on the emulator. It must be a target device running the Symbian OS and the TRK debug agent. + When attempting to find a process the debugger uses the UID3 to locate the process. + + Attaching to any Running Process + + In the Executables view, click the Import an executable file icon () to add an executable to the Executables view for debugging. + The executable added appears in the Project Explorer view under an Executables project. This group includes all executables listed in the Executables view that are not linked to any project in the workspace. + + Figure 1 - Executables list in Project Explorer view + NOTE The executable must include symbolics in order for debugging to work. + + Click Debug () to launch the New Configuration Launch Wizard. + Select the Symbian OS Attach to Process launch configuration option and fill in the requested information. + + Figure 2 - Attach to Process launch configuration + Click Debug. + The Attach to Process dialog appears. Click a column title to sort the processes in ascending or descending order to help you locate a specific process or use the filter text box to show specific processes. + + Figure 3 - Attach to Process window + Select a process, click OK. + In this example we've linked the prefs.dll program to the process BlackFlag.exe on the device. The Attach to Process dialog closes. Open the Symbian OS Data view to show the process and thread information. + NOTE Terminating an Attach to Process session actually kills the process on the device. This means you must restart the process on the device in order to attach to it again. + + + Related references + + Debug View + Debug Window + Symbian OS View + Debugging DLLs with any Process + + Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. License: http://www.eclipse.org/legal/epl-v10.html + + + diff -r d8b5c1e3a21e -r a77f12f0a631 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/attach_to_process_launch_config.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/attach_to_process_launch_config.png has changed diff -r d8b5c1e3a21e -r a77f12f0a631 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/attach_to_process_proj_explorer.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/attach_to_process_proj_explorer.png has changed diff -r d8b5c1e3a21e -r a77f12f0a631 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 Tue Aug 31 14:13:15 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Tue Aug 31 16:18:02 2010 -0500 @@ -20,7 +20,7 @@ Creating a Default Launch Configuration 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 () or Debug () icon in the tool bar + Click the Run () or Debug () 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 diff -r d8b5c1e3a21e -r a77f12f0a631 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 31 14:13:15 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_dlls.htm Tue Aug 31 16:18:02 2010 -0500 @@ -14,7 +14,7 @@ If the DLL appears in the Executables view it can be debugged. Just set breakpoints inside the DLL sources before you start the debug session. The next time the project is debugged, the DLL is loaded and made available for debugging. - NOTE Breakpoints inside a DLL will not be resolved until the DLL is loaded into memory by the calling binary. + NOTE Breakpoints inside a DLL are not resolved until the DLL is loaded into memory by the calling binary. If the DLL is not built by the project you can import the DLL by clicking the Import an executable file icon () in the Executables view. Then, set your breakpoints and start the debug session. diff -r d8b5c1e3a21e -r a77f12f0a631 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Tue Aug 31 14:13:15 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Tue Aug 31 16:18:02 2010 -0500 @@ -22,7 +22,7 @@ NOTE The symbolics are automatically loaded for the binaries that appear in the Executables view. Set breakpoints in the project source files In this example we will set one breakpoint in two different EXEs. The first is set in the file called MCEngine.cpp (MCServer.exe) and the second is set in MPlayerAppUI.cpp (MusicPlayer.exe). - Click the Debug icon () to launch the New Launch Configuration wizard + Click the Debug icon () to launch the New Launch Configuration wizard Select the Application TRK Launch Configuration from the Launch Types page, then click Next diff -r d8b5c1e3a21e -r a77f12f0a631 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview_trk.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview_trk.htm Tue Aug 31 14:13:15 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview_trk.htm Tue Aug 31 16:18:02 2010 -0500 @@ -32,7 +32,7 @@ At this point you can open sources files from the Executables view or project view in order to set breakpoints. Related tasks - Attaching to a Symbian OS Process + Attaching to a Symbian OS Process Related references diff -r d8b5c1e3a21e -r a77f12f0a631 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 Tue Aug 31 14:13:15 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm Tue Aug 31 16:18:02 2010 -0500 @@ -14,7 +14,7 @@ Symbian OS Appication TRK— used to run or debug applications on a target device using the Application TRK on-device debug agent. Application TRK is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian OS installation file to the phone and install it prior to launching. Symbian OS System TRK (not available in the Developer Edition) —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. - By default, you can click the Debug icon () in the toolbar to launch the New Launch Configuration Wizard. This creates a launch configuration for the project based on project information and any additional input required, like COM port selection. It is the recommended method for creating new launch configurations. Or, use the Debug window to create a customized launch configuration. + By default, you can click the Debug icon () in the toolbar to launch the New Launch Configuration Wizard. This creates a launch configuration for the project based on project information and any additional input required, like COM port selection. It is the recommended method for creating new launch configurations. Or, use the Debug window to create a customized launch configuration. Figure 1. Debug launch configuration for on-device debugging (Application TRK shown) diff -r d8b5c1e3a21e -r a77f12f0a631 core/com.nokia.carbide.cpp.doc.user/index.xml --- a/core/com.nokia.carbide.cpp.doc.user/index.xml Tue Aug 31 14:13:15 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/index.xml Tue Aug 31 16:18:02 2010 -0500 @@ -13,7 +13,7 @@ - + @@ -491,7 +491,7 @@ - + diff -r d8b5c1e3a21e -r a77f12f0a631 core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml --- a/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Aug 31 14:13:15 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Aug 31 16:18:02 2010 -0500 @@ -31,6 +31,7 @@ + @@ -278,7 +279,7 @@ --> - + @@ -323,9 +324,11 @@ + + + + - -

Auto-Targeting of Executables

Debugging DLLs

Other References

Table 1 Build Configuration items

Starting a session