Concepts in Symbian OS Eclipse Development User Guide

# HG changeset patch # User fturovic # Date 1249937379 18000 # Node ID 939a4e7e4597c5696bf0005921135d8fb1b12f85 # Parent 9b005a8e6778888800ccfb642de7853e28157081 lets try telling mercurial that the files are really really gone diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/concepts/index.html --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/index.html Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,44 +0,0 @@ - -Concepts in Symbian OS Eclipse Development User Guide - - - -

Concepts

- - -

- This section of the User Guide provides an overview of the main concepts in - Eclipse to create and build programs for Symbian OS. -

- The Symbian OS plug-ins are a set of Eclipse plug-ins that provide project, - SDK and build support for Symbian OS developers. The plug-ins extend the - functionality provided by Eclipse and the C/C++ Development Toolkit (CDT). -

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

- The following topics discuss these concepts in more detail: -

- - - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/bkpt_toggle_breakpoint_off.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/bkpt_toggle_breakpoint_off.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/bkpt_toggle_breakpoint_on.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/bkpt_toggle_breakpoint_on.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_watchpoint_both_resolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_watchpoint_both_resolved.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_watchpoint_both_unresolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_watchpoint_both_unresolved.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_watchpoint_read_unresolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_watchpoint_read_unresolved.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_watchpoint_write_enabled_resolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_watchpoint_write_enabled_resolved.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_watchpoint_write_unresolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_watchpoint_write_unresolved.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/AIFCmplrOptions.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/AIFCmplrOptions.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/AIFDef-Step1.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/AIFDef-Step1.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/AIFDef-Step2.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/AIFDef-Step2.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/AIFDef-Step3.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/AIFDef-Step3.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/AIFInterface.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/AIFInterface.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/AddBMPWithMask.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/AddBMPWithMask.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/AddBMPWithoutMask.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/AddBMPWithoutMask.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/BuildOptions-OLD.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/BuildOptions-OLD.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/BuildOptions.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/BuildOptions.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/MBMCmplrOptions.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/MBMCmplrOptions.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/MBMDef-New.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/MBMDef-New.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/MBMDef-Step1.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/MBMDef-Step1.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/MBMDef-Step2.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/MBMDef-Step2.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/MBMDef-Step3.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/MBMDef-Step3.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/MBMInterface.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/MBMInterface.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/NewMMPWizard.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/NewMMPWizard.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/NewProject.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/NewProject.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/Preferences.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/Preferences.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/RscCompilerOptions.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/RscCompilerOptions.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/SDKPreferences.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/SDKPreferences.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/borrow_license_file.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/borrow_license_file.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/buildconfigprops.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/buildconfigprops.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/carbide_image.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/carbide_image.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/carbide_image_sm.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/carbide_image_sm.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/carbide_image_sm.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/carbide_image_sm.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/export_makefiles_7.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/export_makefiles_7.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/export_scalable_8.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/export_scalable_8.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/icon_build_config_active.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/icon_build_config_active.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/icon_build_config_available.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/icon_build_config_available.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/icon_build_configurations.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/icon_build_configurations.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/icons/carbide.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/icons/carbide.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/icons/carbide_hov.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/icons/carbide_hov.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/icons/debug_codebug_instance_icon.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/icons/debug_codebug_instance_icon.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/icons/debug_debugger_instance_icon.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/icons/debug_debugger_instance_icon.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/icons/debug_thread_instance_icon.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/icons/debug_thread_instance_icon.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/icons/icon_build_target.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/icons/icon_build_target.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/icons/icon_launch_config.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/icons/icon_launch_config.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/import2.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/import2.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/import6.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/import6.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/importMMP1.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/importMMP1.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/importMMP2.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/importMMP2.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/install_license_file.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/install_license_file.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/navigatorview.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/navigatorview.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/ncp_logo.jpg Binary file core/com.nokia.carbide.cpp.doc.user/html/images/ncp_logo.jpg has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/newclassmenu.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/newclassmenu.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/newclassmenu1.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/newclassmenu1.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/proj_prefs_binary_parser.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/proj_prefs_binary_parser.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/proj_prefs_build_settings.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/proj_prefs_build_settings.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/proj_prefs_build_steps.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/proj_prefs_build_steps.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/proj_prefs_error_parser.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/proj_prefs_error_parser.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/related_concepts.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/related_concepts.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/select_license_file.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/select_license_file.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/step3.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step3.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/test_license_file.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/test_license_file.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/tur_images/option_text_encoding.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/tur_images/option_text_encoding.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/tur_images/panel_debug_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/tur_images/panel_debug_debugger.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/tur_images/panel_debug_x86_exceptions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/tur_images/panel_debug_x86_exceptions.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/update1.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/update1.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/update2.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/update2.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/updateMMPQuestion.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/updateMMPQuestion.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/view_build_config_change.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/view_build_config_change.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/view_build_configs.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/view_build_configs.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/view_build_configs_show.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/view_build_configs_show.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/view_license_file.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/view_license_file.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/views/wnd_edit_shared_value.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/views/wnd_edit_shared_value.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/views/wnd_tmp_default_values.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/views/wnd_tmp_default_values.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/wnd_add_bitmaps.png Binary file core/com.nokia.carbide.cpp.doc.user/html/images/wnd_add_bitmaps.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/images/workbench.gif Binary file core/com.nokia.carbide.cpp.doc.user/html/images/workbench.gif has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/bld_config_sos_apptrk_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/bld_config_sos_apptrk_01.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/bld_config_sos_apptrk_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/bld_config_sos_apptrk_02.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/build_target_only.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/build_target_only.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_breakpoints_view.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_breakpoints_view.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_registers_view.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_registers_view.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_variables_view.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_variables_view.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/debug_context_menu.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/debug_context_menu.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/icon_project_file_link.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/icon_project_file_link.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/new_launch_config_wiz1.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/new_launch_config_wiz1.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_ROM_log.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_ROM_log.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_emulator_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_emulator_debugger.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_run_mode_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_run_mode_debugger.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_stop_mode_rom_image.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_stop_mode_rom_image.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_createsis.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_createsis.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_connection.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_connection.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_debugger.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_exe.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_exe.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_image.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_image.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_main.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_main.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_romlog.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_romlog.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_common.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_common.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_debugger.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_main.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_main.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_source.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_source.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_common.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_common.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_connection.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_connection.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_debugger.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_image.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_image.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_main.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_main.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_romlog.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_romlog.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_source.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_source.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_emulator_main.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_emulator_main.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_env.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_env.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_makesis.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_makesis.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_aif_compiler_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_aif_compiler_01.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_mbm_compiler_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_mbm_compiler_01.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_mif_compiler_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_mif_compiler_01.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_common.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_common.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_connection.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_connection.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_debugger.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_exes.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_exes.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_file_transfer.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_file_transfer.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_installation.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_installation.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_source.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_source.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/perspective_prefs.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/perspective_prefs.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/project_updater.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/project_updater.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/select_folder.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/select_folder.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_restart_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_restart_btn.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_resume_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_resume_btn.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_into_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_into_btn.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_over_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_over_btn.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_return_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_return_btn.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_suspend_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_suspend_btn.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_terminate_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_terminate_btn.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_mifdef_editor.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_mifdef_editor.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_remote_connections2.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_remote_connections2.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_sos_processes.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_sos_processes.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_variables.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_variables.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_app_trk_launch_config.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_app_trk_launch_config.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_breakpoint_actions_pref.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_breakpoint_actions_pref.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_debug_stop_mode_overview.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_debug_stop_mode_overview.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_edit_mifdef_icon.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_edit_mifdef_icon.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_exe_actions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_exe_actions.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_log_actions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_log_actions.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_mifdef_wizard.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_mifdef_wizard.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_on_device_setup_install_trk.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_on_device_setup_install_trk.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_pause_actions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_pause_actions.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_properties_cpp_build.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_properties_cpp_build.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_skip_actions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_skip_actions.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_sound_actions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_sound_actions.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_stop_mode_overview.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_stop_mode_overview.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/app_trk_installation.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/app_trk_installation.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,71 +0,0 @@ - - - - - - -Installation Pane - - - -

