Properties

Class

You are required to enter the fully-qualified class name of the exception class in which you wish to set an exception 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.

Enabled

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.

Action

There are two actions available when this breakpoint is encountered. You usually will want to ensure that at least one action is selected although nothing prevents you from creating a breakpoint that has no actions enabled.

Break

If this option is checked, the debug session will become paused when this breakpoint is encountered.

Log

If this option is checked, a message indicating this breakpoint has been reached will be displayed on the Console.

Filter

If this option is checked, you will be able to enter class filters to restrict where this exception breakpoint is allowed to pause execution when thrown. For instance, if you are only interested in catching IllegalArgumentExceptions that are thrown within your own code and wish to ignore this exception if it is thrown in the Java class libraries you would use this breakpoint filter feature to restrict this breakpoint to only your code.

To edit the filters, click on the Edit Filters button which is enabled only when the Filter option is checked. A new dialog will be displayed that will allow you to enter class name patterns that specify which classes are to be used to restrict this breakpoint.

Allowable class name patterns are ones that begin or end with the wildcard star (*) character and exact class name matches. A wildcard star character matches any character zero or more times.

To add a new pattern, click on the Add button or click on the special Click here to add a new filter list item. To remove a pattern, select one or more patterns and press the Remove button. To edit an existing class name pattern, double-click on that list item.

Stop only in these classes

If this option is selected, the exception breakpoint is to be active only in classes whose name matches one of the patterns. Use this option if you know precisely which classes you are interested in pausing execution when the exception is thrown.

Stop in all except these classes

If this option is selected, the exception breakpoint is to be active only in classes whose name does not match any of the patterns entered. Use this option if you know beforehand which classes you are not interested in pausing the debugging session when the exception is thrown.