To skip any breakpoints on the way, use Force run to cursor. You can configure whether you want Run to Cursor to work on clicking a line number in Settings/Preferences | Build, Execution, Deployment | Debugger. Place the caret at the line where you want the program to pause.Ĭlick the Run to cursor button or press Alt+F9.Īlso, you can Run to Cursor by clicking the line number in the gutter. Steps out of the current method and takes you to the caller method.Ĭlick the Step out button or press Shift+F8.Ĭontinues the execution until the position of the caret is reached. If you do not want to use it automatically, go to Settings/Preferences | Build, Execution, Deployment | Debugger | Stepping and clear the Always do smart step into checkbox. You can also select it using the arrow keys or tabs and press Enter/ F7.īy default, smart step into is used every time when there are multiple method calls in the line. This feature allows you to select the method call you are interested in.įrom the main menu, select Run | Debugging Actions | Smart Step Into or press Shift+F7.Ĭlick the method. Smart step into is helpful when there are several method calls on a line, and you want to be specific about which method to enter.
#Thonny source code code
When debugging, you might want to concentrate on your own code and prevent debugger from stepping into library classes.Ĭlick the Step Into My Code button ( Alt+Shift+F7). 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 all library scripts, select the Do not step into library scripts checkbox. In the Settings/Preferences dialog ( Ctrl+Alt+S), go to Build, Execution, Deployment | Debugger | Stepping. This list can be fine-tuned on the Build, Execution, Deployment | Debugger | Stepping page of the Settings/Preferences dialog ( Ctrl+Alt+S). Some scripts are skipped by Step into as you normally might not need to debug them.
This feature is called Smart step into.īy default, smart step into is used every time when there are multiple method calls on the line. If there are several method calls on the line, P圜harm asks you which method to enter. Use this option when you are not sure the method is returning a correct result.
Steps into the method to show what happens inside it. To skip any breakpoints on the way, use Force step over. If there are breakpoints inside the skipped methods, the debugger will stop at them. The implementation of the methods is skipped, and you move straight to the next line of the caller method. Steps over the current line of code and takes you to the next line even if the highlighted line has method calls in it. The stepping buttons are located on the Debug window toolbar. P圜harm provides a set of stepping actions, which are used depending on your strategy (for example, whether you need to go directly to the next line or enter the methods invoked on your way there). Stepping is the process of controlling step-by-step execution of the program.
0 kommentar(er)
