To continue executing your code after you hit a breakpoint, click Resume in the Script tab. The following table summarizes the three ways to step through code. As you step through the code, monitor how your experience changes as the current line executes. The buttons also appear in the top-left corner of the Call Stack window. When the script pauses, execute the following code one line at a time by stepping through them with the buttons in the Script tab. A yellow arrow called the "debugger" indicates which line of code executes next. If you insert a breakpoint at a line in a script, the script pauses before it executes that line. You can also right-click the margin and click Insert Breakpoint. To insert a standard breakpoint at a line of code, left-click the margin to the right of its line number. You can insert a breakpoint at any line of executable code. Breakpoints are one of the most effective ways to debug functions, so they're one of the most important debugging tools. You can use the pauses to inspect and debug your experience, watch variables, and inspect the call stack. Inserting Breakpointsīreakpoints are checkpoints that pause or "break" the execution of your scripts at specific lines. For more information, see Breakpoint Configurations. As you learn the general workflow, you can configure the breakpoints to break only if certain conditions are met, to print a message to the Output window, and to run only on the client or server. Repeat the previous steps until you solve the problem or find its root cause. In the Script tab, click Stop to end the debugging session.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |