Click to show the list of available breakpoint types. Select the desired type to create a new breakpoint.
Click this button to remove selected breakpoints.
Group by File
Press this button to display breakpoints under their respective files:
The controls of this part of the Breakpoints dialog depend on the type of the selected breakpoint.
Types of breakpoints
Select this check box to suspend program when a breakpoint is hit. If the check box is
not selected, the program is not suspended.
Select this check box and specify a condition for hitting a breakpoint in the text field.
A condition is a Boolean expression.
This expression should be valid at the line where the breakpoint is set, and is evaluated every time the breakpoint is reached.
If the evaluation result is true, user-selected actions are performed.
If evaluation result is true, user-selected actions are
If the result is false, the breakpoint does not
produce any effect. If the Debugger cannot evaluate the expression, it displays the Condition
evaluation error message. You can select whether you would like to stop at this breakpoint or ignore
Log message to console
Select this check box if you want a log message to be displayed in the console output when the
breakpoint is hit.
Log evaluated expression
Select this check box if you wish to evaluate a certain expression at this breakpoint and to export
result to the console output.
These options are specific for Python exception breakpoints only.
The Debugger stops when the process terminates with this exception.
If this option is selected, the Debugger stops on throwing an exception. So doing, there are two alternative options:
At each level of call chain: click this radio-button to make the Debugger stop
every time an exception is thrown (including each function call up the stacktrace,
until this exception is caught or the process is terminated).
At top of call chain: click this radio-button to make the Debugger stop only on the first place where the exception has been thrown.