PowerAda Commands to Change the View

Appendix F

• Notice
• Chapter 1. Overview
• Chapter 2. Getting Started
• Chapter 3. Basic PowerAda Concepts
• Chapter 4. The PowerAda Development Environment
• Chapter 5. Project Management with PowerAda
• Chapter 6. The PowerAda Debugger: adbg
• Chapter 7. Interface to Other Languages
• Chapter 8. Implementation Details
• Chapter 9. Optimization
• APPENDIX A - Glossary
• APPENDIX B - Support Packages
• APPENDIX C - Implementation Characteristics
• APPENDIX D - Demos and Tutorials
• APPENDIX E - Tools Reference
• APPENDIX F - Debugger Command Reference
• Index

Contents |  Installation Guide | Release Notes

First | Prev | Next | Last

These commands can be used to change the current task of reference. Subsequently all your object display and modification is done within the context of that task or view.

Selecting a Task for Debugging: BOTTOM

The BOTTOM command changes the current task. Its syntax is:

bottom TaskName

This command causes TaskName to become the new current task of reference, and sets the view within that task to be the bottom, or "real", frame. If you do not name a task, the current task is not changed. The only effect is to reset the view.

The BOTTOM command selects a task from which you select the view. After the debugger executes the BOTTOM command, the view is the lowest level on the dynamic chain (call stack) of that task. Subsequent UP and DOWN commands can change the view to other levels on the same task.

Not every task is allowed to be current. The debugger rejects tasks that are not alive. Examples of tasks that are not alive include terminated tasks and tasks in the process of being created.

Here are some examples of BOTTOM:

bottom
bottom my_test

Moving the Program View Down: DOWN

The DOWN command moves the program view down one or more call levels. Its syntax is:

down Count

The Count qualifier specifies the number of levels to be traversed. The default is one level.

DOWN moves the view lower, towards the frame most recently called frame on the current task's call stack. If there are fewer levels beneath the current position than specified, the debugger positions the view on the bottom frame. Some examples are:

down
down 2

Restoring the Program View: RESTORE

During debugging you may backtrack through the call chain using the UP command or you may switch tasks (in a multi tasked program) with the BOTTOM command. If you wish to restore your view to the original context when the program halted, the RESTORE command may be used. The syntax is

restore

This may be done from the command line or by clicking the Restore button in the debugger GUI.

Moving the Program View Up: UP

The UP command moves the program view up one or more levels. Its syntax is:

up Count

The Count qualifier specifies the number of levels to be traversed. The default is one level.

UP moves the view higher, towards the frame least recently called frame on the current task's call stack. If there are fewer levels above the current position than specified, the debugger positions the view on the top frame. Some examples are:

up
up 2