diff -r 2ee12718a766 -r 9b005a8e6778 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 Fri Aug 07 15:50:06 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Mon Aug 10 15:21:12 2009 -0500 @@ -1,72 +1,72 @@ - - -
- - - -This example shows how to create and build an application and debug it on a device using the Application TRK on-device debug agent. The majority of steps are identical to the ones used to create a program and debug in an emulator, with some minor variations.
-In this example we are importing a project called Music, a complex project that includes several EXEs (MusicPlayer, MusicShop, MusicVisualizer). When we import, we select an ARM target.
-NOTE The symbolics are automatically loaded for the binaries that appear in the Executables view.
-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).
-Figure 1 - Launch Types page showing selection
-For this example we select the musicplayer.exe as the main executable.
-Figure 2 - Executable Selection page showing selection
-Figure 3 - TRK Connection Settings page showing selection
----
Figure 4 - TRK Connection Settings page showing selection
-
The SISX file is downloaded and authenticated, then the binaries are installed automatically on the phone.
-At this point you can debug the program in the Debug perspective. Look at the Breakpoints view to verify that the breakpoints set earlier are resolved. In this case, the breakpoint in the MCServer.exe.
-Figure 5 - Debug perspective showing the resolved breakpoint
-Figure 6 - Debug perspective showing the resolved EXE breakpoint
-In addition, you can click the Symbian OS Data View to examine the processes running on the devise during the debug session.
-This example shows how to create and build an application and debug it on a device using the Application TRK on-device debug agent. The majority of steps are identical to the ones used to create a program and debug in an emulator, with some minor variations.
+In this example we are importing a project called Music, a complex project that includes several EXEs (MusicPlayer, MusicShop, MusicVisualizer). When we import, we select an ARM target.
+NOTE The symbolics are automatically loaded for the binaries that appear in the Executables view.
+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).
+Figure 1 - Launch Types page showing selection
+For this example we select the musicplayer.exe as the main executable.
+Figure 2 - Executable Selection page showing selection
+Figure 3 - TRK Connection Settings page showing selection
++++
Figure 4 - TRK Connection Settings page showing selection
+
The SISX file is downloaded and authenticated, then the binaries are installed automatically on the phone.
+At this point you can debug the program in the Debug perspective. Look at the Breakpoints view to verify that the breakpoints set earlier are resolved. In this case, the breakpoint in the MCServer.exe.
+Figure 5 - Debug perspective showing the resolved breakpoint
+Figure 6 - Debug perspective showing the resolved EXE breakpoint
+In addition, you can click the Symbian OS Data View to examine the processes running on the devise during the debug session.
+