This list can be fine-tuned on the Build, Execution, Deployment | Debugger | Stepping page of the Settings/Preferences dialog Ctrl+Alt+S. Some methods (for example methods of standard Java classes like System) are skipped by Step into as you normally don't need to debug them. To configure this feature, go to Settings/Preferences | Build, Execution, Deployment | Debugger | Stepping and set the Always do smart step into option as required.
Alternatively, it can be invoked only when you expressly do so. You can configure Smart Step Into to be automatically used every time when there are multiple method calls on the line. If there are several method calls on the line, IntelliJ IDEA asks you which method to enter. If you step into, the debugger will jump into the implementation of the count(int to) method allowing you to examine in detail how its result is produced. In the example, line 5 is about to be executed. Use this option when you are not sure the method is returning a correct result. Steps into the method to show what happens inside it. To skip any breakpoints on the way, use Force step over. If there are breakpoints inside the skipped methods, the debugger will stop at them. If you step over, the debugger will move straight to line 6 without jumping into the count() method. The implementation of the methods is skipped, and you move straight to the next line of the caller method.
#THE PROGRAM CODE#
Steps over the current line of code and takes you to the next line even if the highlighted line has method calls in it. The stepping buttons are located on the Debug window toolbar. IntelliJ IDEA provides a set of stepping actions, which are used depending on your strategy (for example, whether you need to go directly to the next line or enter the methods invoked on your way there). Stepping is the process of controlling step-by-step execution of the program.
0 kommentar(er)
