Once the debugger is running, the following commands are available for controlling further execution of the debug program from Wing. These are accessible from the tool bar and the Debug menu:
- At any time, a freely running debug program can be paused with the Pause item in the Debug menu or with the pause tool bar button. This will stop at the current point of execution of the debug program.
- At any time during a debug session, the Stop Debugging menu item or toolbar item can be used to force termination of the debug program. This option is disabled by default if the current process was launched outside of Wing. It may be enabled for all local processes by using the Kill Externally Launched preference.
When stopped on a given line of code, execution can be controlled as follows from the Debug menu or tool bar:
Step Over will step over a single byte code operation in Python. This may not leave the current line if it contains something like a list comprehension or single-line for loop.
Step Into will attempt to step into the next executed function on the current line of code. If there is no function or method to step into, this command acts like Step Over.
Step Out will complete execution of the current function or method and stop on the first instruction encountered after returning from the current function or method.
Continue will continue execution until the next breakpoint, exception, or program termination
Run To Cursor will run to the location of the cursor in the frontmost editor, or to the next breakpoint, exception, or program termination.
Attach and Detach (only in Wing IDE Professional) may be used to change the debugger between different debug processes. This is for advanced users and is detailed in Attaching and Detaching.
|« 12.5. Debugger Status||Table of Contents||12.7. Viewing the Stack »|