Installation Pane

The Debug or launch configuration windows Installation pane specifies the .sis file to install on the target device when using Application TRK. This is required when using the TRK debug agent with 9.x based SDK’s.

Figure 1 - Debug windows Installation pane

Table 1. Installation pane —items

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

Item	Explanation
Installation file -	Enter the complete path to the .sis or .pkg file to install on the target device or click Browse to use the standard file selection dialog. -
Download directory	The directory on the target device to download the file into before installing it. The default directory value is C:\data\.
Install each launch even if installer file has not changed	Enable this option to force an update of the installed file even if no changes have been detected. This ensures a clean program install for each debug session.
Do not show installer UI on the phone	Use this option to specify if the installer UI on the target device is shown when installing the file. Disabling this option may require interaction with the installer UI on the target device, slowing down the install process. The default setting is on.
Install to drive	A list of common drives where files may be installed to. The default drive setting is C.

- -

To access the Installation Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click Installer tab

The Installation pane appears (Figure 1).

Common concepts

Common references

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_debugger.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_debugger.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,73 +0,0 @@ - - - - - - -Debugger Pane - - - -

Debugger Pane

The Debug/Run windows Debugger pane provides control entry point breaks and which consoles are active to show logs.

Figure 1 - Debug windows Debugger tab

Table 1. Debugger pane —items

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

Item	Explanation
Break at entry point	Select to halt program execution at a specified - function or address. Enter the desired function - name or address in the corresponding field. If you - enter an address, ensure that it is correct and within - your program.
View program output	Enable to direct standard output messages to the Emulation Program Output Console in the Console view. - NOTE In the epoc.ini file the option LogToFile must also be set to 1.
View emulator output	Enable to output emulator messages to the Emulator Output Console in the Console view. - NOTE In the epoc.ini file the option LogToDebugger must also be set to 1.
View Windows system messages	Enable to output Windows system messages to the Windows System Messages Console in the Console view.

- -

To access the Debug window

Select the Run > Debug... menu item

The Debug window appears.

Select a Configuration setting
Click Debugger tab

The Debugger pane appears (Figure 1).

Common concepts

About the Debugger

Common tasks

Debugging a Program (Example)
Creating a Launch Configuration

Common references

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_exceptions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_exceptions.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,59 +0,0 @@ - - - - - - -x86 Exceptions Pane - - - -

x86 Exceptions Pane

The Debug/Run windows x86 Exceptions pane lists all the exceptions that the debugger is able to catch. If you want the debugger to catch all the exceptions, enable all of the options in this view. However, if you prefer to handle only certain exceptions, enable only those options that reflect the exceptions you prefer to handle.

Figure 1 - x86 Exceptions pane

Table 1. x86 Exceptions pane —items

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

Item	Explanation
Check All	Enables catching all exceptions.
Clear All	Disables catching all exceptions.

To access the x86 Exceptions pane

Select the Run > Run... or Run > Debug... menu item

The Debug window (Figure 1) appears.

Select a Configuration setting
Click x86 Exceptions tab

The x86 Exceptions pane appears.

Common concepts

About the Debugger

Common tasks

Debugging a Program (Example)
Creating a Launch Configuration

Common references

- - - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_main.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_main.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,52 +0,0 @@ - - - - - - -Main Pane (Emulator) - - - -

Main Pane (Emulator)

The emulator Main pane defines the process to be launched by the emulator.

The behavior that occurs when launching a debug session varies based upon the SDK. Normally, starting a debug session launches the emulator (epoc.exe) and you must then navigate to your application and open it. However, starting a debug session for an .exe file will, in most cases, launch the .exe directly. This starts the emulator and then opens your application automatically. Note that some SDKs do not support this behavior. In those cases you must still open your application in the emulator manually.

Figure 1 - Debug windows emulator's Main tab

Table 1. Emulator Main pane —items

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

Item	Explanation
Project	The project to associate with this debug launch configuration. Click Browse to select a different project.
Process to launch	The path to the emulator or executable to launch. For Symbian OS 9.1 the emulator path is required. For Symbian OS 9.2 and later the path to the executable should be used. Click Browse to select a different emulator.

- -

To access the Main Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS System emulator configuration in the Configurations list
Click Main tab

The Main pane appears (Figure 1).

Other references

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_overview.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,35 +0,0 @@ - - - - - - -Emulator Overview - - - -

Emulator Overview

The Debug or launch configuration window provides C/C++ emulator debug options when a Symbian OS Emulation launch configuration is created. The settings included in the Symbian OS Emulation launch configuration are a combination of Carbide, CDT, and Eclipse options. The tabs in the window include:

The Main tab defines the project to be launched. Enter the name of the project containing the class to launch in the project field, and the executable name in the the Executable field and the emulator or host application in the Emulator or host application field.
The Arguments tab (standard CDT page) defines the arguments to be passed to the application and to the virtual machine (if any). You can also specify the working directory to be used by the launched application.
The Environment tab (standard CDT page) defines the environment variable values to use when running or debugging a program. By default, the environment is inherited from the Eclipse runtime. You may override or append to the inherited environment.
The Debugger tab provides common debugger options for the project.
The Executables tab allows you to specify which executables are debugged by your project.
The x86 Exceptions tab lists all the x86 exceptions that the debugger can catch.
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 and specify which perspectives become active when the launch configuration is launched.

Figure 1 - Debug or launch configuration window

Other references

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_connection.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_connection.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,81 +0,0 @@ - - - - - - -Connection Pane - - - -

Connection Pane

The Connection pane specifies the method used to transfer files to the target device. Once a Serial Port type is chosen, the remaining options contain default values for the specific connection type. Users can change these remaining options to match the target device's communication specifications.

Figure 1 - Debug windows Connection pane

Table 1. Connection pane —items

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

Item	Explanation
Serial Port	Select the serial port option to use for this launch or launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again. Note that for USB and BT can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device. - If you are using a USB connection, the connected phone's name should appear in the menu to help identify which port is being used.
Baud Rate	Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps).
Data Bits	Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8.
Parity	Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None.
Stop Bits	Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 1.
Flow Control	Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None.

