Tip:
Highlight text to annotate it
X
Welcome to this screncast about debugger steps.
When you defined a breakpoint inside your script and you start the debugger, PHPEdit will stop before the execution of that line.
You can continue the debugging with steps.
The StepInto command for example will take you to each executed line.
You can start the debugger again to continue the script or chose to stop the running debug session.
The StepInto command allows you to follow the exact way PHPEdit takes to run your script.
Each time you call it, PHPEdit will go to the next line that will be executed and stop in front of it.
You will exactly see what’s going on in your script with this command.
The StepOver feature works a little bit different than the StepInto command.
It will execute each line of your code with the exception that it will not display you each executed line from within function calls.
When you just would like to debug your current block inside your code, and you know what going on inside your function calls,
you can just stop at each line is the same level of the callstack.
As you can see the breakpoint is reached multiple times but we do not see the execution of the function.
Our debugger steps just through the loop and we can concentrate on this level of the code.
The last command of this screencast is the StepOut command.
With this you can jump out of the current function, or method, and continue the debugging from the point where this function has been called.
When we start our debugging process from within a function we see each executed line.
With the StepOut command we will be taken to the point where the function has been called.
The rest of the function is executed but we do not need to step through each of that lines.