Use step filters |
This option controls is step filtering should be enabled or not. See also the step
filtering command in the
Debug View
|
On |
Defined step filters |
This is a listing of all of the defined step filters (the listing itself) and whether the step filters are in use or not (the checked state of step filter) |
|
Add Filter button |
Used to add a new step filter that is based on a regular expression |
|
Add Class button |
Used to add a new Java class to the listing of step filters |
|
Add Packages button |
Used to add new Java packages to the listing of step filters |
|
Remove button |
Used to remove the selected step filter(s) |
|
Select All button |
Used to set all defined step filters as enabled (or checked) |
|
Deselect All button |
Used to set all defined step filters as disabled (or unchecked) |
|
Filter synthetic methods |
This option controls if synthetic method should always be filtered or not while stepping. This option requires that the VM used support synthetic methods |
Off |
Filter static initializers |
This option controls if static initializers should always be filtered or not while stepping |
Off |
Filter constructors |
This option controls if constructors should always be filtered or not while stepping |
Off |
Step through filters |
This option controls step filters to always return from
a filtered location or step through to a non-filtered location.
For
example, if java.util is a filtered location, stepping
into code in HashMap could result in a call-back to your
application code to check the equality of an object. If you choose to Step through filters a step into would end up in your
application code. However, when the Step through filters option is disabled, a step into HashMap would behave like
a step over.
|
On |