Class
You are required to enter the fully-qualified class name of the class in which you wish to set a class breakpoint for. If you are setting a breakpoint in a nested class be sure to use the same naming conventions as is used for naming .class files (ie. use the $ character instead of the . character) as this is the format BugSeeker uses to determine precisely which class to set the breakpoint. Example: use org.myproject.Outer$Inner rather than org.myproject.Outer.Inner).
Name
You may optionally assign a name to this breakpoint. A default name will be assigned if you do not enter a breakpoint name.
Group
From the combo, select the breakpoint group you wish to assign this breakpoint to. Breakpoint groups allow you to organize your breakpoints logically into groups which is helpful if you have lots of breakpoints set for the current project. All breakpoints will be initially assigned to the current breakpoint group that is specified on the current breakpoint group combo on the main BugSeeker application window's toolbar.
Enable
Check this option if you wish to enable this breakpoint; uncheck if you wish to disable this breakpoint. A disabled breakpoint will no longer have any effect on the current debugging session.
Skip
If this option is checked, you will be allowed to specify the amount of times BugSeeker is to skip this breakpoint before it is to evaluate the condition expression (if any) and then possibly perform any specified actions.
Skip amount
Enter the number of times BugSeeker is to skip this breakpoint. The value must be equal to or greater than one. A skip amount of three means the first three times execution reaches this location will be ignored until the fourth encounter in which case we will perform the breakpoint action if the condition expression (if any) evaluates to true.
Repeat
If this option is checked, we will keep repeating the skip amount continuously. If this option is unchecked, once we perform the specified skip amount, the breakpoint will evaluate the conditional expression each time the breakpoint is encountered as though skip were disabled.
Condition
If this option is checked, you are required to enter a conditional expression that BugSeeker will evaluate each time the breakpoint is encountered. Only when the expression evaluates to true will the breakpoint actions be performed. If the expression evaluates to false, no action is taken place. If BugSeeker is unable to evaluate the expression because the expression is invalid an error message indicating such a condition will be displayed on the Console and execution will resume. Please consult Appendix B for details on how to specify expressions in BugSeeker.
Action
The breakpoint actions are performed only after the conditional expression (if any) evaluates to true. You usually will want to ensure that at least one action is selected although there is nothing preventing you from creating a breakpoint with no actions enabled.
Break
If this option is checked, the debug session will be paused when this breakpoint is encountered.
Log expression
If this option is checked, you will be required to enter an expression in which BugSeeker is to log and display its value on the Console. An example expression would be "n=" + n. Please refer to Appendix B for details on how to specify expressions in BugSeeker.