16. Debugging Your Application : How Debugging an Application Works : How You Can Control Execution of Your Application : Step Into Button
 
Share this page                  
Step Into Button
The Step Into button behaves like the Step button in all cases except the following:
When the next statement to be executed is a callframe statement.
The Step Into button moves you into the script for the frame and stops at the first statement in the initialize block. If the called frame has no initialize block, there is no statement to execute and you must click Step, Step Into, or Continue to display the frame and continue execution.
When the next statement is a callproc statement.
The Step Into button moves you to the script for the called procedure and stops at the first executable statement.
When the next statement invokes a method of a user class.
The Step Into button moves you into the script for the method and stops at the first executable statement.
When the next statement is openframe.
If a new thread is created, a new Debugger window is opened. The Debugger stops execution at the first statement of the initialize block of the new frame. If there is no initialize block, you must click Step, Step Into, or Continue to display the frame and continue execution.
There is an exception if the called frame, procedure, or method is in an included application, and the included application is in an image file. In this case, Step Into behaves like Step because no source is available. If the included application is in the database, however, the source is available.