As you write PL/SQL code for an application, you want to ensure your application functions according to requirements. If you notice an error in the behavior of a module at runtime, you can identify the line of code that is causing the error by debugging the code.
The Builder includes an interactive PL/SQL debugger that enables you to effectively run and debug your application in an integrated development environment. This means you can monitor and modify the runtime environment while the application is running, which allows you to test how various changes in form item values and variable values will affect your application.
The simple interface of the debugger provides great control in debugging your applications locally or remotely.
The debugger functions in the Builder allow you to:
To perform any of these debugging tasks, you need to run your application in debug mode to invoke the debugger.
When you work with the debugger, you use these components:
Debugger Component | Description |
---|---|
Debug Console and windows |
The main component of the debugger is the Debug Console. When application execution is interrupted during debugging, debug windows in the Debug Console display information related to the current execution context. Use the debug windows to examine stack frames and data such as local variables, global variables, and form item values. |
Debug toolbar buttons |
Contains buttons you use to perform debug actions, such as Step Into, Step Over, Step Out, and Pause. The toolbar is enabled when you run your application in debug mode. |
Debug menu |
Contains the same debug action commands as the debug toolbar buttons. Also contains commands to toggle showing and hiding the Debug Console and debug windows. |
PL/SQL Editor |
When application execution is interrupted during debugging, the PL/SQL Editor opens and displays the current executing subprogram with a pointer at the current execution source line. |