PowerAda Different Ways to Use the Debugger

Chapter 6

• 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

The debugger operates in either of two modes: execution or command. In execution mode, your program continues running until it either reaches a breakpoint, an unhandled exception, or a normal program end. In command mode, the debugger stops all execution while it reads and processes your commands. The debugger returns to execution mode when you issue a command to continue running the program or to start running the program from the beginning.

There are several ways you can use these two basic modes of operation:

• An interactive session using the debugger graphical user interface. This is the most common way the debugger is used.
• A series of commands from a script file. "Executing Pre-Recorded Commands: SCRIPT" in Appendix F describes how to do this using the SCRIPT command.
• A series of commands from a start-up file. "Executing Commands at Start-up" describes how to use this feature.
• By executing the target program on a different machine than the debugger. =

See "Remote Debugging" for information on this process.