Answering for DD:
1- What is the planned date for the next major release of your
project? Version number?
Device Debugging will release Version 0.9 in June 2007 along
with the Europa Eclipse train release. We will release milestones with
Europa starting with milestone 3.
2- What are the most important features to be added in this
release?
This release with contain a near-production quality Debugger
Services Framework (DSF) with will take advanced of recent enhancements in the
Eclipse Platform Debug Interfaces. This framework will allow commercial device
software tooling vendors to better implement their commercial debug engines in Eclipse.
The framework will contain an MI implementation design to be the next
generation CDT debugger implementation for GDB. The release will also
contain enhanced debug view support, including multi-core capabilities. Finally,
the release will contain initial tooling for the IP-XACT Debug specification currently
in design in the SPIRIT consortium.
3- What are the major benefits of those features?
Device Software Tooling vendors typically have proprietary debug
engines geared towards embedded-specific debugging capabilities. These
engines often provide greater visibility into and control over target
hardware. The DSF technology will provide a modular, extensible, and
performant framework for implementing embedded debuggers in Eclipse.
Multi-core support will allow debugger views to associate
themselves with one or more debug contexts, e.g. processors, cores, processes,
threads. Multiple debug views of the same type will exist and will
display information specific to their context. For example, imagine
having two register views showing the hardware registers of two different cores
on an embedded processor.
The SPIRIT consortium originally formed to provide EDA vendors with
common data file formats for describing system-on-chip hardware. The
consortium recently created a new working group around specifications for
debugger tooling. The IP-XACT debugger specification is designed to provide
silicon vendors with a standard data file format for describing their hardware
so that tools vendors can better display information from and provide control
over the hardware.
4- Will anything be left out of this release, and if so, what?
API’s will be provisional in the 0.9 timeframe. We
are currently planning additional functionality (mostly features) beyond the
June 07 Europa release.
5- When will those left-out features be added?
A maintenance release later in 07 will contain additional
functionality.
6- The tool will run on which major operating systems? (Linux,
Windows, MacOS)
All, but the testing focus will be Linux and Windows.
7- The tool requires which version of Eclipse?
The Europa release, likely versions Eclipse 3.3.
8- The tool plugs into an existing Eclipse install does it install
a new distribution?
It plugs into an existing install. It is designed to be
used in conjunction with CDT, although CDT will be optional.
9- Would you consider the project “mostly framework”
or “mostly tool” and why?
Mostly framework. The CDT project already provides tooling
for C/C++ development. The DD project exists to provide additional
frameworks for more customized embedded debugger implementations that one can get
from CDT or the Eclipse Platform.
10- What are the purpose and intended user group(s) for your project?
In open source, the intended user group will be users of the GDB
debug engine. Commercially, we are targeting all companies that build
embedded debuggers on top of Eclipse. We intend to provide the
next-generation CDT debugger implementation while at the same time enabling
companies that do debugging outside of CDT.
11- What other Eclipse projects does DD have
dependencies on?
Eclipse Platform
CDT
12- Please provide your full name, title, project and your role in
it.
Doug Gaff
Engineering Manager, Wind River Systems
DSDP PMC Lead, DD Project Lead