PowerAda Using the Debugger Window Commands

From OC Systems Wiki!
< PowerAda:APPENDIX F. Debugger Command Reference
Revision as of 21:53, 14 April 2019 by imported>WikiVisor
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The PowerAda debugger allows you to divide your display screen into several regions. If you are debugging on a character display, you can subdivide the display into up to three vertical sections. If you are using a terminal with the AIXwindows Environment licensed program, you can open up to three different windows to display different types of input and output data, or subdivide a single window as on a character display. In the following sections, operations like resizing that apply to windows under AIXwindows also apply to subdivisions of the display screen on character displays.

Opening a Window: OPEN

When the debugger starts, all input and output is displayed in a single area. Use the OPEN command to create new display areas to hold specific types of output data. Its syntax is:

open WindowName [Attributes]

All debugger input and output is through the original command window. As you issue OPEN commands, the display area where you enter debugger commands becomes smaller if needed to make room for new windows.

Window Names

WindowName can be one of the following names; if you use a different name, the debugger opens a window with that name to display output from the IN command. You cannot open more than one of any type of window.

Source Displays output from Ada source files.If a breakpoint is set on a line visible in the source window, the debugger places a marker arrow on the line with the breakpoint. ProgramIO Displays all output from a program you run through the debugger, and accepts input for that program. Help Displays any output from the HELP command. Error Displays any error messages from the debugger. Stderr Under an AIXwindows display only, displays the output from standard error while the program runs. You must open it before issuing the LOAD command.

Window Attributes

The attributes that you specify control the window's appearance. To change the attributes of an existing window, use the RESIZE command. To choose the opposite of an attribute, precede it with NOT.

Hidden Shrinks the window so that just the title is displayed. If you use RESIZE to expand the window again, the contents are restored. Reversed Displays text in the window in reverse video. Size You can select the number of lines for the window as
StartLine..EndLine or StartLine-EndLine. To specify the exact size and position for the window, you select the top-left and bottom-right corners of the window as TopLeftX,TopLeftY..BottomRightX,BottomRightY or TopLeftX,TopLeftY-BottomRightX,BottomRightY

Closing a Window: CLOSE

Use this command to close any windows you no longer want on your screen:

close WindowName

When a window closes, the debugger may expand the command window to minimize the empty space on the screen. It may also displace other windows.

Clearing a Window: CLEAR

Use this command to clear the text from the named window:

clear WindowName

Directing Commands to a Window: IN

Direct output or commands into a window:

in WindowName [do Statement]

The DO clause specifies the debugger command to be executed in the named window.

Two basic functions are provided. Without a DO clause, the IN command switches control to the named window; the debugger prompts for commands and produces output in that window until control is switched to some other window. With a DO clause, the command directs the statement to be executed in the named window, with control returned to the current window. For example:

in source
in fred do? x

Resizing a Window: RESIZE

Use this command to change the attributes of a debugger window, for the curses display only. The attributes are the same as for the OPEN command. The RESIZE command has the following syntax:

resize WindowName Attributes

When a window changes size, the debugger may expand or shrink the command window to accommodate the amount of space on the screen. The debugger may move other windows to further minimize empty space on the screen, but the other windows will not be resized. The command window will always hold at least one text line.