Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Debug Platform/Planning
Revision as of 18:28, 19 August 2008 by Pawel.piech.windriver.com (Talk | contribs) (→Better platform)
This page is gathering place of ideas for the future evolution of the Eclipse debug platform (3.*, and e4).
There will be a phone meeting held at 11AM CST (12PM EST, 9AM PST) on Thursday, August 21st, 2008 to gather and dicuss these ideas. Please add your ideas here and join the meeting to discuss:
- Toll-free dial-in (North America): 1-866-245-5059
- Global toll free: 800-4444-1010
- Conference ID: 1696709
Contents
Debug Platform 3.5 and 3.*
More modular
- Asynchronous viewer framework
- Contribute asynchronous viewer to JFace (bug 161435).
- Create a virtual viewer implementation and tests for the async. viewer framework (bug 242489).
- Prototype a standard debug model/flexible hierarchy integration using DSF View Model (Pawel Piech).
Better platform
- Contribute process "Spawner" from CDT to platform, to support process IDs and system signals (Darin Wright).
- Make it easier to create different breakpoint types from the same editor (bug 212316).
- Make run to line adapter async (bug 213074).
- Allow command framework handlers easy access to active debug context 229219.
- Allow plug-ins to extend/modify/cancel launches (bug 175538).
- Move breakpoint actions from CDT to the platform (Ken Ryall).
- Support EFS (external file system) for launch configuration persistence (Darin Wright).
Better workflow
- Debugging without the debug view or debug perspective
- Lightweight context switching (quick pop-up to select new context)
- Would a bread crumb solution be helpful/possible? (provides context and navigation in one)
- Where should the debug toolbar reside?
- AlanB: some customers have sized the debug view until it just shows the toolbar to get around the fact that they can't have just the debug toolbar.
- Could we get workbench support to allow action sets to appear in menus and/or toolbar selectively?
- Is there a need for lightweight variables view or "debug dashboard"?
- Lightweight context switching (quick pop-up to select new context)
- Debugger tooltip enhancements
- Instant debugger tooltips, without waiting for operating system delay (may require some infrastructure changes for tooltips in the platform ui)
- Each time you step, tooltip automatically refreshes the displayed value
- AlanB: pin the tooltip to the variable so that it follows it as the editor is scrolled
- AlanB: show hovers for each variable on the current line
- Expressions view: click or double-click to add or edit expressions in-line (without dialog)
- Mikhail K: Breakpoints presentation
- Decorate breakpoints according to active debug context (bug 238954)
- Improve usability of the breakpoints view (bug 238956)
- AlanB: Add ability for Variables view to just show variables on the current execution line.
More reliable
- Create more meaningful performance tests and backport to 3.4
- Pawel: a virtual tree viewer as a test tool and for copy, find, etc.
Debug Platform e4
More modular
- Use services instead of singletons (launch manager, expression manager...)
- Separate launching into a new component, that can be used without debug
- Moving forward what happens to the standard debug model? DSF?
Better platform
- Improve launch framework
- Consolidate/simplify launching APIs (mixed mode, launch shortcuts, contextual launch)
- Should we continue to use launch configurations, or consider an architecture that would allow aspects of a launch be used more easily to compose different types of launch configurations (e.g. JRE, Source lookup...)
- How can we make the UI for a launch aspect more reuseable?
- Merge external tools with run/debug
- Support for multi-launch
- Provide direct access to a process's input/output streams (no need for StreamsProxy)
- Namespace for launch configurations should not be flat