Once execution of your program is halted, you can step through your lines of
code using the following commands on the Debug menu or toolbar:
Step Over (F8). Executes one source line. If the source line contains
a call, executes the entire routine without stepping through the individual
instructions.
Step Into (F7). Executes one source line. If the source line contains
a call, the IDE stops just before executing the first statement of the routine.
You can also start a debugging session with the Step Into command. Program
execution stops on the first line after the main routine before
any changes have been made to the state of the program.
Step Out (Ctrl-F7). Executes one source line. If the source
line is part of a routine, executes the remaining lines of the routine and
returns control to the caller of the routine.
Notes:
By default, the IDE steps over all calls to JDK classes. To step into JDK
classes when debugging, choose Window > Debugging
>
Sources (Alt-Shift-8). The sources window lists all of the source directories
on your project classpath. Check the checkbox for the JDK sources to let the
debugger step into the JDK sources.
For
, you set the target JDK in your Ant script and specify the source
level in the Project Properties dialog box. When you step into JDK
classes, the IDE searches the platforms registered in the Java Platform Manager
for a Java platform with a matching source level. If no matching Java platform
is found, the IDE opens the source code for the IDE's default platform.
If you have a free-form project on the classpath of another project, you
must declare the free-form project's output files in order to step into classes
from the project. To declare the output files, right-click the free-form project
node and choose Properties. Then click Outputs and specify the output file
for each source folder.