beautypg.com

Status bar, Code line indicators – Zilog Z8F0130 User Manual

Page 411

background image

UM013037-1212

Status Bar

Zilog Developer Studio II – Z8 Encore!

User Manual

387

Status Bar

The status bar displays the current status of your program’s execution. The status can be
STOP, STEP, or RUN. The STOP mode indicates that your program is not executing. The
STEP mode indicates that a Step operation (using the Step Into, Step Over, or Step Out
command) is in progress. The RUN mode indicates that the program is executing after a
Go command has been issued. In RUN mode, the following debug operations are avail-
able: Reset, Stop Debugging, and Break.

When the program is in RUN mode, disabling a breakpoint temporarily stops and resumes
program execution. If a breakpoint is reached before it is disabled, program execution does
not resume. When the program is in RUN mode, enabling the breakpoint also temporarily
stops and resumes program execution but, if the program reaches a breakpoint after you
enable it, the program stops or breaks. You must press the

Go

button again to continue the

program execution. See the

Using Breakpoints

section on page 404 for more information

about breakpoints.

View/read memory, Step Into, Step Over, Step Out, and Go are disabled in RUN mode.

The status bar is either a box displayed in the upper right corner under the title bar or a hor-
izontal bar under the buttons, depending on your screen resolution.

Code Line Indicators

The

Edit

window displays your source code with line numbers and code line indicators.

The debugger indicates the status of each line visually with the following code line indica-
tors:

A red octagon indicates an active breakpoint at the code line; a white octagon indi-
cates a disabled breakpoint.

Blue dots are displayed to the left of all valid code lines; these are lines in which
breakpoints can be set, the program can be run to, and so on.

Some source lines do not have blue dots because the code has been optimized out of the
executable (and the corresponding debug information).

Note:

Note:

Note: