Re: [platform-debug-dev] Requirement for more stepping types

[Darin_Wright@xxxxxxx]

The java debug model implements a similar feature - step filtering. The user defines the packages/types they are *not* interested in seeing. When active, any "step into" action steps until the next "interesting" code is hit. To implement this feature, no additional step types are required in core. Instead, there is a "Use Step Filters" option that is added to the preference pages, and to the debug view pop-up menu (via standard workbench extendsions).

I would think that a similar thing could be done for step debug. Using standard action contribution mechanims, you could add a special step button to the debug view that invoked the special "step debug" function.

Darin

boxall@xxxxxxxxxx Sent by: platform-debug-dev-admin@xxxxxxxxxxx 01/16/2002 03:08 PM Please respond to platform-debug-dev

To:        platform-debug-dev@xxxxxxxxxxx         cc:                 Subject:        [platform-debug-dev] Requirement for more stepping types

I need to support another stepping type.

The debug core has the following step types:

Step into
Step over
Step return

I need to add ... Step debug.

Step debug is a special case where the debug engine will step until it hits
user code.  It is a hybrid of step into and step over.

There are 2 areas that are affected:

The core and the UI.

The core explicitly looks at the detail of the DebugEvent to determine if
it is one of its known types.

The UI adds the step icons to the debug view and asks the debug targets
what they support.

Do you have any suggestions/ways for me to extend it to add my Step Debug?

Alan Boxall - IBM Distributed Debugger

_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-debug-dev