5.10.13. Process control

To display the Process Control pane:

  1. Switch the Register pane back to the Process Control pane. To do this:

    1. Click the Pane Control menu button.

      The name of the previous pane (Process Control) is included at the top of the menu. This is an alternative to selecting the pane from the New Pane menu option.

    2. Select Process Control from the Pane Control menu.

      The Register pane switches back to the Process Control pane. It looks like the example in Figure 5.8.

    Figure 5.8. Process Control pane

    Process Control pane

    The Process tab shows details about your current process. If you are debugging a single process application, this is the same as viewing the processor details. In this example, you can identify the target processor and see details about your project and the loaded image.

  2. Right-click on an entry in this pane, for example dhrystone.axf, and select Properties from the context menu. This displays a text box giving more information on the chosen item.

Working with source files

When working with entries in the Process Control pane, you can use type ahead facilities to locate files. This is especially useful where your project specifies a large number of source files. For example, type the first letter of the source file that you want to view. RealView Debugger expands the Sources entry and locates the first matching occurrence. When using this feature, the type ahead buffer is case insensitive and is limited to 128 characters. Do one of the following to clear the buffer:

  • select a different item

  • press Home to move to the top of the pane

  • press Escape.

Working with images

Where you have created a user-defined project, it is recommended that you open this first to load and debug the associated image, or images. This enables you to access the project properties, save new settings, or make changes to the build model. In this example, the user-defined project is open so project settings have been used to populate entries in the Process tab.

When an image is loaded directly to a debug target, RealView Debugger checks to see if an auto-project exists for that image in the same location. Where no auto-project exists, RealView Debugger creates an in-memory project to use in the current session.

An auto-project is a custom, image control, project that holds project settings where the build model is unknown. You can view these settings using the Project Properties window. Using an auto-project enables you to amend and save image load parameters where you do not have a user-defined project or where you have no control over the build model. You also have the option to use the saved auto-project as the basis of a user-defined project.

Note

If you load an image built as part of a user-defined project without opening the project you cannot access all the project properties because these are unknown to RealView Debugger. In this case, RealView Debugger creates an in-memory project, or uses the saved auto-project file.

See the chapter that describes working with images in RealView Debugger v1.8 User Guide for details on using auto-projects in RealView Debugger.

Copyright © 2002-2005 ARM Limited. All rights reserved.ARM DUI 0181G
Non-Confidential