Step filters allow for uninteresting packages and classes to be ignored during step debugging.
execute
method of the SampleHandler
class.HandlerUtil
and then into ExecutionEvent
.org.eclipse.ui
, followed by a click on OK:getApplicationContext
method in the ExecutionEvent
class.getApplicationContext
method, the execution will drop through to the getVariable
method of the ExpressionContext
class instead.
Step Filters allows uninteresting packages to be skipped, at least from the point of debugging. Typically, JVM internal classes (such as those beginning with sun
or sunw
) are not helpful when debugging and can easily be ignored. This also avoids debugging through the ClassLoader
as it loads classes on demand.
Typically it makes sense to enable all the default packages in the Step Filters dialog, as it's pretty rare to need to debug any of the JVM libraries (internal or public interfaces). This means that when stepping through code, if a common method such as toString
is called, debugging won't step through the internal implementation.
It also makes sense to filter out simple setters and getters (those that just set a variable or those that just return a variable). If the method is more complex (like the getVariable
method previously), then it will still stop in the debugger.
Constructors and static initializers can also be filtered specifically.
18.218.234.83