Home >> All >> org >> eclipse >> debug >> [ core Javadoc ]

•	org.eclipse.debug.core.model.* (40)	•	org.eclipse.debug.core.sourcelookup.* (22)
•	org.eclipse.debug.core.sourcelookup.containers.* (12)

• org.eclipse.debug.core: Javadoc index of package org.eclipse.debug.core.


Package Samples:

• org.eclipse.debug.core.model
• org.eclipse.debug.core.sourcelookup
• org.eclipse.debug.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 ...
• 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 ...
• 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 ...
• 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" ...
• 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 ...
• 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 ...
• 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> ...
• 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 ...
• IDebugElement: A debug element represents an artifact in a program being debugged. Some methods on debug elements require communication with the target program. Such methods may throw a DebugException with a status code of TARGET_REQUEST_FAILED when unable to complete a request due to a failure on the target. Methods that require communication with the target program or require the target to be in a specific state (for example, suspended), are declared as such. Debug elements are language independent. However, language specific features can be made available via the adapter mechanism provided by IAdaptable , ...
• IWatchExpressionDelegate: A delegate which computes the value of a watch expression when provided a context. Watch delegates are provided on a per debug model basis. Watch expressions query the appropriate delegate based on the debug model of the context element. Plug-ins that wish to contribute watch expression delegates may do so using the org.eclipse.debug.core.watchExpressionDelegates extension point. For example, the following is the definition of a watch expression delegate for the com.example.foo plug-in: <extension point="org.eclipse.debug.core.watchExpressionDelegates"> <watchExpressionDelegate debugModel="org.eclipse.jdt.debug" ...
• ISourceLookupParticipant: A source lookup participant participates in source lookup by searching an ordered list of source containers for source elements corresponding to a debug artifact. For example, a participant may be asked to find source corresponding to a stack frame or breakpoint. An implementation of a source lookup participant is debug model specific, since it must convert the debug model artifact (stack frame, breakpoint, etc.), into a source name that can be recognized by a source container ( ISourceContainer ), to search for source elements. Source containers are generally debug model independent, whereas source ...
• IVariable: A variable represents a visible data structure in a stack frame or value. Each variable has a value which may in turn contain more variables. A variable may support value modification. An implementation may choose to re-use or discard variables on iterative thread suspensions. Clients cannot assume that variables are identical or equal across iterative thread suspensions and must check for equality on iterative suspensions if they wish to re-use the objects. An implementation that preserves equality across iterative suspensions may display more desirable behavior in some clients. For example, if ...
• IValue: A value represents the value of a variable. A value representing a complex data structure contains variables. An implementation may choose to re-use or discard values on iterative thread suspensions. Clients cannot assume that values are identical or equal across iterative thread suspensions and must check for equality on iterative suspensions if they wish to re-use the objects. An implementation that preserves equality across iterative suspensions may display more desirable behavior in some clients. For example, if variables are preserved while stepping, a UI client would be able to update the ...
• IWatchExpression: A watch expression is an expression that is evaluated in the context of a specific stack frame, thread, debug target, process, or launch. Generally, a watch expression is a snippet of code that is evaluated each time a debug target suspends, or when a user provides a context for an evaluation by selecting a debug target or thread. An expression updates its value when it is provided with a context in which it can perform an evaluation. Clients are not intended to implement this interface. An implementation is provided by the debug platform. Clients that support watch expressions should contribute ...
• IExpression: An expression is a snippet of code that can be evaluated to produce a value. When and how an expression is evaluated is implementation specific. The context/binding required to evaluate an expression varies by debug model, and by user intent. Furthermore, an expression may need to be evaluated at a specific location in a program (for example, at a breakpoint/line where certain variables referenced in the expression are visible/allocated). A user may want to evaluate an expression once to produce a value that can be inspected iteratively, or they may wish to evaluate an expression iteratively producing ...
• ILaunchMode: A launch mode. The debug platform contributes launch modes for run, debug, and profile. Clients may contribute additional launch modes in plug-in XML via the launchModes extension point. Following is an example launch mode contribution for profiling. A launch mode has an unique identifer specified by the mode attribute and a human readable label specified by the label attribute. <extension point="org.eclipse.debug.core.launchModes"> <launchMode mode="profile" label="Profile"> </launchMode> </extension> Clients are not intended to implement this ...
• Launch: A launch is the result of launching a debug session and/or one or more system processes. This class provides a public implementation of ILaunch for client use. Clients may instantiate this class. Clients may subclass this class. Many of the methods in this class that are part of the ILaunch interface are final. Clients that subclass this class are not intended to change the behavior or implementation of the provided methods. Subclassing is only intended to add additional information to a specific launch. For example, a client that implements a launch object representing a Java launch might store ...
• IBreakpointManager: The breakpoint manager manages the collection of breakpoints in the workspace. A breakpoint suspends the execution of a program being debugged. The kinds of breakpoints supported by each debug architecture and the information required to create those breakpoints is defined by each debug architecture. Breakpoint creation is a client responsibility. Clients interested in breakpoint change notification may register with the breakpoint manager - see IBreakpointListener and IBreakpointsListener This interface is not intended to be implemented by clients.
• ISourceContainer: A source container is a container of source code. A source container is capable of searching for source elements by name. For example, a source container may be a project or a directory capable of searching for files by name. A source container may be a composite container - i.e. contain other source containers. When a source container is created and added to a source director, the source container's dispose() method is called when the source director is disposed. Clients creating source containers for other purposes must dispose of containers themselves.

Home | Contact Us | Privacy Policy | Terms of Service