Stepping Through the Program
When a breakpoint is reached the Debug tool window becomes active and enables you to get control over the program's execution. For this purpose, you can use the menu commands, or the icons on the stepping toolbar of in the Debug tool window.
Each stepping action advances the execution point to the next execution location, depending on the action you choose.
Stepping through the program
Suppressing stepping into
You can create a list of scripts, methods, and functions that you want the debugger skip while stepping through the program.
In the Settings/Preferences dialog (Ctrl+Alt+S), click Debugger under Build, Execution, Deployment, and then click Stepping. The Debugger. Stepping page opens.
To skip all library scripts, select the Do not step into library scripts checkbox.
To suppress stepping into some specific scripts, select the Do not step into scripts checkbox and create a list of such scripts using the toolbar buttons.
To skip some PHP methods
In the Settings/Preferences dialog (Ctrl+Alt+S), click PHP under Languages and Frameworks, and then click Step Filters under Debug. The Step Filters page opens.
Select the checkboxes next to the relevant method types: Magic methods and Constructors.
If necessary, add specific methods to the Skipped Methods list using the toolbar button.
Tips and tricks
The Force Step Into command enables you to step into a method of a class not to be stepped into.
The classes, stepping into which is suppressed, are specified on the Debugger. Stepping page of the Settings/Preferences dialog box.
The Force Step Over command enables you to jump over the method call ignoring the breakpoints on the way.
The Force Run to Cursor command enables you to jump to the cursor position ignoring existing breakpoints on the way.