- -

To access the Connection Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click Connection tab

The Connection pane appears (Figure 1).

Common concepts

Common tasks

Common references

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_executables.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_executables.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,73 +0,0 @@ - - - - - - -Executables Pane - - - -

Executables Pane

The Executables pane specifies which executables to debug with your project based on the chosen rule. The Executables pane gives you project level control over the executables associated with it. The pane shows all the executables in the workspace or those imported into the Executables view from outside the workspace that can be debugged by this project. See the Executables view for information on controlling executables from the workspace.

Figure 1 - Debug windows Executables pane

Table 1. Executable pane —items

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

Item	Explanation
Load symbols for these executables and target them for debugging	Select the rule which govern the executable support used by this project for debugging purposes. The options include: - - Executables in the workspace from this SDK — shows all executables in the workspace built using the specified SDK. This is the default setting. - Executables built by this project — shows only the executables built by this project using the specified SDK - Executables selected below — shows only the executables chosen by the user. Initial list display uses the All Executables listing. - All executables (slows launch) — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. - -
Executables list	Shows all the executables associated with this project.
Add...	Opens the Select an executable file dialog which can locate and select executable files and add them to the project's executables list.
Select All	Enables all the executables in the list for debugging.
Unselect All	Disables all the executables in the list from debugging.

To access the Executables Pane

Select the Run > Open Debug Dialog... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click Executables tab

The Executables pane appears (Figure 1).

Common concepts

Common references

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_file_transfer.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_file_transfer.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,85 +0,0 @@ - - - - - - -TRK File Transfer Pane - - - -

File Transfer Pane

The File Transfer pane displays an auto-populated list of files for System TRK that the IDE transfers to the target device at the start of each launch. Users can add, edit, or delete files in the list. By default, any file added is automatically checked for downloading to the device. Users can uncheck a file to remove it from the download list without removing the file itself. Any missing files are marked with a warning icon and a message appears describing the issue making it easy to see potential file problems prior to attempting a download.

System TRK users can use this panel to download any type of file, like bitmaps, HTML, sounds, and more, to the phone and applicable to Application TRK for transfering any files outside of the installation file.

Figure 1 - Debug windows File Transfer pane

Table 1. File Transfer pane —items

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

Item	Explanation
File transfer list	The File transfer list displays the project files that are moved to the target device for launch and debugging purposes. It contains these columns: - - Enabled—a checkmark indicates that the IDE should transfer the specified file to the target directory. If unchecked, do not transfer the file. - File to transfer—the path and filename to a file on the host machine to be transfered - Target path—the path to the target directory where transfered files are placed on the device -
Add	Click to add a file to the file transfer list.
Edit...	Click to edit the selected file in the file transfer list.
Remove	Click to remove the selected file from the file transfer list.
Select All	Click to select all the files in the file transfer list.
Deselect All	Click to unselect all the files in the file transfer list.

- -

To access the File Tansfer Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click File Transfer tab

The File Transfer pane appears (Figure 1).

Common concepts

Common tasks

Common references

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_debugger.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_debugger.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,133 +0,0 @@ - - - - - - -Debugger panes for TRK - - - -

Debugger panes for TRK

The Debug/Run windows Debugger panes for TRK provides control over entry points, message handling, and instruction set default settings.

Different options are available in the Debugger pane based on the type of TRK launch configuration, including:

Run mode debugging
Stop mode debugging

Run-mode Debugger pane

In run-mode you can control message handling and instruction sets.

Figure 1 - Debug windows Debugger pane for run mode debugging

Table 1. Debugger pane — run-mode options

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

Item	Explanation
Break at entry point -	When checked, break at the specified entry point entered into 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.
View program output	When checked, show the contents of any program output in the TRK Progam Output Console in a Console view.
View messages between Carbide and debug agent	When checked, show the communications between Carbide and the target device in the TRK Communication Log Console of the Console view. - NOTE You can pin the TRK Communication Log view so that it does not lose focus.
Message retry delay (ms)	Enter the delay time in milliseconds (ms) between 100 and 10000 the debugger should wait for a response. The default Message Retry Delay value is 2000.
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. The options are: - - Auto (examine code at current PC location) - ARM (32-bit) - THUMB (16-bit) - - By default the Instruction Set option uses ARM 32-bit.

Stop-mode Debugger pane

In stop-mode 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 2 - Debug windows Debugger pane for stop mode debugging

Table 2. Debugger pane — stop-mode options

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

Item	Explanation
Break at entry point	When checked, break at the specified entry point entered into 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.
Soft attach	Enable the Soft attach option to attach a debug session to a target and debug from the specified start address instead of the target's default start address. When enabled the downloaded image option is ignored.
Debug from start address	Enable the Debug from start address option to debug from the target's default start address.
Run from start address	Enable the Run from start address option to run from the target's default start address.
Start address (hex)	Enter in hexidecimal format (0x0) the starting address to use during the 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.
Target Processor	A drop down with a list of all supported processors. The process selection should help in determining the memory model. This will in turn help determine the base address and the offsets for the Symbian OS kernel aware information.
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 like Sophia, you can 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.

- -

To access the Debugger Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click Debugger tab

The Debugger pane appears (Figure 1).

Common concepts

Common references

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_main.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_main.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,62 +0,0 @@ - - - - - - -Main Pane - - -

Main Pane

The Main pane defines the project and the process to launch on the target device.

Figure 1 - Debug windows Main pane

Table 1. Main pane —items

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

Item	Explanation
Project	The project to associate with this launch configuration. Click Browse to select a different project.
Remote process to launch	The absolute path of the remote executable to launch on the target device. The binary to debug may be stored on one of several memory locations, the most common are: - - RAM (default) — programs running in RAM are launched from c:\sys\bin\ - ROM — programs running in ROM are launched from z:\sys\bin\ - Memory cards — programs running on a memory card are launched from e:\sys\bin\ - - In the event a program is not launching, verify that the path is correct for the memory location where the binary resides. -

Item

Explanation

Project

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

Remote process to launch

The absolute path of the remote executable to launch on the target device. The binary to debug may be stored on one of several memory locations, the most common are:

RAM (default) — programs running in RAM are launched from c:\sys\bin\
ROM — programs running in ROM are launched from z:\sys\bin\
Memory cards — programs running on a memory card are launched from e:\sys\bin\

In the event a program is not launching, verify that the path is correct for the memory location where the binary resides.

- -

To access the Main Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click Main tab

The Main pane appears (Figure 1).

Common concepts

Common references

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/run_mode_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/run_mode_overview.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,42 +0,0 @@ - - - - - - -Run-mode Overview - - - -

Run-mode Overview

The Debug or launch configuration window provides C/C++ debugger options for on-device debugging. On-device debugging uses a program called Terminal Resident Kernel (TRK) to communicate between Carbide and the device. On-device debugging is supported by creating one of the following debug launch configurations:

Symbian OS Application TRK—supports application debugging only
Symbian OS System TRK—supports both application and limited ROM debugging (not available in the Developer Edition)

The settings included in the TRK launch configurations are a combination of Carbide, CDT, and Eclipse options. Once a suitable Symbian OS debug launch configuration is defined the tabs in the window include:

