Efficiently Debug Using Advanced Breakpoint Functionality
First-rate debugging begins with the effective use of breakpoints. Use the debugger to add breakpoints that suspend the execution of your code and allow you to examine the state of your application at that time. You can examine important clues in your troubleshooting such as the stack trace of each thread, console output, and the values of variables and expressions.
Applying hit counts and conditional breakpoints take this functionality to another level. A hit count allows you to suspend execution after a line of code has been hit a specified number of times. This can be useful when you want to break into a loop after a certain number of iterations. A conditional breakpoint allows you to suspend execution of a thread only when an expression is true or the result changes.
Use breakpoints to improve debugging
Easily Navigate the Application
The ability to easily navigate an application during the debug process can be especially important if you are debugging large projects. With the debugger you are in control. You can easily suspend and resume threads and drop to frame to re-enter a stack frame. You can also use the various Step commands (e.g., Step over, Step into and Step return) to control the execution flow when walking through your code.
Control the debug flow with execution commands
Simplify with Source Maps