Debug Project New and Noteworthy for 3.3M3
| |
|
| Mixed mode launch APIs and more | The debug platform's launch API now supports
mixed mode launching. For example, an ISV could contribute a launcher
to profile and debug an application at the same time. See enhancements
to the ISVs can also contribute one or more tabs to existing tab groups in the
launch dialog to extend existing launch types with new function. For example,
a profiling tool could provide a tab to configure profile options for
Java applications. See the new extension point The platform also allows more than one toolset to exist for launching the same kind of application. For example, two profilers could exist for Java applications and the user would be prompted to choose which profiler to use at runtime. |
| |
|
| Debug context API | The debug platform has new API to access the
active debug context. A debug context represents the active state of a program
being debugged and drives the enabled state of debug actions (step, terminate,
etc.), as well as source lookup, visible variables, and watch expression
values. A set of classes and interfaces have been added to the new package
org.eclipse.debug.ui.contexts allowing clients to listen to
and drive the active debug context. |
| |
|
| Debug command API | Debug commands represent common operations implemented
by debuggers - for example, step over, suspend, resume, and terminate. The
debug platform has added API allowing debuggers to provide custom implementations
of the operations by implementing the debug command interfaces. See the
new package org.eclipse.debug.ui.commands. |
| |
|