| |
|
|
|
Stepping In
The Step In feature provides the finest granularity at which you can stop and inspect your application. Stepping in causes the application to stop just before executing the next instrumented command. Stepping in is useful for following the control flow of your application as it sources files, calls procedures, and evaluates command substitutions.
For example, if your application is stopped on the command
myProc [incr x 5]
you can Step In and stop the application before it evaluates the subcommand incr x 5. You can Step In again to stop the application on the first line of code in the body of the myProc procedure.
The following list describes the rules of behavior for the Step In function:
- If the current command contains subcommands, the application stops just before evaluating the first subcommand.
- If the current command is a call to an instrumented procedure, and all subcommands, if any exist, have been evaluated, the application stops on the first line of code in the body of the procedure.
- If the current command is a call to the source command, and all subcommands, if any exist, have been evaluated, the application stops on the first line of code in the sourced file.
- If the current command is not a call to an instrumented procedure, and all subcommands, if any exist, have been evaluated, the application stops on the first instrumented command called by the current command.
- If the current command does not call any instrumented code, then the Step In function behaves like the Step Over function.
 http://www.ajubasolutions.com Voice: (650) 210-0100 Fax: (650) 210-0101 support@ajubasolutions.com |
| |
|
|
|