3.1.2. Default pane configuration

The default pane configuration in the Code window, shown in Figure 3.1, contains:

Top pane row

The top pane row contains the File Editor pane and
the Process Control pane as a side pane by default.

The File Editor pane is always positioned in the top pane
row. However, you can dock one or more other panes to the left or
right of the File Editor pane.

File Editor pane

The File Editor pane is always visible when working with RealView Debugger. You
cannot replace the File Editor pane with another pane (see Debug views and panes). However, you
can define how the view is formatted, for example you can change
the size of text displayed in the File Editor pane.

Use this area of the Code window to:

use a shortcut
to connect to a target or load an image.

enter text to create project files

open source files for editing and resaving

view disassembly

set breakpoints to control execution

use the available menu options to search for specific
text as part of debugging

follow execution through a sequence of source-level
and disassembly-level views

The File Editor pane contains a hyperlink to make your first
connection to a debug target. When a connection is made, this link
changes to give you a quick way to load an image.

When RealView Debugger first starts, the File Editor pane
contains tabs to track program execution:

If you load an image, or when you are working with source
files, more tabs are displayed, for example dhry_1.c.
In this case, click on the Src tab to see
the location of the PC.

See the chapter that describes editing source code in RealView
Developer Kit v2.2 Project Management User Guide for
full details on using the editing facilities in RealView Debugger.

Side pane

By
default, this contains the Process Control pane that displays details
of the current process when you are connected to target processor.
When you first run RealView Debugger, this pane is positioned to
the right of the File Editor pane but you can float this pane, and
place it at another position on the desktop.

The Process Control pane displays a Threads tab if
you are debugging an RTOS application.

Middle pane row

The middle pane row contains the following panes by default:

Call Stack pane

Use this pane to:

display the
procedure calling chain from the entry point to the current procedure

monitor local variables.

The Call Stack pane contains tabs:

Call Stack

Displays the stack functions call chain. This tab is selected
by default.

Locals

Shows
variables local to the current function.

Statics

Displays a list
of static variables local to the current module.

This

Shows
objects located by the C++ specific this pointer.

Watch pane

Use
this pane to:

set up variables
or expressions to watch

display current watches

modify watches already set

delete existing watches.

The Watch pane contains tabs to display sets of watched values.
The first tab, Watch1, is selected by default.

Memory pane

Use
this pane to:

display
the contents of a range of memory locations on the target

edit the values stored by the application.

Bottom pane row

The bottom pane row of the default Code window contains the
Output pane by default. Select the different tabs to:

enter commands during a debugging
session (Cmd)

handle I/O with your application (StdIO)

see the progress of builds (Build)

see the results of Find in Files operations (FileFind)

see the results of operations using your version
control tool (SrcCtrl)

view the results of commands and track events during
debugging (Log).

The command line is located at the bottom of the Output pane.
The command prompt includes the status of the current process, for
example, Stop>, Run>, or None> (no
process). You can also enter debugger commands at this prompt.