The Main tab defines the project to be launched. Enter the name of the project containing the class to launch in the project field, and the executable name in the Executable field and the remote process to launch on the device.
The Arguments tab (standard Eclipse page) defines any arguments to be passed to the process to launch.
The Debugger tab provides common debugger options for the project.
The Connection tab specifies the method used to transfer files to the target device. This is where you specify the COM port if the connection is via Bluetooth or USB.
The File Transfer tab displays a list of files to transfer to the target device at the start of each launch. This is used primarily by System TRK to transfer files to a phone for debugging.
The Installation tab (shown in Application TRK only) defines where programs are installed on the target device. This is where you specify the SIS file to be uploaded for Application TRK.
The Executables tab allows you to specify which executables within your project to debug.
The ROM Log tab (shown in System TRK only) specifies where the ROM log file is stored and the Epoc32 directory.
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 and specify which perspectives become active when the launch configuration is launched.

Figure 1 - Debug/Run window for on-device debugging (Application TRK version)

Other references

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/stop_mode_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/stop_mode_overview.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,33 +0,0 @@ - - - - - - -Stop-mode Overview - - - -

Stop-mode Overview

The Debug or launch configuration window provides C/C++ stop-mode debug options that use a JTAG interface when a Symbian OS Sophia or Trace32 launch configuration is created. The settings included in these launch configuration are a combination of Carbide, CDT, and Eclipse options. The tabs in the window include:

The Main tab defines the project to be launched. Enter the name of the project containing the class to launch in the project field, and the executable name in the Executable field to launch on the device.
The Connection tab specifies the method used to transfer files to the target device.
The Debugger tab provides control over common Carbide.c++ debugger capabilities.
The ROM Image tab allows you to define startup options and ROM image download information.
The Executables tab allows you to specify which executables within your project to debug.
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 and specify which perspectives become active when the launch configuration is launched.

Figure 1 - Debug or launch configuration window for stop mode debugging

Other references

- - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/stop_mode_rom_image.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/stop_mode_rom_image.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,73 +0,0 @@ - - - - - - -ROM Image pane - - - -

ROM Image pane

Use the ROM Image tab to define startup options and ROM image download information.

Figure 1 - ROM Image pane in launch configuration

Table 4. Launch configuration window—ROM Image tab items

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

Item	Explanation
Parse Rom Log File	Check this option to parse the ROM log file.
Symbian Rom Log File	Enter or browse to the Rom log file that is generated when the Symbian OS image is built. This is necessary for debugging any Symbian OS module.
Symbian Epoc32 Directory	Enter or browse to the epoc32 directory for the Symbian OS kit that is being targeted for debugging. This is necessary for the debugger to resolve the full paths for each module in the log file since the log file does not contain the full paths.
Log unresolved modules	Check this option to log unresolved modules. If the actual binary in the log file doesn’t exist on the PC, then a warning message will be logged in a Rom Log console window.
Debug non-XIP executables	Check this option to target non-XIP executables. This allows the debugger to target a non-XIP module whenever it’s loaded.
Download Rom Image	Check this box to enable downloading.
Symbian Rom Image	Enter or browse to the Symbian OS image (.img file) that will be downloaded onto the target at the specified download address.
Download Address (hex)	Specify the address where the image is to be downloaded. This address is target-specific. The address should be in hexadecimal format with the 0x prefix.
Same as start address	Check this option to make the download address the same as the start address.
Ask for download at the start of each debug session	Select this option to prompt you to download the image at the start of the debug session.

Other references

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/sys_trk_rom_log.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/sys_trk_rom_log.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,47 +0,0 @@ - - - - - -ROM Log page - - - -

ROM Log page

Use the ROM Log page to specify where the ROM log file is stored and the Epoc32 directory.

Figure 1. ROM Log page

Table 1. ROM Log page—items

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

Item	Explanation
Parse Rom Log File	Activate 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.
Symbian Rom Log File	In the Symbian Rom Log File 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 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	Activate the Log unresolved modules option 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.

Related tasks

Stop Mode On-Device Debugging Preconditions

- - - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/view_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_debug.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,111 +0,0 @@ - - - - - - -Debug View - - - -

Debug View

The Debug view shows the target debugging information in a tree hierarchy. The items that appear there include:

Launch instance () - launch configuration name and type
Debugger instance () - debugger name and state
Executable instances () - other executables called by the launch instance
Thread instance () - thread number and state
Stack frame reference () - displays stack frame number, function, filename, and file line number when symbols are available and stack frame number, memory address, and filename when symbols are not available

NOTE The number beside the thread label is a reference counter, not a thread -identification number (TID).

The CDT displays stack frames as child elements. It displays the reason for the suspension beside the thread, (such as end of stepping range, breakpoint hit, and signal received). When a program exits, the exit code is displayed.

In addition to controlling the individual stepping of your programs, you can also control the debug session. You can perform actions such as terminating the session and stopping the program by using the debug launch controls available from Debug view. See Table 1 for details.

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

Figure 1 - Debug view

Table 1 Debug view—items

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

Item	Icon	Explanation
Resume		Click to perform these tasks: - - Continue execution up to the next breakpoint, watchpoint, or eventpoint - Run the program until it exits - Continue execution of a currently stopped program -
Suspend		Click to stop (pause) program execution.
Terminate		Click to terminate program execution.
Disconnect		Detaches the debugger from the selected process (useful for debugging attached processes). - NOTE After detaching the debugger from an on-device process, closing TRK on the device will also close the process.
Remove All Terminated		Clears all terminated processes in Debug view.
Restart		Returns the debugger to the beginning of the program and begins execution again. This behavior is equivalent to killing execution, then starting a new debugging session.
Step Over		Click to execute the current line, including any routines, and proceed to the next statement.
Step Into		Click to execute the current line, following execution inside a routine.
Step Return		Click to continue execution to the end of the current routine, then follow execution to the routine’s caller.
Instruction Stepping Mode		Activate to enable instruction stepping mode to examine a program as it steps into disassembled code.

Related concepts

Breakpoints

Related tasks

Related references

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_Trace32_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_Trace32_config.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,297 +0,0 @@ - - - - - - -Trace32 Support - - - -

Symbian OS Trace32 Support

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.

Launch configurations define a collection of settings used to tell the debugger how to start a debug session. The launch configuration panes for creating a Trace32 stop mode debug launch configuration are described below. Figure 1 is an example of the Trace32 Debug launch configuration window and the related panes accessible in a tabbed format. Click Debug after all the preference panels have been set. The Debug window closes and the Carbide.c++ debugger begins a debugging session using the new configuration. The next time you click the Debug icon, this debug launch configuration is used to start a debug session.

To open the Debug window

Select the Project in the C/C++ Project view that you want to debug
Select the Run > Debug... menu item to display the Debug launch configuration window (figure 1)
Define a debug launch configuration to communicate with the protocol interface

The panes include:

