If you are debugging a long procedure, you can stop the debugger while it is working.
To stop the Debugger while it is debugging
The status panel will reset from Running to Idle.
When you have finished debugging your PL/SQL code, the debug symbol tables are left in the code. This makes your code larger and can slow performance. To eliminate this issue, compile the code and its dependencies and references one last time without debug information.
To compile without debug information
Toad sends your PL/SQL debugger output results to the PL/SQL Results window. This window is located on a tab in the output area of the Editor.
When the PL/SQL execution terminates, the PL/SQL Results window displays the input and output of the code, in a format similar to that shown in the Set Parameters window (parameter name, data type, input, and output). If there is a cursor result, you can view the data stored in each REF CURSOR that is returned via out parameters or as a function result.
From this window, you can create new unit tests (Code Tester for Oracle and utPLSQL), run Code Tester for Oracle unit tests, and also open Code Tester for Oracle. Create and Run Unit Tests From Execution Results
The PL/SQL Results window has the following limitations:
To view cursor data
To access the PL/SQL Results tab
If you cannot see the PL/SQL Results window at the bottom of the Editor, try one the following:
Toad provides an intuitive and efficient way to write, run, and test your SQL and PL/SQL code. Toad supports efficient code management for a single developer or a whole team of developers.