Stepping through a program

You can use step commands to step through your program a single statement at a time. The statements can be source code or disassembly instructions. For an explanation of the step commands, see the related topic below.

To execute a Step Over command, do one of the following:

To execute a Step Into command, do one of the following:

ngaix.gif (1051 bytes)ngwin.gif (1069 bytes)To execute a Step Debug command, do one of the following:

To execute a Step Return command, do one of the following:

JavaWhen debugging your interpreted Java program, stepping behavior may be erratic when stepping into constructors, or when stepping into or over SystemLoad library functions.

ngjava.gif (225 bytes) Tip: If you step into a class that has not been registered with the debugger, you may receive a Cannot find source for null message. If this happens, issue a step return command to continue debugging. To avoid this problem, register the appropriate source file for the class or package containing that class) with the debugger before you start debugging.

ngrelt.gif (466 bytes)
Running a program
ngjava.gif (225 bytes)Registering a class or package

ngrelr.gif (548 bytes)
Step commands