The Main tab (Figure 1) 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 (Figure 2) defines the Trace32 executable, configuration file and initialization script.
The Debugger tab (Figure3) defines debug configurations, such as entry point to begin debugging and target options.
The ROM Image tab (Figure 4) allows you to define startup options and ROM image download information.
The Executables tab (Figure 5) allows you to specify which executables that you want to debug that are part of the project.
The Source tab (Figure 6) (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 (Figure 7) (standard CDT page) defines general information about the launch configuration. You may choose to store the launch configuration in a specific file.

Main

Figure 1 - Trace32 Launch Configuration Settings - Main Tab

Table 1. Debug Launch configuration window—Main tab items

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

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

Connection

Figure 2 - Trace32 Launch Configuration Settings - Connection Tab

Table 2. Launch configuration window—Connection tab items

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

Item	Explanation
Trace32 Executable	Enter or browse to the Trace32 executable to be launched for debugging. By default, it will be set to c:\t32\t32marm.exe. The default installation path is c:\t32.
Trace32 Configuration File	Enter or browse to the Trace32 Configuration File. The default configuration file is a Carbide specific T32 config file (config_carbide.t32). Default location is - C:\Program Files\Nokia\Carbide.c++ v2.0.x\plugins\com.nokia.carbide.cpp.support_ - <version>\Symbian_Support\Trace32\ - You can modify the config_carbide.t32 file to support UDP (User Datagram Protocol) connections by adding the following lines: - -RCL=NETASSIST -PACKLEN=1024 -PORT=20000
Trace32 Initialization Script	Enter or browse to the Trace32 initialization cmm script file. This script will be run in Trace32 after connecting to Trace32. Users are expected to have their own scripts for the targets they are using. The cmm files are provided here for H2 and H4 boards: - C:\Program Files\Nokia\Carbide.c++ v2.0.x\plugins\com.nokia.carbide.cpp.support_ - <version>>\Symbian_Support\Trace32\cmm_scripts\H2 & H4
View Messages between Carbide and Trace32	The View Messages between Carbide and Trace32 check box allows you to specify whether or not the debug protocol messages between Carbide and T32 should be logged in a T32 Communication Log console window.

Debugger

Figure 3 - Trace32 Launch Configuration Settings - Debugger Tab

Table 3. Launch configuration window—Debugger tab items

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

Item	Explanation
Break at entry point	Select the check box and specify an entry point in the text box if you want the debugger to break at an entry point in the program being debugged. The default is set to E32Main since most applications entry point is E32Main. But you can specify a function name in the program being debugged.
Soft attach	Select to attach to a target without restarting the target device. This is very handy when the device uses flash, memory cards, or other external media for booting purposes and when it's not possible to configure the device to restart by the debugger. With soft attach, the debugger doesn't change the state of the target device. The debugger halts the target after attaching to the target to show the current PC location. User can preform normal debugging operations from then onwards.
Debug from start address	Select this option to stop the target at the start address once the target initialization is done and the OS is downloaded; if you have chosen to download the OS.
Run from start address	Select this option to run the target from the start address once the target initialization is done.
Start Address (hex)	Specify the memory address that the Carbide debugger will use to set the program counter to start the target. This is typically the start address of the Symbian OS.
Reset target at the start of each debug session	Select this check box to reset the target at the start of each debug session. For Trace32, the reset is typically done as part of the CMM script file. - Consult board specifications to determine if resetting is necessary.
Target Processor	Select a target processor from the drop down list of all supported processors. By default the field is set to Generic. When you select a processor, Carbide determines whether the debugger provides ARMV5 or ARMV6 support.
Target Initialization File	Select the check box and enter or browse to the target initialization file. Typically, this initialization file is used to initialize the target after connecting. When using Trace32, the initialization is done in the CMM script file.
Memory Configuration File	Select the check box and enter or browse to the memory configuration file. The Carbide debugger uses this configuration file to determine which memory is accessible, readable, and writable on the target.
Default Instruction set	The following options are available: - - Auto (examine code at current PC location) - Arm (32 bit) - Thumb (16 bit) - - Arm is the default. It is used by the debugger to determine the processor mode when it cannot be determined otherwise. This can happen at addresses for which there is no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code.

ROM Image

Figure 4 - Trace32 Launch Configuration Settings - ROM Image Tab

Table 4. Launch configuration window—ROM Image tab items

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

Item	Explanation
Parse Rom Log File	Check this option to parse the ROM log file.
Symbian Rom Log File	Enter or browse to the Rom log file that is generated when the Symbian OS image is built. This is necessary for debugging any Symbian OS module.
Symbian Epoc32 Directory	Enter or browse to the epoc32 directory for the Symbian OS kit that is being targeted for debugging. This is necessary for the debugger to resolve the full paths for each module in the log file since the log file does not contain the full paths.
Log unresolved modules	Check this option to log unresolved modules. If the actual binary in the log file doesn’t exist on the PC, then a warning message will be logged in a Rom Log console window.
Debug non-XIP executables	Check this option to target non-XIP executables. This allows the debugger to target a non-XIP module whenever it’s loaded.
Download Rom Image	Check this box to enable downloading.
Symbian Rom Image	Enter or browse to the Symbian OS image (.img file) that will be downloaded onto the target at the specified download address.
Download Address (hex)	Specify the address where the image is to be downloaded. This address is target-specific. The address should be in hexadecimal format with the 0x prefix.
Same as start address	Check this option to make the download address the same as the start address.
Ask for download at the start of each debug session	Select this option to prompt you to download the image at the start of the debug session.

Executables

Figure 5 - Trace32 Launch Configuration Settings - Executables Tab

Table 5. Executable pane —items

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

Item	Explanation
Load symbols for these executables and target them for debugging	Select the rule which govern the executable support used by this project for debugging purposes. The options include: - - Executables in the workspace from this SDK — shows all executables in the workspace built using the specified SDK. This is the default setting. - Executables built by this project — shows only the executables built by this project using the specified SDK - Executables selected below — shows only the executables chosen by the user. Initial list display uses the All Executables listing. - All executables (slows launch) — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. -
Executables list	Shows all the executables associated with this project.
Add...	Opens the Select an executable file dialog which can locate and select executable files and add them to the project's executables list.
Select All	Enables all the executables in the list for debugging.
Unselect All	Disables all the executables in the list from debugging.

Source

Figure 6 - Trace32 Launch Configuration Settings - Source Tab

Table 6. Launch configuration window—Source tab items

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

Item	Explanation
Source Lookup Path	Allows you to add locations to search for source files. You can arrange the list by selecting the type of source path and clicking Up and Down buttons. Select a type of source and click Remove button to delete the item from the list.
Search for duplicate source files on the path	Enable this option to search for duplicate source files on source paths listed.

Common

Figure 7 - Trace32 Launch Configuration Settings - Common Tab

Table 7. Launch configuration window—Common tab items

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

Item	Explanation
Save As	Allows you to save the launch configuration as a file local to the project or as shared file. For a shared file you can enter or browse to a folder within an existing project directory.
Display in favorites menu	Select menu for launch configuration to appear.
Console Encoding	Select the character set to use to display information in the console window.
Standard Input and Output	Allocate input and output to console and/or specified file. If a file is selected, you can select Append option to append data to selected file.
Launch in background	Enable this option to launch debug operation in a background process.

Related concepts

Launch Configurations
About the Debugger

Related tasks

Creating a Launch Configuration

Related references

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_sophia_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_sophia_config.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,301 +0,0 @@ - - - - - - -Sophia Support - - - -

Symbian OS Sophia Target Interface Support

Launch configurations define a collection of settings used to tell the debugger how to start a debug session. The launch configuration panes for creating a Sophia (STI) stop mode debug launch configuration are described below. Figure 1 is an example of the STI Debug launch configuration window and the related panes accessible in a tabbed format.

To open the Debug window

Select the Run > Debug... menu item

The Debug window (Figure 1) appears.

The panes include:

The Main tab (Figure 1) 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 (Figure 2) defines the Sophia Target Interface, EJ_Debug type, and JTAG TCLK Frequency.
The Debugger tab (Figure3) defines debug configurations, such as entry point to begin debugging, target options, and instruction set.
The ROM Image tab (Figure 4) allows you to define startup options and ROM image and ROM log file download information.
The Executables tab (Figure 5) allows you to specify which executables that you want to debug that are part of the project.
The Source tab (Figure 6) (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 (Figure 7) (standard CDT page) defines general information about the launch configuration. You may choose to store the launch configuration in a specific file.

Main

Figure 1 - Sophia (STI) Launch Configuration Settings - Main Tab

Table 1. Debug Launch configuration window—Main tab items

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

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

Connection

Figure 2 - Sophia Launch Configuration Settings - Connection Tab

Table 2. Launch configuration window—Connection tab items

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

Item	Explanation
Sophia Target Interface Location	Enter or browse to the Sophia interface (WTI.dll) to be launched for debugging. By default, it will be set to C:\CarbideIF_ARM\WTI.dll. If default file does not exist then an error message will appear.
EJ_Debug Type	Sophia Systems' EJ-Debug is a compact, USB-powered JTAG emulator. Select the EJ_Debug type. Options include: - - Auto (automatically detects target CPU) - ARM9 (target CPU) - ARM11 (target CPU) - ARM9_11 (target CPU) - ARM7_9_11 (target CPU) -
JTAG TCLK Frequency	Select the JTAG TCLK frequency. Options include: - - Auto - 33 MHz - 16 MHz - 8 MHz - 500 KHz -
View Messages between Carbide and STI	The View Messages between Carbide and STI check box allows you to specify if the debug protocol messages between Carbide and STI should be logged in a Communication Log console window.

Debugger

Figure 3 - Sophia Launch Configuration Settings - Debugger Tab

Table 3. Launch configuration window—Debugger tab items

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

Item	Explanation
Break at entry point	Select the check box and specify an entry point in the text box if you want the debugger to break at an entry point in the program being debugged. The default is set to E32Main since most applications entry point is E32Main. But you can specify a function name in the program being debugged.
Soft attach	Select to attach to a target without restarting the target device. This is very handy when the device uses flash, memory cards, or other external media for booting purposes and when it's not possible to configure the device to restart by the debugger. With soft attach, the debugger doesn't change the state of the target device. The debugger halts the target after attaching to the target to show the current PC location. User can preform normal debugging operations from then onwards.
Debug from start address	Select this option to stop the target at the start address once the target initialization is done and the OS is downloaded; if you have chosen to download the OS.
Run from start address	Select this option to run the target from the start address once the target initialization is done.
Start Address (hex)	Specify the memory address that the Carbide debugger will use to set the program counter to start the target. This is typically the start address of the Symbian OS.
Reset target at the start of each debug session	Select this check box to reset the target at the start of each debug session. For Trace32, the reset is typically done as part of the CMM script file. - Consult board specifications to determine if resetting is necessary.
Target Processor	Select a target processor from the drop down list of all supported processors. By default the field is set to Generic. When you select a processor, Carbide determines whether the debugger provides ARMV5 or ARMV6 support.
Target Initialization File	Select the check box and enter or browse to the target initialization file. Typically, this initialization file is used to initialize the target after connecting. When using Trace32, the initialization is done in the CMM script file.
Memory Configuration File	Select the check box and enter or browse to the memory configuration file. The Carbide debugger uses this configuration file to determine which memory is accessible, readable, and writable on the target.
Default Instruction set	The following options are available: - - Auto (examine code at current PC location) - Arm (32 bit) - Thumb (16 bit) - - Arm is the default. It is used by the debugger to determine the processor mode when it cannot be determined otherwise. This can happen at addresses for which there is no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code.

ROM Image

Figure 4 - Sophia Launch Configuration Settings - ROM Image Tab

Table 4. Launch configuration window—ROM Image tab items

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

Item	Explanation
Parse Rom Log File	Check this option to parse the ROM log file.
Symbian Rom Log File	Enter or browse to the Rom log file that is generated when the Symbian OS image is built. This is necessary for debugging any Symbian OS module.
Symbian Epoc32 Directory	Enter or browse to the epoc32 directory for the Symbian OS kit that is being targeted for debugging. This is necessary for the debugger to resolve the full paths for each module in the log file since the log file does not contain the full paths.
Log unresolved modules	Check this option to log unresolved modules. If the actual binary in the log file doesn’t exist on the PC, then a warning message will be logged in a Rom Log console window.
Debug non-XIP executables	Check this option to target non-XIP executables. This allows the debugger to target a non-XIP module whenever it’s loaded.
Download Rom Image	Check this box to enable downloading.
Symbian Rom Image	Enter or browse to the Symbian OS image (.img file) that will be downloaded onto the target at the specified download address.
Download Address (hex)	Specify the address where the image is to be downloaded. This address is target-specific. The address should be in hexadecimal format with the 0x prefix.
Same as start address	Check this option to make the download address the same as the start address.
Ask for download at the start of each debug session	Select this option to prompt you to download the image at the start of the debug session.

Executables

Figure 5 - Sophia Launch Configuration Settings - Executables Tab

Table 5. Executable pane —items

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

Item	Explanation
Load symbols for these executables and target them for debugging	Select the rule which govern the executable support used by this project for debugging purposes. The options include: - - Executables in the workspace from this SDK — shows all executables in the workspace built using the specified SDK. This is the default setting. - Executables built by this project — shows only the executables built by this project using the specified SDK - Executables selected below — shows only the executables chosen by the user. Initial list display uses the All Executables listing. - All executables (slows launch) — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. -
Executables list	Shows all the executables associated with this project.
Add...	Opens the Select an executable file dialog which can locate and select executable files and add them to the project's executables list.
Select All	Enables all the executables in the list for debugging.
Unselect All	Disables all the executables in the list from debugging.

Source

Figure 6 - Sophia Launch Configuration Settings - Source Tab

Table 6. Launch configuration window—Source tab items

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

Item	Explanation
Source Lookup Path	Allows you to add locations to search for source files. You can arrange the list by selecting the type of source path and clicking Up and Down buttons. Select a type of source and click Remove button to delete the item from the list.
Search for duplicate source files on the path	Enable this option to search for duplicate source files on source paths listed.

Common

Figure 7 - Sophia Launch Configuration Settings - Common Tab

Table 7. Launch configuration window—Common tab items

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

Item	Explanation
Save As	Allows you to save the launch configuration as a file local to the project or as shared file. For a shared file you can enter or browse to a folder within an existing project directory.
Display in favorites menu	Select menu for launch configuration to appear.
Console Encoding	Select the character set to use to display information in the console window.
Standard Input and Output	Allocate input and output to console and/or specified file. If a file is selected, you can select Append option to append data to selected file.
Launch in background	Enable this option to launch debug operation in a background process.

Related concepts

Launch Configurations
About the Debugger

Related tasks

Creating a Launch Configuration

Related references

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_disconnect.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_disconnect.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,34 +0,0 @@ - - - - - - -Disconnecting the Debugger - - - -

Disconnecting the Debugger

Use the Disconnect command () when debugging with Application TRK or System TRK to detach the debugger from a process on the device while leaving the device running.

When debugging in stop-mode it will detach the debugger and leave the CPU running on the device.

Disconnecting the Debugger

Click the Disconnect button () in the Debug view

-
or
-

Right-click the thread in the Debug view and select Disconnect from the Debug context menu

Related references

Working with the Debugger
Debug View

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_kill.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_kill.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,45 +0,0 @@ - - - - - - -Killing Program Execution - - - -

Terminate Program Execution

Use the Terminate command () to stop or halt a program based on the type of debugging session underway. Terminate behavior includes:

Emulator - terminates program execution and ends the debug session
Application TRK or System TRK - kills the process on the device and ends the debug session. To terminate without killing the process, use Disconnect instead.
Stop-mode soft attach - suspends the attached process while other processes continue to run on the device. If only a single process is running on the device, the device CPU is suspended. Once the CPU is suspended you must launch a new debug session to resume the device CPU.

This behavior differs from suspending a program, as this temporarily suspends execution.

NOTE If the Debug view loses focus, the Terminate control will appear disabled. To regain focus, select a thread in the Debug view to update the tool bar and reactivate the Terminate control.

Terminating Program Execution

Click the Terminate button () in the Debug view

-
or
-

Right-click and select Terminate from the Debug context menu

Select Run > Terminate from the menu bar

The debugger kills program execution and ends the debugging session.

NOTE If using an emulator, exiting it will also end the debugging session.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_restart.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_restart.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,36 +0,0 @@ - - - - - - -Common Debugging Actions - - - -

Restarting the Debugger

Use the Restart command () after stopping program execution. The debugger goes back to the beginning of the program and begins execution again. This behavior is equivalent to killing execution, then starting a new debugging session.

Restarting the Debugger

Click the Restart button () in the Debug view

-
or
-

Right-click the thread in the Debug view and select Restart from the Debug contextual menu

Select Run > Restart from the menu bar

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_resume.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_resume.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,41 +0,0 @@ - - - - - - -Resuming Program Execution - - - -

Resuming Program Execution

Use the Resume command () to continue executing a suspended debugging session. If the debugging session is already active, use this command to switch view from the Thread window to the executing program.

NOTE If the Debug view loses focus, the Resume control will appear disabled. To regain focus, select a thread in the Debug view to update the tool bar and reactivate the Resume control.

Resuming Program Execution

Click the Resume button () in the Debug view

-
or
-

Right-click the thread in the Debug view and select Resume from the Debug contextual menu

Select Run > Resume from the menu bar

The suspended session resumes, or the view changes to the running program.

NOTE The Resume command appears only for those platforms that support it. If your platform does not support this command, you must stop the current debugging session and start a new session.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_run.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_run.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,42 +0,0 @@ - - - - - - -Running a Program - - - -

Running a Program

Use the Run command () to execute a program normally, without debugger control. If the target is an emulator, the emulator is launched and the program installed. Use the emulator controls to run the program within the emulator environment. If the target is not an emulator, the program is installed and can be run on the device like any other program.

When starting the program for the first time, there are two types of launch configurations that you can choose between:

Run As > Symbian OS Application — select this option to create a new run launch configuration for the project or run the the first launch configuration it finds in the run launch configuration list (starting at the top of the list). Basically, this is a shortcut to help you start debugging immediately.
Open Run Dialog... — enables you to define one or more launch configurations for this project.

Running a Program

Click the Run () control in the tool bar

-
or
-

Right-click the project's EXE file in the C/C++ Projects view and select Run As > Project_Name from the C/C++ Projects context menu

The debugger does not control program execution as the program runs.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_start.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_start.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,45 +0,0 @@ - - - - - - -Starting the Debugger - - - -

Starting the Debugger

Use the Debug command () to begin debugging a compiled program. The debugger takes control of program execution, starting at the main entry point of the program. When starting the debugger for the first time, there are two types of debug launch configurations that you can choose between:

Debug As > Symbian OS Application — select this option to create a new debug launch configuration for the project or run the the first debug launch configuration it finds in the debug launch configuration list (starting at the top of the list). Basically, this is a shortcut to help you start debugging immediately.
Open Debug Dialog... — enables you to define one or more launch configurations for this project.

In the following steps, Config_Name refers to both debug launch configuration types.

Starting the Debugger

NOTE You can only debug compiled programs. Use the Build Project command to compile project sources into a binary file.

Right-click the project's EXE file in the C/C++ Projects view and select Debug As > Config_Name from the C/C++ Projects contextual menu

Select the project to debug and click the Debug button () in the C/C++ perspective

-
NOTE If you don't see the Debug button on your EXE file you'll need to define a Configuration for the program.
-
or
-

Select the project to debug and then select Run > Debug As > Config_Name from the menu bar

The current routine executes and returns to its caller, then program execution stops

NOTE Some projects require additional configuration before the debugging session can begin. The IDE might prompt you for permission to perform this configuration automatically.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepinto.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepinto.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,44 +0,0 @@ - - - - - - -Stepping Into a Routine - - - -

Stepping Into a Routine

Use the Step Into command () to execute one source-code statement at a time and follow execution into a routine call.

When stepping through a program in a debug session the IDE attempts to match the program counter (PC) location in the executable with a known project source file. If there is no source file associated with the PC the debugger displays in the Debug view the current PC address of the thread (e.g. 0x6002CC11(EUSER.DLL)()) instead of the function name. At this point you can open the Disassembly view to step through the assembler code. This most commonly happens when trying to step into Symbian OS code. We recommend that you Step Return out of the OS code and back into your project to continue debugging.
-

Stepping Into a Routine

Click the Step Into button () in the Debug view

-
or
-

Right-click the thread in the Debug view and select Step Into from the Debug contextual menu

Select Run > Step Into from the menu bar

After the debugger executes the source-code statement, the current-statement arrow moves to the next statement determined by these rules:

If the executed statement did not call a routine, the current-statement arrow moves to the next statement in the source code.
If the executed statement called a routine, the current-statement arrow moves to the first statement in the called routine.
If the executed statement is the last statement in a called routine, the current-statement arrow moves to the statement that follows the calling routine.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepout.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepout.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,38 +0,0 @@ - - - - - - -Step Return Out of a Routine - - - -

Step Return Out of a Routine

-Use the Step Return command (

) to execute the rest of the current routine and stop program execution after the routine returns to its caller. -

This command causes execution to return up the calling chain.

Step Returning from a Routine

Click the Step Return button () in the Debug view

-
or
-

Right-click the thread in the Debug view, then select Step Return from the Debug context menu

Select Run > Step Return from the menu bar

The current routine executes and returns to its caller, then program execution stops

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepover.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepover.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,43 +0,0 @@ - - - - - - -Stepping Over a Statement - - - -

Stepping Over a Statement

Use the Step Over command () to execute the current statement and advance to the next statement in the source code. If the current statement is a routine call, program execution continues until reaching one of these points:

the end of the called routine
a breakpoint
a watchpoint
an eventpoint that stops execution

Stepping Over a Routine

Click the Step Over button () in the Debug view

-
or
-

Right-click the thread in the Debug view and select Step Over from the Debug contextual menu

Select Run > Step Over from the menu bar

The current statement or routine executes, then program execution stops.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stop.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stop.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,30 +0,0 @@ - - - - - - -Suspending Program Execution - - - -

Suspending Program Execution

Use the Suspend command () to stop program execution during a debugging session.

Stopping a Debug Session

Select the thread in the Debug view to suspend
Click the Suspend () button, or right-click the thread and select Suspend

The operating system surrenders control to the debugger, which suspends program execution.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/launch_config_toolbar.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/launch_config_toolbar.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/new_config.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/new_config.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/sos_processes_attach.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/sos_processes_attach.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/add_build_config_create_wnd.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/add_build_config_create_wnd.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/icon_add_item_to_list.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/icon_add_item_to_list.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_build_config_select_tgt_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_build_config_select_tgt_02.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_prj_debugas_debug.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_prj_debugas_debug.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_prj_debugas_sos_menu.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_prj_debugas_sos_menu.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/new_launch_config_wiz.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/new_launch_config_wiz.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_app.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_app.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_02.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_bld_tgt.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_bld_tgt.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_cpp_view.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_cpp_view.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/pref_launching.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/pref_launching.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/proj_prop_builders.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/proj_prop_builders.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/run_config_device.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/run_config_device.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/symprojnav_mmp.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/symprojnav_mmp.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_01.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_02.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_03.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_03.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_04.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_04.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_hellocarbide_cpp_view.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_hellocarbide_cpp_view.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wiz_add_sos_class_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wiz_add_sos_class_01.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wiz_add_sos_class_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wiz_add_sos_class_02.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_debug_configuration.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_debug_configuration.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_03.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_03.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_04.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_04.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_07.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_07.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_08.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_08.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_prj_freeze_def_files.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_prj_freeze_def_files.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_prj_props_createsis.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_prj_props_createsis.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/wiz_new_launch_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/wiz_new_launch_config.htm Mon Aug 10 15:21:12 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,95 +0,0 @@ - - - - - - - New Launch Configuration Wizard - - - -

New Launch Configuration Wizard

The New Launch Configuration Wizard launches when no launch configuration exists for a project. Wherever possible the New Launch Configuration wizard gathers the information from the project and asks additional questions based on the type of launch configuration chosen. For example, a launch configuration using Application TRK requires different information than one targeted for System TRK.

For Application TRK and System TRK the following pages appear:

Launch Type
Executable Selection
TRK Connection Settings
TRK SIS Selection (Application TRK only)
New Launch Configuration

For Trace32 launch configurations the following wizard pages appear:

Launch Type
Executable Selection
Trace32 Initialization Settings
Symbian ROM Image Settings
New Launch Configuration

For Sophia STI launch configurations the following wizard pages appear:

Launch Type
Executable Selection
Sophia Initialization Settings
Symbian ROM Image Settings
New Launch Configuration

For Attach to Process launch configurations the following wizard pages appear:

TRK Connection Settings
New Launch Configuration

To access the New Launch Configurtion Wizard, set the Build Target to a Phone Debug target (Figure 1), then click the Debug icon (). If no launch configuration exists for the build target the wizard is launched. If a launch configuration already exists, then that launch configuration is launched and not the wizard.

For emulator targets, the New Launch Configuration Wizard can gather all the information it needs from the project, so clicking Debug just launches the debug session.

Figure 1 - Build Target selection list

Launch Types

Use the Launch Types page to select the type of launch configuration for the build target. This page does not appear when using an Emulator target. Available types are listed from the most frequently chosen (Application TRK) to the least likely type (Attach to Process). Select a type and click Next.

Figure 2 - Launch Type page

Executable Selection

Use the Application Selection page to choose a binary created by the project to launch and debug and verify its location. If only a single binary is available the Process to launch option is disabled.

EMULATOR ONLY Use the Location field for emulator targets to verify that the correct executable on the host is selected. This field is not used with on-device launch configurations.

Use the Specify device path of remote process to launch option to specify alternate paths for launching the executable from RAM (c:\sys\bin\), ROM (z:\sys\bin\) or memory cards (e:\sys\bin\) .

Select the Executable to launch, verify it is the correct binary, then click Next.

Figure 3 - Executable Selection page (when project has multiple EXEs)

TRK Connection Settings

Use the TRK Connection Settings page to specify the connection used to communicate with the target device. If the device is already connected, the drop down list will include both the COM port and the name of the device using that port. Use the On-Device Conection dialog to verify and update all Carbide software services on the device. Choose the serial port used to communicate with the target device and click Next.

Figure 4 - TRK Connection Settings page

TRK SIS Selection

Use the TRK SIS Selection page to select the SIS file to install on the target device. Click the Modify SIS builder settings for build configuration link to open the SIS Builder properties pane to add, edit, or review the SIS files to build. Once the correct SIS File to Install is selected, click Next.

Figure 5 - TRK SIS Selection page

New Launch Configuration

Use the New Launch Configuration page to note the name of the configuration, confirm the launch configuration settings, and then launch the debug session. If something doesn't look right, click Back to return to a page and change its setting. If all the settings are correct, click Finish to start the debug session using this launch configuration.

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 6 - 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 7 - Trace32 Initialization Settings page

Sophia STI Initialization Settings

Use the Sophia STI Initialization Settings page to specify the target interface, initialization file, and target processor of the target device. Enter the Sophia Target Interface and Target Initialization File paths, choose a Target Processor, then click Next.

This page only appears when creating a Sophia STI launch configuration.

Figure 8 - Sophia STI 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 or Sophia STI launch configuration.

Figure 9 - Symbian ROM Image Settings page

Other references

Launch Configuration

- - - - \ No newline at end of file diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/window_updater.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/window_updater.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_copy_to_memory_card.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_copy_to_memory_card.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_select_device.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_select_device.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_stop_usb_device.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_stop_usb_device.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_file_transfer.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_file_transfer.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_mass_storage.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_mass_storage.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_remove_hardware.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_remove_hardware.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_both_resolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_both_resolved.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_both_unresolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_both_unresolved.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_read_resolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_read_resolved.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_read_unresolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_read_unresolved.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_write_resolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_write_resolved.png has changed diff -r 9b005a8e6778 -r 939a4e7e4597 core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_write_unresolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_write_unresolved.png has changed