All Packages from org.eclipse.debug.core.* to org.eclipse.debug.ui.*

Home >> All >> org >> eclipse >> debug

•

Package Samples:

• org.eclipse.debug.ui.sourcelookup
• org.eclipse.debug.ui.console
• org.eclipse.debug.ui.actions
• org.eclipse.debug.ui
• org.eclipse.debug.internal.ui.views.variables
• org.eclipse.debug.internal.ui.views.registers
• org.eclipse.debug.internal.ui.views.memory
• org.eclipse.debug.internal.ui.views
• org.eclipse.debug.internal.ui.views.breakpoints
• org.eclipse.debug.internal.ui.views.console
• org.eclipse.debug.internal.ui.views.expression
• org.eclipse.debug.internal.ui.views.launch
• org.eclipse.debug.internal.ui.launchConfigurations
• org.eclipse.debug.internal.ui.actions
• org.eclipse.debug.internal.ui
• org.eclipse.debug.internal.ui.preferences
• org.eclipse.debug.internal.ui.sourcelookup
• org.eclipse.debug.internal.ui.sourcelookup.browsers
• org.eclipse.debug.internal.ui.stringsubstitution
• org.eclipse.debug.internal.core.sourcelookup.containers

Classes:

• DebugEvent: A debug event describes an event in a program being debugged or in a running process. Debug models and process implementations are required to generate debug events as specified by this class. The following list defines the events generated for each debug model element. The getSource() method of a debug event returns the element associated with the event. Creation events are guaranteed to occur in a top down order - that is, parents are created before children. Termination events are guaranteed to occur in a bottom up order - that is, children before parents. However, termination events are not ...
• ILaunchShortcut: A launch shortcut is capable of launching a selection or active editor in the workbench. The delegate is responsible for interpretting the selection or active editor (if it applies), and launching an application. This may require creating a new launch configuration with default values, or re-using an existing launch configuration. A launch shortcut is defined as an extension of type org.eclipse.debug.ui.launchShortcuts . A shortcut specifies the perspectives in which is should be available from the "Run/Debug" cascade menus. A launch shortcut extension is defined in plugin.xml . Following is an ...
• IDebugModelPresentation: A debug model presentation is responsible for providing labels, images, and editors associated with debug elements in a specific debug model. Extensions of type org.eclipse.debug.ui.debugModelPresentations implement this interface. Generally, a debug model implementation will also provide a debug model presentation extension to render and display its elements. A debug model presentation is registered for a specific debug model, and is responsible for the presentation elements defined/implemented by that model. A debug model presentation extension is defined in plugin.xml . Following is an example ...
• ILaunchConfigurationTabGroup: A launch configuration tab group is used to edit/view attributes of a specific type of launch configuration. Launch configurations are presented in a dialog, with a tab folder. Each tab manipulates one or more attributes of a launch configuration. The tab group controls which tabs are displayed for a specific type of launch configuration, and provides a mechanism for overriding configuration initialization performed by tabs. A tab group has the following lifecycle methods: createTabs(ILaunchConfigurationDialog, String) - this is the first method called on a tab group after it is instantiated. initializeFrom(ILaunchConfiguration) ...
• IDebugUIConstants: Constant definitions for debug UI plug-in. Popup menus in the debug UI support action contribution via the org.eclipse.ui.popupMenus extension. Actions may be contributed to any group on the menu. To facilitate insertion of actions inbetween existing groups, empty groups have been defined in the menu. Each group prefixed by "empty" indicates an empty group. Debug View Popup Menu Empty edit group Edit group Copy stack action Empty step group Step group Step into group Step into action Step over group Step over action Step return group Step return action Empty thread group Thread group Resume action ...
• ILaunchConfigurationType: Describes and creates instances of a specific type of launch configuration. Launch configuration types are defined by extensions. A launch configuration type extension is defined in plugin.xml . Following is an example definition of a launch configuration type extension. <extension point="org.eclipse.debug.core.launchConfigurationTypes"> <launchConfigurationType id="com.example.ExampleIdentifier" delegate="com.example.ExampleLaunchConfigurationDelegate" modes="run, debug" name="Example Application"> </launchConfigurationType> </extension> The attributes are specified as ...
• IBreakpoint: A breakpoint is capable of suspending the execution of a program at a specific location when a program is running in debug mode. Each breakpoint has an associated marker which stores and persists all attributes associated with a breakpoint. A breakpoint is defined in two parts: By an extension of kind "org.eclipse.debug.core.breakpoints" By a marker definition that corresponds to the above breakpoint extension For example, following is a definition of corresponding breakpoint and breakpoint marker definitions. Note that the markerType attribute defined by the breakpoint extension corresponds to ...
• ILaunchConfigurationTab: A launch configuration tab is used to edit/view attributes of a specific type of launch configuration. Launch configurations are presented in a dialog, with a tab folder. Each tab manipulates one ore more attributes of a launch configuration. A tab has the following lifecycle methods: setLaunchConfigurationDialog(ILaunchConfigurationDialog) - this is the first method called on a tab after it is instantiated. initializeFrom(ILaunchConfiguration) - called when a launch configuration is selected to be displayed. activated(ILaunchConfigurationWorkingCopy) - called when a tab is entered. deactivated(ILaunchConfigurationWorkingCopy) ...
• IStatusHandler: A status handler registers to handle a specific status - error or otherwise. Provides a mechanism for separating core (headless) function from UI interaction. The debug plug-in provides a status handlers extension point, against which handlers can register for specific status codes - identified by plug-in identifier and plug-in specific status code. The interaction between an object requiring a status handler (source), and the status handler is defined by the source and handler. For example, a launch configuration delegate might encounter a timeout while launching an application. In this case the ...
• IConsoleColorProvider: Provides coloring for a console document. When a process is added to a registered launch the debug plug-in creates a console document for the process. By default, a document is created which is connected to the standard input, output, and error streams associated with the process. A client may override the default coloring by specifying a custom content provider for a process type. A proccess type is defined via the process attribute IProcess. ATTR_PROCESS_TYPE . A console color provider extension is defined in plugin.xml . Following is an example definition of a console color provider extension. ...
• ILogicalStructureType: Provides a value representing the logical structure of a raw implementation value from a debug model. Logical structures are useful for navigating complex data structures. Logical structure types are contributed via extensions in plug-in XML, and provide a delegate for performing logical value computation. Logical structure types can be retrieved from the DebugPlugin . Following is example plug-in XML to define a logical structure type. <extension point="org.eclipse.debug.core.logicalStructureTypes"> <logicalStructureType id="com.example.ExampleLogicalStructure" class="com.example.ExampleLogicalStructureDelegate" ...
• AbstractDebugView: Common function for views related to debugging. Clients implementing views for a debugger should subclass this class. Common function includes: Debug view adpater implementation - IDebugView Action registry - actions can be stored in this view with a key. Actions that implement IUpdate are updated when updateActions() is called. Hooks the context menu associated with this view's underlying viewer and registers the menu with this view's site, such that other plug-ins may contribute. Hooks a key press listener, and invokes the REMOVE_ACTION when the delete key is pressed. Hooks a double-click listener, ...
• ISourceLocator: A source locator locates source elements for stack frames. A launch (optionally) specifies a source locator which is used to locate source for that debug session. If a launch does not provide a source locator, source cannot be displayed. Abstraction of source lookup allows clients to hide implementation details of source location and representation. Generally, an implementor of a debug model will also implement launch configuration types, delegates, and source locators that work together as a whole. That is, the implementation of a source locator will have knowledge of how to locate a source element ...
• IToggleBreakpointsTarget: An adapter to support breakpoint creation/deletion for an active part or selection within an active part. The debug platform provides retargettable actions for toggling line breakpoints, method breakpoints, and watchpoints. A debug implementation can plug into the global actions by providing an adapter of this type on relevant parts and objects. The debug platform provides one command and keybinding for each breakpoint operation. When a part is activated, a retargettable action asks the part for its IToggleBreakpointTarget adapter. If one exists, that adapter is delegated to to perform breakpoint ...
• ISourcePresentation: A source presentation is used to resolve an editor in which to display a debug model element, breakpoint, or source element. By default, a debug model presentation (which implements this interface) is used to resolve editors when performing source lookup. However, a source locator may override default editor resolution by implementing this interface. Source lookup consists of the following steps: Locating a source element - the source locator associated with a launch is queried for the source element associated with a stack frame. Resolving an editor in which to display a source element - by default, ...
• IProcessFactory: A process factory is used to override default process ( IProcess ) creation by the debug plug-in, and can be contributed via plug-in XML. When a new process is created via DebugPlugin.newProcess(..) , the launch configuration associated with the specified launch is consulted for a process factory attribute ( ATTR_PROCESS_FACTORY_ID ). If present, the associated process factory is consulted to create a process for the launch. If not present a default process implementation is created and returned by the debug plug-in. Following is example plug-in XML that contributes a process factory. <extension ...
• IStackFrame: A stack frame represents an execution context in a suspended thread. A stack frame contains variables representing visible locals and arguments at the current execution location. Minimally, a stack frame supports the following: suspend/resume (convenience to resume this stack frame's thread) stepping termination (convenience to terminate this stack frame's thread or debug target) A debug model implementation may choose to re-use or discard stack frames on iterative thread suspensions. Clients cannot assume that stack frames are identical or equal across iterative thread suspensions and must check ...
• ILaunchConfiguration: A launch configuration describes how to launch an application. Each launch configuration is an instance of a type of launch configuration as described by a launch configuration type extension. Each launch configuration has a launch configuration delegate which performs the actual launching of a configuration. A launch configuration may be shared in a repository via standard VCM mechanisms, or may be stored locally, essentially making the launch configuration private for a single user. Thus, a launch configuration may stored as a file in the workspace (shared), or as a file in the debug plug-in's ...
• IConsoleLineTracker: Notified of lines appended to the console. A line tracker is defined in plugin.xml . A line tracker is associated with a type of process. Following is an example definition of a console line tracker extension. <extension point="org.eclipse.debug.ui.consoleLineTrackers"> <consoleLineTracker id="com.example.ExampleConsoleLineTracker" class="com.example.ExampleConsoleLineTrackerClass" processType="ExampleProcessType"> </consoleLineTracker> </extension> The attributes are specified as follows: id specifies a unique identifier for this line tracker. class specifies a fully qualified ...
• IPersistableSourceLocator: A source locator that can be persisted and restored, to be used with a specfic launch configuration. The debug plug-in defines a source locator extension point for persistable source locators. A source locator extension is defined in plugin.xml . Following is an example definition of a source locator extension. <extension point="org.eclipse.debug.core.sourceLocators"> <sourceLocator id="com.example.ExampleIdentifier" class="com.example.ExampleSourceLocator" name="Example Source Locator"> </sourceLocator> </extension> The attributes are specified as follows: id specifies ...
• ISourcePathComputer: A source path computer computes the default source lookup path (set of source containers that should be considered) for a launch configuration. A source path computer is contributed in plug-in XML via the sourcePathComputers extension point, that provides a delegate to compute the path specific to a launch configuration. Following is an example contribution. <extension point="org.eclipse.debug.core.sourcePathComputers"> <sourcePathComputer id="org.eclipse.example.exampleSourcePathComputer" class="org.eclipse.example.SourcePathComputer"> </sourcePathComputer> ...
• IRunToLineTarget: An adapter for a "run to line" operation. The debug platform provides a retargettable "run to line" action that debuggers may plug into by providing an adapter (see IAdaptable ) of this type. This allows the platform to provide one command and keybinding for the "run to line" function to be shared by many debuggers. When a part is activated, a retargettable action asks the part for its IRunToLineTarget adapter. If one exists, that adapter is delegated to to perform "run to line" operations when the user invokes an associated action. If an adapter does not exist for the part, the retargettable actions ...
• ISourceContainerType: A source container type represents a kind of container of source code. For example, a source container type may be a project or a directory. A specific project or directory is represented by an instance of a source container type, which is called a source container ( ISourceContainer ). A source container type is contributed via the sourceContainerTypes extension point, providing a delegate to the work specific to the contributed type. Following is an example contribution. <extension point="org.eclipse.debug.core.sourceContainerTypes"> <sourceContainerType name="Project" ...
• IStepFilters: Support for step filters for a debug target. A debug target that supports step filters should implement this interface. Step filters can be toggled on/off for a debug target via this interface. When a step method is called (see IStep ), the step implementation must respect the state of the step filters as defined by this interface. This allows step filters to be toggled on/off for all stepping operations (in, over, return). Step filter management is debug model specific - this interface is used only to turn them on/off. In 2.1, the IFilteredStep interface was used to implement step filtering. The ...
• AbstractSourceLookupDirector: Directs source lookup among a collection of source lookup participants, and a common collection of source containers. Each source lookup participant is a source locator itself, which allows more than one source locator to participate in source lookup for a launch. Each source lookup participant searches for source in the source containers managed by this director, and each participant is notified of changes in the source containers (i.e. when the set of source containers changes). When a source director is intilaized, it adds it self as a launch listener, and automatically disposes itself when ...

Home | Contact Us | Privacy Policy | Terms of Service