![]() Select the breakpoint that will trigger the current breakpoint. Select to remove the breakpoint from your project right after it has been hit. Select to evaluate an expression when the breakpoint is hit, and show the result in the console output. This is useful if you want to check what paths have led to this point without interrupting the program's execution. Stack trace: when the breakpoint is hit, its stack trace will be printed to the console. "Breakpoint hit" message: a log message will be displayed in the console output when the breakpoint is hit. Select if you want to log the following events to the console: If you selected any logging actions in the Log area, the Console tab shows the corresponding message: If the expression evaluates to true, the program is suspended. When the debugger reaches the line with a conditional breakpoint, the specified boolean expression is evaluated. Optionally, specify the actions that you want WebStorm to perform if the condition is met and the debugger stops at the breakpoint, learn more from Log below. (!Array.isArray(scope) & typeof scope = 'object' To edit the properties of a breakpoint, press Control+Shift+F8, or right-click the breakpoint in the editor gutter. In the Breakpoints dialog, select the breakpoint you want to delete under JavaScript Exception Breakpoints or Dart Exception Breakpoints and click or press Alt+Delete.ĭepending on the type of a breakpoint, you can configure the following additional breakpoint properties:Īctions to be performed when the breakpoint is hitĪ suspend policy that defines whether the application must be suspended when the breakpoint is hitĬonditions that define when the breakpoint must be hit Then, in the Add Exception Breakpoint dialog that opens, specify an exception class from a library or from your project. To have the debugger stop at exceptions of a specific type, press Alt+Insert or click and select JavaScript Exception Breakpoint. ![]() In the Breakpoints dialog, select the Any exception checkbox. Press Control+Shift+F8 or select Run | View Breakpoints from the main menu. Exception breakpointsĮxception breakpoints are triggered when the specified exception is thrown. Clicking a breakpoint will then toggle its state (enabled/disabled). To avoid accidentally removing a breakpoint and losing its parameters, you can choose to remove breakpoints by dragging them to the editor, or by clicking the middle mouse button: open the Settings dialog ( Control+Alt+S), go to Build, Execution, Deployment | Debugger, and select Drag to the editor or click with middle mouse button. Click the gutter and select the functions where you want to set breakpoints. The breakpoint will be removed from your project right after it is hit.įor arrow functions, you can set multiple breakpoints within a single line. To set a temporary line breakpoint, press Control+Alt+Shift+F8. Set a line breakpointĬlick the gutter next to the executable line of code where you want to set a breakpoint.Īlternatively, place the caret at this line and press Control+F8. Thread execution is suspended before the line with such breakpoint, and WebStorm displays the stack frames on that thread's stack. Line breakpoints can be set on executable lines of code. ![]() Note that WebStorm must be running when such changes are made, otherwise they will pass unnoticed. If a file with breakpoints was modified externally, for example, updated through a VCS or changed in an external editor, and the line numbers have changed, breakpoints will be moved accordingly. Once set, a breakpoint remains in your project until you remove it explicitly (except for temporary line breakpoints). Breakpoints are source code markers that let you suspend program execution at a specific point and examine its behavior.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |